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/templates/plan-template.md

@@ -1,6 +1,6 @@
 <!--
 Optional YAML frontmatter — include ONLY when the plan was generated from a
-`type: ultrareview` input (Handover 6). Lists the 40-char hex IDs of the
+`type: trekreview` input (Handover 6). Lists the 40-char hex IDs of the
 BLOCKER + MAJOR findings consumed from `review.md`. Use block-style YAML;
 the frontmatter parser does not support flow-style arrays.
 
@@ -18,7 +18,7 @@ source_findings:
 
 > **Plan quality: {grade}** ({score}/100) — {APPROVE | APPROVE_WITH_NOTES | REVISE | REPLAN}
 >
-> Generated by ultraplan-local v{version} on {YYYY-MM-DD} — `plan_version: 1.7`
+> Generated by trekplan v{version} on {YYYY-MM-DD} — `plan_version: 1.7`
 
 ## Context
 
@@ -116,7 +116,7 @@ concrete command (e.g., run the app, check output, curl an endpoint).*
 ### Manifest — objective completion predicate
 
 Every step MUST have a Manifest block. This is the machine-checkable contract
-that ultraexecute-local verifies after the Verify command passes. A step is
+that trekexecute verifies after the Verify command passes. A step is
 not considered complete until its manifest verifies — regardless of Verify
 command exit code.
 
@@ -182,7 +182,7 @@ before execution.*
 ## Verification
 
 *Per-step manifest verification runs automatically during execution (every
-step's Manifest block is objectively checked by ultraexecute-local before the
+step's Manifest block is objectively checked by trekexecute before the
 step is marked passed). This section is for end-to-end integration checks
 that cross step boundaries — complete workflows, system-level behavior.*
 
@@ -198,7 +198,7 @@ that cross step boundaries — complete workflows, system-level behavior.*
 ## Execution Strategy
 
 *Include this section when the plan has more than 5 implementation steps.
-Omit for small plans (≤ 5 steps) — ultraexecute will run them sequentially
+Omit for small plans (≤ 5 steps) — trekexecute will run them sequentially
 in a single session.*
 
 *The execution strategy groups steps into sessions and organizes sessions