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/examples/README.md

@@ -1,13 +1,13 @@
 # Examples
 
-Complete kalibrerte walk-throughs of the ultraplan-local pipeline for
+Complete kalibrerte walk-throughs of the trekplan pipeline for
 realistic tasks. Each example shows the four artifacts a project
 directory contains after a full run:
 
-- `brief.md` — task brief from `/ultrabrief-local`
-- `research/*.md` — research briefs from `/ultraresearch-local`
-- `plan.md` — implementation plan from `/ultraplan-local`
-- `progress.json` — execution log from `/ultraexecute-local`
+- `brief.md` — task brief from `/trekbrief`
+- `research/*.md` — research briefs from `/trekresearch`
+- `plan.md` — implementation plan from `/trekplan`
+- `progress.json` — execution log from `/trekexecute`
 
 These are **hand-calibrated**, not LLM-generated. The point is to give
 a fork-er a deterministic reference — what the artifacts look like
@@ -19,10 +19,10 @@ For your own work, point the four commands at a real project directory:
 
 ```bash
 mkdir -p .claude/projects/2026-05-01-my-task
-/ultrabrief-local
-/ultraresearch-local --project .claude/projects/2026-05-01-my-task
-/ultraplan-local --project .claude/projects/2026-05-01-my-task
-/ultraexecute-local --project .claude/projects/2026-05-01-my-task
+/trekbrief
+/trekresearch --project .claude/projects/2026-05-01-my-task
+/trekplan --project .claude/projects/2026-05-01-my-task
+/trekexecute --project .claude/projects/2026-05-01-my-task
 ```
 
 The artifacts in each example mirror that flow.