feat(voyage): S13 — RELEASE v5.5.0 (framing 2.2 badge + NW1–NW3 + W2/W3 roll-up)

The coordinated release held since S6. Bumps 5.1.1 → 5.5.0 across plugin.json,
package.json, package-lock.json, README badge, and CHANGELOG (operator-confirmed
version; matches the codebase-wide v5.4/v5.5 milestone labels). Additive — no
breaking change for existing consumers; new brief requirements gate only on
briefs that declare brief_version 2.2.

Lands:
- brief_version 2.2 framing enforcement (framing enum + memory-alignment dim +
  obligatory TL;DR), held since S6 — badge now bumped
- Handover 1 PUBLIC CONTRACT formalization (the unreleased "v5.4")
- W2: Opus 4.8 baseline + native effort: on 8 agents + resolver model-gate fix
- W3: exec-form hooks (CC-14) + disallowed-tools on trekexecute (CC-11)
- NW1 reviewer-output schema contract; NW2 --workflow opt-in (bake-off POSITIVE);
  NW3 synthesis-agent dormant (declined per measurement)

CC 2.1.130→181 dispositions (docs/cc-upgrade-2.1.181-decision-matrix.md §S13):
- CC-08: GH#36071 (hooks in headless) CLOSED AS NOT PLANNED, not fixed →
  in-prompt safety preamble retained
- CC-29/31: verified clean / aligned, no code change
- CC-07/12/13: DEFER confirmed (recorded, no code)
- CLAUDE.md root warning: ACCEPTED BY DESIGN (universal across marketplace,
  advisory only; repo/maintainer context, not shipped consumer context)

TDD: version-consistency + v5.5.0-entry tests added first (RED→GREEN).
Tests 695 → 697 (695 pass / 2 skip / 0 fail). `claude plugin validate` passes
(one accepted advisory warning).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LqBYc8Ltrk7LipyJmGxXiB

docs/cc-upgrade-2.1.181-decision-matrix.md

@@ -195,6 +195,52 @@ prose-vs-Workflow bake-off was specified but **not run**.
   design (thresholds POSITIVE/NEGATIVE/INCONCLUSIVE), §6 no-Workflow schema-contract PoC, all ready
   to run if the operator greenlights tier 1 and/or tier 2.
 
+## S13 resolutions (RELEASE — 2026-06-18, operator-gated)
+
+S13 is the coordinated release that lands everything accumulated since `v5.1.1`: the
+`brief_version 2.2` framing badge (held since S6), the W2/W3 hardening, and the W1 narrow wins
+(NW1–NW3). Operator confirmed **two release decisions** (2026-06-18): version `5.5.0` and the
+CLAUDE.md-warning disposition (below). Shipped as **v5.5.0** — see `CHANGELOG.md`.
+
+- **Version = `5.5.0` (operator-confirmed).** The codebase already labels the framing milestone
+  `v5.5` and the contract formalization `v5.4` in ~25 test/doc sites; `5.5.0` makes those true
+  against the shipped version. Minor bump (additive — existing `2.0`/`2.1` briefs still validate;
+  new requirements gate only on briefs that *declare* `2.2`). Versions `5.2`–`5.4` were never
+  released — internal milestone labels folded into this one coordinated entry. Synced across
+  `plugin.json` + `package.json` + README badge + CHANGELOG top, guarded by a new
+  version-consistency test in `tests/lib/doc-consistency.test.mjs`.
+- **CLAUDE.md root warning — ACCEPTED BY DESIGN (operator-confirmed).** `claude plugin validate`
+  emits one advisory warning ("root: CLAUDE.md … is not loaded as project context; use a skill
+  instead"). **Verified universal** across the marketplace (`graceful-handoff` emits the identical
+  warning *even with* a `skills/` dir — adding a skill does NOT clear it). It is advisory only
+  (validation passes), and the root `CLAUDE.md` is repo/maintainer context — consumer context ships
+  via README + command/agent frontmatter. Removing it would lose in-repo project instructions and
+  break the global continuity system. Disposition recorded so future sessions do not re-chase an
+  impossible "fix"; `validate` stays "passed with warnings" as the expected steady state.
+- **CC-08 — RESOLVED: keep the safety preamble.** GH #36071 (PreToolUse hooks don't block in
+  headless `-p` mode) is **CLOSED AS NOT PLANNED, not fixed** (verified against the issue + official
+  changelog; the recent "hook deferral" feature is a workaround, not a fix to the headless
+  synchronization bug). The in-prompt safety preamble (`trekexecute.md:341`,
+  `templates/headless-launch-template.md:48`) **stays** — do not relax it on a silence-implies-fixed
+  assumption.
+- **CC-29 — VERIFIED clean (SHIP).** `subagent_type` matching is now case/separator-insensitive and
+  multiple `Agent(...)` type grants are no longer dropped. No Voyage agent declares multiple
+  `Agent(...)` types in `tools:`; `subagent_type` references (`/trekplan`'s `"Explore"`, the
+  namespaced `voyage:*` agentTypes in the trekreview Workflow port) are unaffected. Free robustness,
+  no code change.
+- **CC-31 — VERIFIED aligned (no change).** The tightened background worktree-isolation guard
+  (2.1.154) reinforces exactly Voyage's intent: isolate parallel waves. `/trekplan` uses
+  `TeamCreate isolation:"worktree"` with a documented sequential fallback when `TeamCreate` is
+  unavailable; `/trekexecute` Phase 2.6 creates/merges/cleans worktrees per wave with stale-worktree
+  cleanup. Doc-level verification (no live multi-session wave run this session); behavior consistent
+  with the guard.
+- **CC-07 / CC-12 / CC-13 — DEFER confirmed (recorded, no code).** CC-07 (`fallbackModel`) triggers
+  when `/trekexecute` Phase 2.6 launch flags are next touched. CC-12 (Stop/SubagentStop
+  `additionalContext`) and CC-13 (`background_tasks`/`session_crons` in Stop-hook input) adopt when
+  the continuity-flush / OTLP exporter is next touched. No current gap forces any of them.
+- **Final gates.** `claude plugin validate` passes (one accepted advisory warning); full `node --test`
+  green. Test count rises by the 2 new version-consistency/changelog-entry tests.
+
 ## Sequencing
 
 ```