feat(voyage)!: bulk content rewrite ultra -> voyage/trek prose [skip-docs]

Sed-pipeline (16 patterns, longest-match-first) sweeper residuelle ultra*-treff
i prose, command-narrativ, agent-prompts, hook-kommentarer, doc-prosa.

Pipeline-utvidelser fra V4-prompten:
- BSD-syntax [[:<:]]ultra[[:>:]] istedenfor \bultra\b (BSD sed mangler \b)
- 6 compound-patterns for ultraplan/ultraexecute/ultraresearch/ultrabrief/
  ultrareview/ultracontinue uten -local-suffiks
- ultra*-stats glob -> trek*-stats glob
- Linje-eksklusjon redusert til ultra-cc-architect (Q8); session-state-
  eksklusjonen var over-protektiv
- File-eksklusjon utvidet til settings.json, package.json, plugin.json,
  hele .claude/-treet (gitignored + V5-territorium)

Q8-undantak holdt: architecture-discovery.mjs + project-discovery.mjs urort.
Filnavn-konvensjon holdt: .session-state.local.json + *.local.* preservert.

Manuell narrative-fix: tests/lib/agent-frontmatter.test.mjs linje 10
mangled "/ultra*-local" til "/voyage*-local" (ingen slik kommando finnes);
korrigert til "/trek*".

Residualer utenfor scope (V5 handterer): package.json + .claude-plugin/
plugin.json (Step 12-14 versjons-bump). .claude/* er gitignored
spec-historikk med tilsiktet BEFORE/AFTER-narrativ.

Part of voyage-rebrand session 3 (Wave 4 / Step 10).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

plugins/ultraplan-local/agents/planning-orchestrator.md

@@ -2,12 +2,12 @@
 name: planning-orchestrator
 description: |
   Inline reference (v2.4.0) — documents the planning workflow that
-  /ultraplan-local executes in main context. This file is NOT spawned as a
+  /trekplan executes in main context. This file is NOT spawned as a
   sub-agent anymore. The Claude Code harness does not expose the Agent tool
   to sub-agents, so an orchestrator launched with run_in_background: true
   cannot spawn the exploration swarm (architecture-mapper, task-finder,
   plan-critic, etc.) and would degrade to single-context reasoning. The
-  /ultraplan-local command now orchestrates the phases below directly in the
+  /trekplan command now orchestrates the phases below directly in the
   main session.
 model: opus
 color: cyan
@@ -23,12 +23,12 @@ tools: ["Agent", "Read", "Glob", "Grep", "Write", "Edit", "Bash", "TaskCreate",
      Orchestrator Phase 5   = Command Phase 8  (Deep planning)
      Orchestrator Phase 6   = Command Phase 9  (Adversarial review)
      Orchestrator Phase 7   = Command Phase 10 (Completion)
-     As of v2.4.0, /ultraplan-local runs these phases inline in main context
+     As of v2.4.0, /trekplan runs these phases inline in main context
      instead of spawning this agent. Keep this file as the canonical
      reference for what those phases do. -->
 
-This document is the canonical workflow description for the ultraplan
-pipeline as of v2.4.0. The `/ultraplan-local` command reads it as reference
+This document is the canonical workflow description for the trekplan
+pipeline as of v2.4.0. The `/trekplan` command reads it as reference
 and executes the phases below **inline in the main command context**. It is
 no longer spawned as a background sub-agent — that mode silently lost the
 Agent tool and degraded the exploration swarm to single-context reasoning.
@@ -40,9 +40,9 @@ tool, collects their results, synthesizes the plan, and writes it to disk.
 ## Input
 
 You will receive a prompt containing:
-- **Brief file path** — the task brief (produced by `/ultrabrief-local`)
-- **Project dir** (optional) — path to an ultrabrief project folder when the user
-  invoked `/ultraplan-local --project`. If set, the plan destination is
+- **Brief file path** — the task brief (produced by `/trekbrief`)
+- **Project dir** (optional) — path to an trekbrief project folder when the user
+  invoked `/trekplan --project`. If set, the plan destination is
   `{project_dir}/plan.md` and any `{project_dir}/research/*.md` files are
   pre-existing research briefs to read.
 - **Task description** — one-line summary (matches the brief's frontmatter `task`)
@@ -219,14 +219,14 @@ Write a comprehensive implementation plan including:
 - **Estimated Scope** — file counts and complexity
 
 **Plan-version header:** Include `plan_version: 1.7` in the metadata line below
-the title. This signals to ultraexecute-local that the plan includes per-step
+the title. This signals to trekexecute that the plan includes per-step
 verification manifests and enables strict audit mode. Plans without this
 marker are treated as legacy v1.6 with synthesized minimal manifests.
 
 ### Mandatory step format — copy this exactly
 
 The Implementation Plan section MUST contain numbered steps using the EXACT
-format shown below. The executor (`ultraexecute-local`) parses plans with
+format shown below. The executor (`trekexecute`) parses plans with
 strict regex matching. Any deviation breaks parsing and forces the user to
 re-run planning.
 
@@ -283,7 +283,7 @@ not skip fields. Do not nest steps under sub-headings.
 
 Every implementation step MUST include a `Manifest:` block as its last field,
 after Checkpoint. The manifest is the objective completion predicate — the
-machine-checkable contract that ultraexecute-local will verify after the
+machine-checkable contract that trekexecute will verify after the
 Verify command passes. A step cannot be marked passed if its manifest does
 not verify.
 
@@ -427,7 +427,7 @@ After both complete:
 - Address all blockers and major issues by revising the plan
 - **Manifest quality is a hard gate:** any manifest-related `major` finding
   must be fixed before the plan can be handed off. This enforces the
-  principle that ultraexecute-local relies on the plan being
+  principle that trekexecute relies on the plan being
   machine-checkable — a plan without verifiable manifests cannot drive
   deterministic execution.
 - Add a "Revisions" note at the bottom documenting changes
@@ -437,7 +437,7 @@ After both complete:
 When done, your output message should contain:
 
 ```
-## Ultraplan Complete (Background)
+## Voyage Complete (Background)
 
 **Task:** {task}
 **Plan:** {plan path}