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/brief-reviewer.md

@@ -7,8 +7,8 @@ description: |
   exploration with a flawed brief.
 
   <example>
-  Context: Ultraplan runs brief review before exploration
-  user: "/ultraplan-local --project .claude/projects/2026-04-18-notifications"
+  Context: Voyage runs brief review before exploration
+  user: "/trekplan --project .claude/projects/2026-04-18-notifications"
   assistant: "Reviewing brief quality before launching exploration agents."
   <commentary>
   Orchestrator Phase 1b triggers this agent after the brief is available.
@@ -35,8 +35,8 @@ missing, vague, or contradictory.
 
 ## Input
 
-You receive the path to a brief file (ultrabrief v2.0 format, produced by
-`/ultrabrief-local`). Read it and evaluate its quality across five dimensions.
+You receive the path to a brief file (trekbrief v2.0 format, produced by
+`/trekbrief`). Read it and evaluate its quality across five dimensions.
 
 A brief has these sections (see template for full structure):
 - `## Intent` — why the work matters (load-bearing)
@@ -115,18 +115,18 @@ Flag as **unclear scope** if:
 ### 5. Research Plan validity (NEW in v2.0)
 
 The `## Research Plan` section declares topics that must be answered before
-`/ultraplan-local` can produce a high-confidence plan. Validate:
+`/trekplan` can produce a high-confidence plan. Validate:
 
 **Per topic:**
 - **Research question:** phrased as a question, ends in `?`, answerable by
-  `/ultraresearch-local` (not "figure out the architecture" but "what are
+  `/trekresearch` (not "figure out the architecture" but "what are
   the tradeoffs between library X and library Y for our use case?")
 - **Required for plan steps:** names specific kinds of steps that consume
   this answer (e.g., "migration strategy", "library selection", "threat model")
 - **Confidence needed:** one of `high`, `medium`, `low`
 - **Estimated cost:** one of `quick`, `standard`, `deep`
 - **Scope hint:** one of `local`, `external`, `both`
-- **Suggested invocation:** copy-paste-ready `/ultraresearch-local` command
+- **Suggested invocation:** copy-paste-ready `/trekresearch` command
 
 **Cross-check with frontmatter:**
 - `research_topics: N` matches the actual count of `### Topic` headings
@@ -165,7 +165,7 @@ Rate each dimension on two parallel scales:
 - **1** — section is effectively missing or contradictory (maps to Fail)
 
 Use both. The verbal rating drives the human-readable verdict. The numeric
-score drives callers (such as `/ultrabrief-local` Phase 4) that use the
+score drives callers (such as `/trekbrief` Phase 4) that use the
 review as a quality gate and need per-dimension granularity.
 
 ## Output format
@@ -174,7 +174,7 @@ Produce **two artifacts in this order**:
 
 1. A prose report (for humans and for `planning-orchestrator` Phase 1b).
 2. A final fenced `json` block with per-dimension numeric scores (for callers
-   that gate on machine-readable output, such as `/ultrabrief-local` Phase 4).
+   that gate on machine-readable output, such as `/trekbrief` Phase 4).
 
 The JSON block MUST be the last fenced block in your output so parsers can
 find it by reading the last `json` code fence.
@@ -202,7 +202,7 @@ find it by reading the last `json` code fence.
 - **Suggestion:** {how to fix it}
 
 ### Suggested additions
-{Questions that should have been asked during the ultrabrief interview, or
+{Questions that should have been asked during the trekbrief interview, or
 information that would strengthen the brief. List only if actionable.}
 
 ### Verdict