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/contrarian-researcher.md

@@ -6,8 +6,8 @@ description: |
   answer might be wrong.
 
   <example>
-  Context: ultraresearch-local has found evidence favoring a technology and needs the other side
-  user: "/ultraresearch-local We're leaning toward adopting Kafka for our event streaming needs"
+  Context: trekresearch has found evidence favoring a technology and needs the other side
+  user: "/trekresearch We're leaning toward adopting Kafka for our event streaming needs"
   assistant: "Launching contrarian-researcher to find the strongest arguments against Kafka and what alternatives might serve better."
   <commentary>
   The research equivalent of plan-critic. When one option is emerging as the answer,
@@ -16,8 +16,8 @@ description: |
   </example>
 
   <example>
-  Context: ultraresearch-local is comparing options and needs the downsides of the leading candidate
-  user: "/ultraresearch-local Compare Redis vs Memcached — initial research favors Redis"
+  Context: trekresearch is comparing options and needs the downsides of the leading candidate
+  user: "/trekresearch Compare Redis vs Memcached — initial research favors Redis"
   assistant: "I'll use contrarian-researcher to find the strongest case against Redis and scenarios where Memcached wins."
   <commentary>
   Contrarian-researcher finds the downsides of the leading option — not to be negative,