@chllming/wave-orchestration 0.8.8 → 0.8.9

package/CHANGELOG.md

@@ -2,6 +2,25 @@
 
 ## Unreleased
 
+## 0.8.9 - 2026-03-27
+
+### Changed
+
+- The current release surface now points consistently at `0.8.9`, including the README, current-state notes, migration guide, release manifest, tracked install-state fixtures, and the versioned recommendations guide `docs/guides/recommendations-0.8.9.md`.
+
+### Fixed And Hardened
+
+- Reducer snapshots now preserve design packet report paths when rebuilding summaries from result envelopes, so `designGate` no longer reopens as `missing-design-packet` after a successful design pass.
+- Launcher transitions after design-only passes now stop on the actual design-gate blocker instead of falling through to a misleading downstream implementation `missing-result-envelope` failure.
+- Trace bundle summary reconstruction now also resolves design packet report paths, so copied trace summaries stay aligned when design summaries are rebuilt from logs.
+
+### Testing And Validation
+
+- `pnpm exec vitest run --config vitest.config.ts test/wave-orchestrator/wave-state-reducer.test.ts test/wave-orchestrator/launcher.test.ts test/wave-orchestrator/traces.test.ts`
+- `pnpm test`
+- `node scripts/wave.mjs doctor --json`
+- `node scripts/wave.mjs launch --lane main --dry-run --no-dashboard`
+
 ## 0.8.8 - 2026-03-27
 
 ### Changed

package/README.md

@@ -103,18 +103,17 @@ Wave is built to mitigate those failures with a canonical authority set, generat
 
 Current release:
 
-- `@chllming/wave-orchestration@0.8.8`
-- Release tag: [`v0.8.8`](https://github.com/chllming/agent-wave-orchestrator/releases/tag/v0.8.8)
+- `@chllming/wave-orchestration@0.8.9`
+- Release tag: [`v0.8.9`](https://github.com/chllming/agent-wave-orchestrator/releases/tag/v0.8.9)
 - Public install path: npmjs
 - Authenticated fallback: GitHub Packages
 
-Highlights in `0.8.8`:
+Highlights in `0.8.9`:
 
-- The shipped starter surface now includes `skills/signal-hygiene/` plus seeded `scripts/wave-status.sh` and `scripts/wave-watch.sh` wrappers for long-running-agent and operator wait loops.
-- Long-running agents and resident orchestrators now get prompt-level signal-state and signal-ack paths, so wakeups are edge-triggered by versioned signal changes instead of relying on terminal injection.
-- Versioned wave or agent signal snapshots are now a first-class operator surface under `.tmp/<lane>-wave-launcher/signals/`, with failure treated as terminal in both the runtime and the wrapper exit contract.
-- `0.8.5` design-role and hybrid design-steward behavior remains part of the shipped release surface, and the current release line keeps the `0.8.7` capability-specific same-wave helper routing, blocker-severity consistency, and stable per-wave tmux session reuse hardening.
-- Release docs, current-state notes, migration guidance, publishing instructions, and the packaged operator recommendations guide now point at the `0.8.8` surface.
+- Reducer snapshots now preserve design packet report paths when they rebuild summaries from result envelopes, so successful design passes no longer get replayed as `missing-design-packet`.
+- Launcher transitions after design-only passes now stop on the real design-gate failure and record a design-specific blocker instead of falling through to a misleading downstream implementation `missing-result-envelope` error.
+- Trace bundle summary reconstruction now also preserves design packet report paths, so copied summary artifacts stay aligned when a trace has to rebuild a design summary from logs.
+- Release docs, current-state notes, migration guidance, publishing instructions, the packaged operator recommendations guide, and the tracked install-state fixtures now all point at the `0.8.9` surface.
 
 Requirements:
 

package/docs/README.md

@@ -36,15 +36,15 @@ The useful path is journey-first:
 - Drafting or revising waves:
   Read [guides/author-and-run-waves.md](./guides/author-and-run-waves.md), then use [plans/wave-orchestrator.md](./plans/wave-orchestrator.md) as the operator runbook.
 - Adding an optional pre-implementation design steward:
-  Read [guides/author-and-run-waves.md](./guides/author-and-run-waves.md), then the standing prompt in [agents/wave-design-role.md](./agents/wave-design-role.md). The shipped `0.8.8` surface includes `role-design` plus `tui-design`, with docs-first design stewards by default and explicit hybrid design stewards when a wave also gives that same agent code ownership.
+  Read [guides/author-and-run-waves.md](./guides/author-and-run-waves.md), then the standing prompt in [agents/wave-design-role.md](./agents/wave-design-role.md). The shipped `0.8.9` surface includes `role-design` plus `tui-design`, with docs-first design stewards by default and explicit hybrid design stewards when a wave also gives that same agent code ownership.
 - Want signal-driven automation or long-running watcher loops:
   Read [guides/signal-wrappers.md](./guides/signal-wrappers.md). It covers the seeded `wave-status.sh` and `wave-watch.sh` wrappers, the versioned signal snapshot files, and the ack-loop contract behind `signal-hygiene`.
 - Adding a security review pass:
   Read [plans/wave-orchestrator.md](./plans/wave-orchestrator.md) and the standing reviewer prompt in [agents/wave-security-role.md](./agents/wave-security-role.md).
 - Upgrading an existing repo:
   Read [plans/migration.md](./plans/migration.md), then review the release notes in [../CHANGELOG.md](../CHANGELOG.md) before running `pnpm exec wave upgrade`.
-- Want the practical `0.8.8` operating stance:
-  Read [guides/recommendations-0.8.8.md](./guides/recommendations-0.8.8.md) for the recommended default around relaxed blocker states, advisory turn budgets, and targeted recovery.
+- Want the practical `0.8.9` operating stance:
+  Read [guides/recommendations-0.8.9.md](./guides/recommendations-0.8.9.md) for the recommended default around relaxed blocker states, advisory turn budgets, and targeted recovery.
 - Want the concrete runtime module map:
   Read [plans/end-state-architecture.md](./plans/end-state-architecture.md) for the engine-by-engine architecture and artifact ownership model.
 - Want the CLI surface map:

package/docs/guides/author-and-run-waves.md

@@ -61,7 +61,7 @@ Good fits:
 - multi-owner waves where downstream implementers need the same decisions and assumptions
 - ambiguous tasks where open questions should become explicit before code owners fan out
 
-The starter contract in `0.8.8` is:
+The starter contract in `0.8.9` is:
 
 - import `docs/agents/wave-design-role.md`
 - own one packet such as `docs/plans/waves/design/wave-<n>-<agentId>.md`

package/docs/guides/planner.md

@@ -6,7 +6,7 @@ If you want the full author-to-launch workflow, start with [author-and-run-waves
 
 It reduces repeated setup questions, stores project defaults, and generates wave specs plus markdown that already fit the launcher.
 
-The published `0.8.8` package already includes the optional `design` worker role for pre-implementation design packets. This guide calls out where that affects drafting.
+The published `0.8.9` package already includes the optional `design` worker role for pre-implementation design packets. This guide calls out where that affects drafting.
 
 ## What Ships Today
 

package/docs/guides/{recommendations-0.8.8.md → recommendations-0.8.9.md}

@@ -1,15 +1,15 @@
 ---
-title: "0.8.8 Recommendations"
-summary: "How to use 0.8.8's softer blocker states, advisory turn budgets, and targeted recovery without weakening proof and closure."
+title: "0.8.9 Recommendations"
+summary: "How to use 0.8.9's softer blocker states, advisory turn budgets, and targeted recovery without weakening proof and closure."
 ---
 
-# 0.8.8 Recommendations
+# 0.8.9 Recommendations
 
-Use this guide when you are adopting `0.8.8` and want one practical operating stance for the softer blocker states, advisory turn-budget behavior, and targeted recovery flow that the current package line ships.
+Use this guide when you are adopting `0.8.9` and want one practical operating stance for the softer blocker states, advisory turn-budget behavior, and targeted recovery flow that the current package line ships.
 
 ## Recommended Default
 
-For most repos, the safest `0.8.8` default is:
+For most repos, the safest `0.8.9` default is:
 
 - bound work with `budget.minutes`
 - leave generic `budget.turns` as advisory metadata
@@ -75,7 +75,7 @@ Only set a hard runtime ceiling when you deliberately want the runtime itself to
 
 ## 2. Softer Coordination States
 
-`0.8.8` keeps “still visible” separate from “still blocking”.
+`0.8.9` keeps “still visible” separate from “still blocking”.
 
 Use these states intentionally:
 
@@ -111,7 +111,7 @@ If the current wave cannot truthfully close without the answer, keep it blocking
 
 ## 4. Recovery Recommendation
 
-My recommendation after reviewing the current `0.8.8` code path is:
+My recommendation after reviewing the current `0.8.9` code path is:
 
 - let timeout, max-turn, rate-limit, and missing-status failures go through the built-in targeted recovery path first
 - inspect the queued rerun or resume request before manually relaunching the whole wave

package/docs/plans/current-state.md

@@ -1,10 +1,10 @@
 # Current State
 
-- The published package is `0.8.8`, and that release now includes the optional pre-implementation `design` worker role, the `role-design`, `tui-design`, and `signal-hygiene` starter bundles, plus the seeded signal-wrapper scripts for long-running-agent and operator wait loops.
+- The published package is `0.8.9`; that release keeps the shipped design-role and signal-hygiene starter surface, preserves design packet report paths during reducer and trace summary reconstruction, and reports blocked design passes as design-gate failures before implementation starts.
 - The canonical shipped runtime architecture is documented in `docs/plans/end-state-architecture.md`; historical cutover notes remain in `docs/plans/architecture-hardening-migration.md`.
 - The repository contains the published `@chllming/wave-orchestration` package plus the starter scaffold used by `wave init`.
 - The runtime is package-first and non-destructive for adopting repos: `wave init --adopt-existing` records existing repo-owned plans, waves, prompts, and config without overwriting them, and `wave upgrade` writes only `.wave/install-state.json` plus `.wave/upgrade-history/`.
-- The recommended `0.8.8` operating stance is documented in `docs/guides/recommendations-0.8.8.md`: keep proof and closure strict, keep generic `budget.turns` advisory, and use softer coordination states only for non-proof follow-up.
+- The recommended `0.8.9` operating stance is documented in `docs/guides/recommendations-0.8.9.md`: keep proof and closure strict, keep generic `budget.turns` advisory, and use softer coordination states only for non-proof follow-up.
 - Runtime launch entrypoints now perform a best-effort npmjs version check, cache the result under `.wave/package-update-check.json`, and point operators at `pnpm exec wave self-update` when a newer published package exists.
 - This source repo is itself kept as an adopted Wave workspace, so `node scripts/wave.mjs doctor --json` should pass from the repo root.
 - The default lane is `main`.

package/docs/plans/end-state-architecture.md

@@ -1,6 +1,6 @@
 # End-State Architecture
 
-This document describes the canonical architecture for the current Wave runtime. It is the authoritative reference for the engine boundaries, canonical authority set, and artifact ownership model that the shipped `0.8.8` surface now follows.
+This document describes the canonical architecture for the current Wave runtime. It is the authoritative reference for the engine boundaries, canonical authority set, and artifact ownership model that the shipped `0.8.9` surface now follows.
 
 The thesis is unchanged: bounded waves, closure roles, proof artifacts, selective rerun, and delivery discipline. What changes is the internal authority model. The launcher stops being the decision engine and becomes a thin orchestrator that reads decisions from canonical state, sequences the engines, and delegates process work to the session supervisor.
 

package/docs/plans/examples/wave-example-design-handoff.md

@@ -1,6 +1,6 @@
 # Wave 12 - Optional Design Steward Handoff
 
-This is a showcase-first sample wave for the shipped `design` worker role in `0.8.8`.
+This is a showcase-first sample wave for the shipped `design` worker role in `0.8.9`.
 
 This example demonstrates the docs-first design-steward path where a design packet is published before code-owning implementation begins.
 

package/docs/plans/examples/wave-example-live-proof.md

@@ -2,7 +2,7 @@
 
 This is a showcase-first sample wave.
 
-Use it as the single reference example for the current `0.8.8` Wave surface.
+Use it as the single reference example for the current `0.8.9` Wave surface.
 
 It intentionally combines more sections than a normal production wave so one file can demonstrate:
 

package/docs/plans/migration.md

@@ -1,6 +1,6 @@
 # Migration
 
-This page is the practical repo-upgrade guide for the current `0.8.8` surface.
+This page is the practical repo-upgrade guide for the current `0.8.9` surface.
 
 Use it when you are:
 
@@ -10,20 +10,20 @@ Use it when you are:
 
 For the completed internal architecture cutover record, see [architecture-hardening-migration.md](./architecture-hardening-migration.md). That document is historical. This one is the operator-facing upgrade checklist.
 
-## What `0.8.8` Changes
+## What `0.8.9` Changes
 
-The current `0.8.8` surface keeps the `0.8.7` policy-consistency and stable per-wave session reuse hardening, and now also packages the operator recommendations guide and install-state alignment follow-up in the release itself.
+The current `0.8.9` surface keeps the `0.8.8` packaged operator-guidance alignment and adds a focused repair for design-pass replay and post-design transition handling.
 
 The practical changes are:
 
-- generic `budget.turns` stays advisory metadata unless the runtime-specific ceiling is set explicitly with `claude.maxTurns` or `opencode.steps`
-- capability-targeted helper routing now treats demonstrated same-wave success as capability-specific evidence; unrelated completed work no longer makes an agent the preferred helper owner
-- advisory or stale clarification and human-input records remain visible in coordination history and reducer blocker views, but they no longer reopen `clarifying` or blocked reducer state by themselves
-- wave-agent and resident-orchestrator tmux sessions now reuse stable per-wave session names, so relaunches and stale launcher exits stop accumulating extra tmux sessions for the same wave
+- reducer snapshots now preserve design packet report paths when they rebuild summaries from result envelopes
+- blocked design passes now stop at the design gate instead of being surfaced later as downstream implementation envelope failures
+- trace bundle summary reconstruction now also resolves design packet report paths, so copied design summaries stay aligned when they are rebuilt from logs
+- the current release surface and tracked install-state fixtures now all move together on `0.8.9`
 
-If your repo copied starter docs, shell automation, or operator runbooks, these are the areas most likely to need a sync before the `0.8.8` package cut.
+If your repo copied starter docs, shell automation, or operator runbooks, these are the areas most likely to need a sync before the `0.8.9` package cut.
 
-For a practical `0.8.8` operating stance after the upgrade, read [../guides/recommendations-0.8.8.md](../guides/recommendations-0.8.8.md).
+For a practical `0.8.9` operating stance after the upgrade, read [../guides/recommendations-0.8.9.md](../guides/recommendations-0.8.9.md).
 
 ## What `0.8.6` Changes
 
@@ -138,14 +138,14 @@ pnpm exec wave coord inbox --lane main --wave 0 --agent A1 --dry-run
 
 Use `pnpm exec wave dashboard --lane <lane> --attach current` or `--attach global` when you need to reattach to a tmux-backed dashboard after the upgrade.
 
-## `0.8.8` Release Model
+## `0.8.9` Release Model
 
-The current `0.8.8` surface is three changes together:
+The current `0.8.9` surface is three changes together:
 
 - the shipped `design` worker role and hybrid design-steward flow introduced in `0.8.5`
 - the signal-driven long-running-agent and wrapper model introduced in `0.8.6`
 - the policy-consistency, targeted-recovery, capability-specific routing, and stable per-wave session reuse hardening introduced in `0.8.7`
-- the packaged recommendations guide and install-state alignment follow-up released in `0.8.8`
+- the packaged recommendations guide and install-state alignment follow-up released in `0.8.9`
 
 ### Signal-driven waiting and wrapper model
 
@@ -329,9 +329,9 @@ If the repo copied starter `wave.config.json` defaults, also sync:
 - if the repo uses hybrid design stewards, confirm the same agent rejoins implementation only when the authored wave explicitly gives it code ownership
 - if the repo uses long-running agents or shell automation, confirm the new wrapper exit contract and ack-loop semantics before relying on an older polling script
 
-## Upgrading From `0.8.3` To `0.8.8`
+## Upgrading From `0.8.3` To `0.8.9`
 
-Treat this as one move to the current `0.8.8` surface.
+Treat this as one move to the current `0.8.9` surface.
 
 ### What changed across that range
 
@@ -364,7 +364,7 @@ If your repo copied starter docs or skills, sync:
 - dry-run one design-steward wave if the repo wants the new authored surface
 - if the repo uses long-running watcher agents or shell automation, validate `scripts/wave-status.sh` and `scripts/wave-watch.sh` against a live or staged lane
 
-## Upgrading From `0.6.x` Or `0.7.x` To `0.8.8`
+## Upgrading From `0.6.x` Or `0.7.x` To `0.8.9`
 
 This is the main migration path for older adopted repos.
 
@@ -405,7 +405,7 @@ pnpm exec wave control proof get --lane main --wave 0 --json
 
 If the repo carries proof-first waves, verify that required proof artifacts still exist locally and not only in historical summaries.
 
-## Upgrading From `0.5.x` Or Earlier To `0.8.8`
+## Upgrading From `0.5.x` Or Earlier To `0.8.9`
 
 Do not treat this as a tiny patch bump.
 
@@ -515,4 +515,4 @@ For repos that depend on replay parity, replay at least:
 
 ## Summary
 
-The current `0.8.8` surface keeps the same authority-set and phase-engine architecture, ships both the design-role starter surface and the signal-driven long-running-agent starter surface, keeps the `0.8.7` policy and routing hardening, and now also packages the practical operator recommendations guide inside the release line. For most repos already on `0.8.x`, the upgrade is package bump plus validation. For older adopted repos, the real work is syncing repo-owned prompts, skills, planner corpus, wrapper scripts, and runbooks so they describe the runtime the package now ships.
+The current `0.8.9` surface keeps the same authority-set and phase-engine architecture, ships both the design-role starter surface and the signal-driven long-running-agent starter surface, keeps the `0.8.7` policy and routing hardening, and now also packages the practical operator recommendations guide inside the release line. For most repos already on `0.8.x`, the upgrade is package bump plus validation. For older adopted repos, the real work is syncing repo-owned prompts, skills, planner corpus, wrapper scripts, and runbooks so they describe the runtime the package now ships.

package/docs/reference/cli-reference.md

@@ -561,7 +561,7 @@ Interactive draft currently offers worker role kinds:
 - `research`
 - `security`
 
-Agentic planner payloads also accept `workerAgents[].roleKind = "design"`. The shipped `0.8.8` surface uses `design-pass` as the default executor profile for that role and typically assigns a packet path like `docs/plans/waves/design/wave-<n>-<agentId>.md`. Interactive draft scaffolds the docs-first default; hybrid design stewards are authored by explicitly adding implementation-owned paths and the normal implementation contract sections.
+Agentic planner payloads also accept `workerAgents[].roleKind = "design"`. The shipped `0.8.9` surface uses `design-pass` as the default executor profile for that role and typically assigns a packet path like `docs/plans/waves/design/wave-<n>-<agentId>.md`. Interactive draft scaffolds the docs-first default; hybrid design stewards are authored by explicitly adding implementation-owned paths and the normal implementation contract sections.
 
 ## Ad-Hoc Task Commands
 

package/docs/reference/coordination-and-closure.md

@@ -134,7 +134,7 @@ Practical rule:
 
 That means a targeted helper request only blocks while it remains open *and* still has blocking severity in coordination state.
 
-For the practical `0.8.8` recommendation on when to keep records blocking versus when to downgrade them to `soft`, `stale`, or `advisory`, see [../guides/recommendations-0.8.8.md](../guides/recommendations-0.8.8.md).
+For the practical `0.8.9` recommendation on when to keep records blocking versus when to downgrade them to `soft`, `stale`, or `advisory`, see [../guides/recommendations-0.8.9.md](../guides/recommendations-0.8.9.md).
 
 This page is documenting runtime semantics first. The important contract is that closure follows the durable coordination state, not that a particular human or agent used one exact command path to mutate it.
 

package/docs/reference/npmjs-trusted-publishing.md

@@ -2,7 +2,7 @@
 
 This repo now includes a dedicated npmjs publish workflow at [publish-npm.yml](../../.github/workflows/publish-npm.yml).
 
-The current `0.8.8` release procedure publishes through a repository Actions secret named `NPM_TOKEN`.
+The current `0.8.9` release procedure publishes through a repository Actions secret named `NPM_TOKEN`.
 
 ## What This Repo Already Does
 
@@ -48,6 +48,6 @@ If this repo later needs private npm dependencies during CI, consider a separate
 2. Confirm `NPM_TOKEN` exists in the GitHub repo secrets.
 3. Confirm the package version has been bumped and committed.
 4. Confirm `README.md`, `CHANGELOG.md`, `releases/manifest.json`, and `docs/plans/migration.md` all describe the same release surface.
-5. Push the release commit and release tag, for example `v0.8.8`.
+5. Push the release commit and release tag, for example `v0.8.9`.
 6. Verify both `publish-npm.yml` and `publish-package.yml` start from the tag push.
 7. Verify the npmjs publish completes successfully for the tagged source.

package/docs/reference/runtime-config/README.md

@@ -74,7 +74,7 @@ Practical guidance:
 - prefer `budget.minutes` for normal synthesis, integration, and closure work
 - use generic `budget.turns` as a planning hint, not a hard failure trigger
 - only set `claude.maxTurns` or `opencode.steps` when you deliberately want a hard ceiling for that runtime
-- see [../../guides/recommendations-0.8.8.md](../../guides/recommendations-0.8.8.md) for the recommended `0.8.8` operating stance that combines advisory turn budgets with softer non-proof coordination states
+- see [../../guides/recommendations-0.8.9.md](../../guides/recommendations-0.8.9.md) for the recommended `0.8.9` operating stance that combines advisory turn budgets with softer non-proof coordination states
 
 ## Runtime Pages
 

package/docs/reference/sample-waves.md

@@ -1,11 +1,11 @@
 ---
 title: "Sample Waves"
-summary: "Showcase-first sample waves that demonstrate the shipped 0.8.8 authored surface, including the optional design-role path."
+summary: "Showcase-first sample waves that demonstrate the shipped 0.8.9 authored surface, including the optional design-role path."
 ---
 
 # Sample Waves
 
-This guide points to showcase-first sample waves that demonstrate the shipped `0.8.8` authored Wave surface.
+This guide points to showcase-first sample waves that demonstrate the shipped `0.8.9` authored Wave surface.
 
 The examples are intentionally denser than typical production waves. Their job is to teach the current authoring and runtime surface quickly, not to be the smallest possible launch-ready files.
 
@@ -15,7 +15,7 @@ The examples are intentionally denser than typical production waves. Their job i
   Shows what a good `repo-landed` outcome looks like when one promoted component only closes honestly if desired-state records, reconcile-loop substrate, and cluster-view surfaces land together. It emphasizes maturity discipline, explicit deliverables, and shared-plan closure without drifting into `pilot-live` claims.
 
 - [Full modern sample wave](../plans/examples/wave-example-live-proof.md)
-  Shows the combined `0.8.8` authored surface in one file: closure roles, `E0`, optional security review, delegated and pinned benchmark targets, richer executor config, `### Skills`, `### Capabilities`, `### Deliverables`, `### Exit contract`, `### Proof artifacts`, sticky retry, deploy environments, and proof-first live-wave structure.
+  Shows the combined `0.8.9` authored surface in one file: closure roles, `E0`, optional security review, delegated and pinned benchmark targets, richer executor config, `### Skills`, `### Capabilities`, `### Deliverables`, `### Exit contract`, `### Proof artifacts`, sticky retry, deploy environments, and proof-first live-wave structure.
 
 - [Optional design-steward handoff wave](../plans/examples/wave-example-design-handoff.md)
   Shows the shipped design-role surface: one pre-implementation design steward publishes a design packet, downstream implementation owners read that packet before coding, and normal closure roles still decide final completion. For terminal or operator-surface work, pair that shape with explicit `tui-design` in the design steward's `### Skills`. For the hybrid variant, explicitly give that same design agent implementation-owned paths and the normal implementation contract sections.
@@ -42,7 +42,7 @@ The examples are intentionally denser than typical production waves. Their job i
 
 ## Feature Coverage Map
 
-Together these samples cover the main surfaces added or hardened through `0.8.8`:
+Together these samples cover the main surfaces added or hardened through `0.8.9`:
 
 - repo-landed maturity discipline and anti-overclaim framing
 - explicit shared-plan closure for future-wave safety
@@ -89,7 +89,7 @@ Adapt more aggressively when:
 ## Suggested Reading Order
 
 1. Start with [High-fidelity repo-landed rollout wave](../plans/examples/wave-example-rollout-fidelity.md) if you want the clearest example of good closure-ready wave fidelity for a repo-only outcome.
-2. Read [Full modern sample wave](../plans/examples/wave-example-live-proof.md) if you want the denser proof-first and eval-heavy `0.8.8` surface.
+2. Read [Full modern sample wave](../plans/examples/wave-example-live-proof.md) if you want the denser proof-first and eval-heavy `0.8.9` surface.
 3. Read [Optional design-steward handoff wave](../plans/examples/wave-example-design-handoff.md) if the task needs a design packet before implementation fan-out.
 4. Read [docs/evals/README.md](../evals/README.md) if you want more background on benchmark target selection.
 5. Read [docs/reference/live-proof-waves.md](./live-proof-waves.md) if you want more detail on proof-first `pilot-live` authoring.

package/docs/reference/skills.md

@@ -124,7 +124,7 @@ Top-level and lane-local skill attachment use the same shape:
 
 Lane-local `lanes.<lane>.skills` extends the global config instead of replacing it.
 
-Optional design workers in the shipped `0.8.8` surface normally attach `role-design`. That bundle is intended for docs/spec-first design packets and explicit implementation handoff work before implementation starts. When the design packet covers terminal UX, dashboards, or other operator surfaces, add `tui-design` explicitly in the wave's `### Skills`.
+Optional design workers in the shipped `0.8.9` surface normally attach `role-design`. That bundle is intended for docs/spec-first design packets and explicit implementation handoff work before implementation starts. When the design packet covers terminal UX, dashboards, or other operator surfaces, add `tui-design` explicitly in the wave's `### Skills`.
 
 Long-running agents that should stay resident and react only to orchestrator signal changes can add `signal-hygiene` explicitly in `### Skills`. That bundle is not auto-attached and is not meant for normal one-shot implementation agents.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chllming/wave-orchestration",
-  "version": "0.8.8",
+  "version": "0.8.9",
   "license": "MIT",
   "description": "Generic wave-based multi-agent orchestration for repository work.",
   "repository": {

package/releases/manifest.json

@@ -2,6 +2,24 @@
   "schemaVersion": 1,
   "packageName": "@chllming/wave-orchestration",
   "releases": [
+    {
+      "version": "0.8.9",
+      "date": "2026-03-27",
+      "summary": "Design-gate report-path preservation, accurate post-design failure reporting, trace-summary alignment, and 0.8.9 release-surface sync.",
+      "features": [
+        "Reducer snapshots now preserve design packet report paths when rebuilding summaries from result envelopes, so `designGate` no longer reopens as `missing-design-packet` after a successful design pass.",
+        "Launcher transitions after design-only passes now stop on the actual design-gate blocker and record a design-specific blocker instead of falling through to a misleading downstream implementation `missing-result-envelope` error.",
+        "Trace bundle summary reconstruction now also resolves design packet report paths, so copied trace summaries stay aligned when design summaries are rebuilt from logs.",
+        "README, current-state notes, migration guidance, release manifest, tracked install-state fixtures, and the versioned recommendations guide now all point at the `0.8.9` package surface.",
+        "Planner migration guidance and the `planner-agentic` bundle placeholder remain part of the shipped current-surface docs so adopted repos still have one aligned upgrade target."
+      ],
+      "manualSteps": [
+        "Run `pnpm exec wave doctor` and `pnpm exec wave launch --lane main --dry-run --no-dashboard` after upgrading so the repo validates against the `0.8.9` release surface.",
+        "If your repo copied current-surface docs or runbooks, sync `README.md`, `docs/README.md`, `docs/plans/current-state.md`, `docs/plans/migration.md`, `docs/reference/coordination-and-closure.md`, `docs/reference/runtime-config/README.md`, and `docs/guides/recommendations-0.8.9.md` so local guidance matches the packaged release.",
+        "If your repo copied trace or replay helpers around design packets, sync the updated reducer, launcher, and trace-summary reconstruction behavior before relying on rebuilt design summaries in replay tooling."
+      ],
+      "breaking": false
+    },
     {
       "version": "0.8.8",
       "date": "2026-03-27",

package/scripts/wave-orchestrator/launcher.mjs

@@ -500,6 +500,49 @@ function buildGateSnapshot(params) {
   });
 }
 
+export function resolvePostDesignPassTransition({
+  waveNumber,
+  designGate,
+  remainingImplementationRuns,
+  currentRuns,
+  fallbackLogPath = null,
+}) {
+  const nextRuns = Array.isArray(remainingImplementationRuns) ? remainingImplementationRuns : [];
+  if (designGate?.ok && nextRuns.length > 0) {
+    const nextAgentIds = nextRuns.map((run) => run.agent.agentId);
+    return {
+      kind: "continue-implementation",
+      nextRuns,
+      attemptDetail: `Design pass complete; continuing with implementation agents ${nextAgentIds.join(", ")}.`,
+      eventMessage: `Design pass complete; launching implementation agents next: ${nextAgentIds.join(", ")}.`,
+      coordinationDetails: `next_agents=${nextAgentIds.join(",")}`,
+    };
+  }
+  if (!designGate?.ok) {
+    const currentAgentIds = (Array.isArray(currentRuns) ? currentRuns : []).map((run) => run.agent.agentId);
+    const blockedAgentId = designGate?.agentId || currentAgentIds[0] || null;
+    const detail =
+      designGate?.detail ||
+      `Design gate blocked wave ${waveNumber}; implementation did not start.`;
+    return {
+      kind: "blocked",
+      failure: {
+        agentId: blockedAgentId,
+        statusCode: designGate?.statusCode || "design-gate-blocked",
+        detail,
+        logPath: designGate?.logPath || fallbackLogPath,
+      },
+      eventMessage: `Design gate blocked wave ${waveNumber}: ${detail}`,
+      coordinationDetails:
+        `agent=${blockedAgentId || "unknown"}; reason=${designGate?.statusCode || "design-gate-blocked"}; ${detail}`,
+    };
+  }
+  return {
+    kind: "no-op",
+    nextRuns,
+  };
+}
+
 function waveGateLabel(gateName) {
   switch (gateName) {
     case "designGate":
@@ -1650,22 +1693,29 @@ export async function runLauncherCli(argv) {
                   !isClosureRoleAgentId(run.agent.agentId, roleBindings) &&
                   (!isDesignAgent(run.agent) || isImplementationOwningDesignAgent(run.agent)),
               );
-              if (designGate?.ok && remainingImplementationRuns.length > 0) {
+              const postDesignTransition = resolvePostDesignPassTransition({
+                waveNumber: wave.wave,
+                designGate,
+                remainingImplementationRuns,
+                currentRuns: runsToLaunch,
+                fallbackLogPath: path.relative(REPO_ROOT, messageBoardPath),
+              });
+              if (postDesignTransition.kind === "continue-implementation") {
                 recordAttemptState(lanePaths, wave.wave, attempt, "completed", {
                   selectedAgentIds: runsToLaunch.map((run) => run.agent.agentId),
-                  detail: `Design pass complete; continuing with implementation agents ${remainingImplementationRuns.map((run) => run.agent.agentId).join(", ")}.`,
+                  detail: postDesignTransition.attemptDetail,
                 });
                 recordCombinedEvent({
-                  message: `Design pass complete; launching implementation agents next: ${remainingImplementationRuns.map((run) => run.agent.agentId).join(", ")}.`,
+                  message: postDesignTransition.eventMessage,
                 });
                 appendCoordination({
                   event: "wave_design_ready",
                   waves: [wave.wave],
                   status: "running",
-                  details: `next_agents=${remainingImplementationRuns.map((run) => run.agent.agentId).join(",")}`,
+                  details: postDesignTransition.coordinationDetails,
                   actionRequested: "None",
                 });
-                runsToLaunch = remainingImplementationRuns;
+                runsToLaunch = postDesignTransition.nextRuns;
                 for (const run of runsToLaunch) {
                   setWaveDashboardAgent(dashboardState, run.agent.agentId, {
                     state: "pending",
@@ -1677,139 +1727,156 @@ export async function runLauncherCli(argv) {
                 traceAttempt += 1;
                 continue;
               }
+              if (postDesignTransition.kind === "blocked") {
+                failures = [postDesignTransition.failure];
+                recordCombinedEvent({
+                  level: "error",
+                  agentId: postDesignTransition.failure.agentId,
+                  message: postDesignTransition.eventMessage,
+                });
+                appendCoordination({
+                  event: "wave_gate_blocked",
+                  waves: [wave.wave],
+                  status: "blocked",
+                  details: postDesignTransition.coordinationDetails,
+                  actionRequested: `Lane ${lanePaths.lane} owners should resolve the design packet gap before implementation starts.`,
+                });
+              }
             }
-            const implementationGate = readWaveImplementationGate(wave, agentRuns);
-            if (!implementationGate.ok) {
-              failures = [
-                {
-                  agentId: implementationGate.agentId,
-                  statusCode: implementationGate.statusCode,
-                  logPath: implementationGate.logPath || path.relative(REPO_ROOT, messageBoardPath),
-                },
-              ];
-              recordCombinedEvent({
-                level: "error",
-                agentId: implementationGate.agentId,
-                message: `Implementation exit contract blocked wave ${wave.wave}: ${implementationGate.detail}`,
-              });
-              appendCoordination({
-                event: "wave_gate_blocked",
-                waves: [wave.wave],
-                status: "blocked",
-                details: `agent=${implementationGate.agentId}; reason=${implementationGate.statusCode}; ${implementationGate.detail}`,
-                actionRequested: `Lane ${lanePaths.lane} owners should resolve the implementation contract gap before wave progression.`,
-              });
-            } else {
-              const componentGate = readWaveComponentGate(wave, agentRuns, {
-                laneProfile: lanePaths.laneProfile,
-                mode: "live",
-              });
-              if (!componentGate.ok) {
-                if (componentGate.statusCode === "shared-component-sibling-pending") {
-                  applySharedComponentWaitStateToDashboard(componentGate, dashboardState);
-                }
+            if (failures.length === 0) {
+              const implementationGate = readWaveImplementationGate(wave, agentRuns);
+              if (!implementationGate.ok) {
                 failures = [
                   {
-                    agentId: componentGate.agentId,
-                    statusCode: componentGate.statusCode,
-                    logPath:
-                      componentGate.logPath || path.relative(REPO_ROOT, messageBoardPath),
-                    detail: componentGate.detail,
-                    ownerAgentIds: componentGate.ownerAgentIds || [],
-                    satisfiedAgentIds: componentGate.satisfiedAgentIds || [],
-                    waitingOnAgentIds: componentGate.waitingOnAgentIds || [],
-                    failedOwnContractAgentIds: componentGate.failedOwnContractAgentIds || [],
+                    agentId: implementationGate.agentId,
+                    statusCode: implementationGate.statusCode,
+                    logPath: implementationGate.logPath || path.relative(REPO_ROOT, messageBoardPath),
                   },
                 ];
                 recordCombinedEvent({
                   level: "error",
-                  agentId: componentGate.agentId,
-                  message: `Component promotion blocked wave ${wave.wave}: ${componentGate.detail}`,
+                  agentId: implementationGate.agentId,
+                  message: `Implementation exit contract blocked wave ${wave.wave}: ${implementationGate.detail}`,
                 });
                 appendCoordination({
                   event: "wave_gate_blocked",
                   waves: [wave.wave],
                   status: "blocked",
-                  details: `component=${componentGate.componentId || "unknown"}; reason=${componentGate.statusCode}; ${componentGate.detail}`,
-                  actionRequested: `Lane ${lanePaths.lane} owners should close the component promotion gap before wave progression.`,
+                  details: `agent=${implementationGate.agentId}; reason=${implementationGate.statusCode}; ${implementationGate.detail}`,
+                  actionRequested: `Lane ${lanePaths.lane} owners should resolve the implementation contract gap before wave progression.`,
                 });
-              } else if (launchedImplementationRuns.length > 0) {
-                const reducerDecision = refreshReducerSnapshot(attempt);
-                const helperAssignmentBarrier =
-                  reducerDecision?.reducerState?.gateSnapshot?.helperAssignmentBarrier ||
-                  readWaveAssignmentBarrier(derivedState);
-                const dependencyBarrier =
-                  reducerDecision?.reducerState?.gateSnapshot?.dependencyBarrier ||
-                  readWaveDependencyBarrier(derivedState);
-                if (!helperAssignmentBarrier.ok) {
-                  failures = [
-                    {
-                      agentId: null,
-                      statusCode: helperAssignmentBarrier.statusCode,
-                      logPath: path.relative(REPO_ROOT, messageBoardPath),
-                      detail: helperAssignmentBarrier.detail,
-                    },
-                  ];
-                  recordCombinedEvent({
-                    level: "error",
-                    message: `Helper assignment barrier blocked wave ${wave.wave}: ${helperAssignmentBarrier.detail}`,
-                  });
-                  appendCoordination({
-                    event: "wave_gate_blocked",
-                    waves: [wave.wave],
-                    status: "blocked",
-                    details: `reason=${helperAssignmentBarrier.statusCode}; ${helperAssignmentBarrier.detail}`,
-                    actionRequested: `Lane ${lanePaths.lane} owners should resolve helper assignments before closure.`,
-                  });
-                } else if (!dependencyBarrier.ok) {
+              } else {
+                const componentGate = readWaveComponentGate(wave, agentRuns, {
+                  laneProfile: lanePaths.laneProfile,
+                  mode: "live",
+                });
+                if (!componentGate.ok) {
+                  if (componentGate.statusCode === "shared-component-sibling-pending") {
+                    applySharedComponentWaitStateToDashboard(componentGate, dashboardState);
+                  }
                   failures = [
                     {
-                      agentId: null,
-                      statusCode: dependencyBarrier.statusCode,
-                      logPath: path.relative(REPO_ROOT, messageBoardPath),
-                      detail: dependencyBarrier.detail,
+                      agentId: componentGate.agentId,
+                      statusCode: componentGate.statusCode,
+                      logPath:
+                        componentGate.logPath || path.relative(REPO_ROOT, messageBoardPath),
+                      detail: componentGate.detail,
+                      ownerAgentIds: componentGate.ownerAgentIds || [],
+                      satisfiedAgentIds: componentGate.satisfiedAgentIds || [],
+                      waitingOnAgentIds: componentGate.waitingOnAgentIds || [],
+                      failedOwnContractAgentIds: componentGate.failedOwnContractAgentIds || [],
                     },
                   ];
                   recordCombinedEvent({
                     level: "error",
-                    message: `Dependency barrier blocked wave ${wave.wave}: ${dependencyBarrier.detail}`,
+                    agentId: componentGate.agentId,
+                    message: `Component promotion blocked wave ${wave.wave}: ${componentGate.detail}`,
                   });
                   appendCoordination({
                     event: "wave_gate_blocked",
                     waves: [wave.wave],
                     status: "blocked",
-                    details: `reason=${dependencyBarrier.statusCode}; ${dependencyBarrier.detail}`,
-                    actionRequested: `Lane ${lanePaths.lane} owners should resolve required dependency tickets before closure.`,
+                    details: `component=${componentGate.componentId || "unknown"}; reason=${componentGate.statusCode}; ${componentGate.detail}`,
+                    actionRequested: `Lane ${lanePaths.lane} owners should close the component promotion gap before wave progression.`,
                   });
+                } else if (launchedImplementationRuns.length > 0) {
+                  const reducerDecision = refreshReducerSnapshot(attempt);
+                  const helperAssignmentBarrier =
+                    reducerDecision?.reducerState?.gateSnapshot?.helperAssignmentBarrier ||
+                    readWaveAssignmentBarrier(derivedState);
+                  const dependencyBarrier =
+                    reducerDecision?.reducerState?.gateSnapshot?.dependencyBarrier ||
+                    readWaveDependencyBarrier(derivedState);
+                  if (!helperAssignmentBarrier.ok) {
+                    failures = [
+                      {
+                        agentId: null,
+                        statusCode: helperAssignmentBarrier.statusCode,
+                        logPath: path.relative(REPO_ROOT, messageBoardPath),
+                        detail: helperAssignmentBarrier.detail,
+                      },
+                    ];
+                    recordCombinedEvent({
+                      level: "error",
+                      message: `Helper assignment barrier blocked wave ${wave.wave}: ${helperAssignmentBarrier.detail}`,
+                    });
+                    appendCoordination({
+                      event: "wave_gate_blocked",
+                      waves: [wave.wave],
+                      status: "blocked",
+                      details: `reason=${helperAssignmentBarrier.statusCode}; ${helperAssignmentBarrier.detail}`,
+                      actionRequested: `Lane ${lanePaths.lane} owners should resolve helper assignments before closure.`,
+                    });
+                  } else if (!dependencyBarrier.ok) {
+                    failures = [
+                      {
+                        agentId: null,
+                        statusCode: dependencyBarrier.statusCode,
+                        logPath: path.relative(REPO_ROOT, messageBoardPath),
+                        detail: dependencyBarrier.detail,
+                      },
+                    ];
+                    recordCombinedEvent({
+                      level: "error",
+                      message: `Dependency barrier blocked wave ${wave.wave}: ${dependencyBarrier.detail}`,
+                    });
+                    appendCoordination({
+                      event: "wave_gate_blocked",
+                      waves: [wave.wave],
+                      status: "blocked",
+                      details: `reason=${dependencyBarrier.statusCode}; ${dependencyBarrier.detail}`,
+                      actionRequested: `Lane ${lanePaths.lane} owners should resolve required dependency tickets before closure.`,
+                    });
+                  } else {
+                    recordCombinedEvent({
+                      message: `Implementation pass complete; running closure sweep for ${wave.wave}.`,
+                    });
+                    const closureResult = await runClosureSweepPhase({
+                      lanePaths,
+                      wave,
+                      closureRuns: agentRuns.filter((run) =>
+                        isClosureRoleAgentId(run.agent.agentId, roleBindings),
+                      ),
+                      coordinationLogPath: derivedState.coordinationLogPath,
+                      refreshDerivedState,
+                      dashboardState,
+                      recordCombinedEvent,
+                      flushDashboards,
+                      options,
+                      feedbackStateByRequestId,
+                      appendCoordination,
+                    });
+                    failures = closureResult.failures;
+                    timedOut = timedOut || closureResult.timedOut;
+                    materializeAgentExecutionSummaries(wave, agentRuns);
+                    failures = annotateFailuresWithRecoveryHints(failures, agentRuns);
+                    refreshDerivedState(attempt);
+                  }
                 } else {
                   recordCombinedEvent({
-                    message: `Implementation pass complete; running closure sweep for ${wave.wave}.`,
-                  });
-                  const closureResult = await runClosureSweepPhase({
-                    lanePaths,
-                    wave,
-                    closureRuns: agentRuns.filter((run) =>
-                      isClosureRoleAgentId(run.agent.agentId, roleBindings),
-                    ),
-                    coordinationLogPath: derivedState.coordinationLogPath,
-                    refreshDerivedState,
-                    dashboardState,
-                    recordCombinedEvent,
-                    flushDashboards,
-                    options,
-                    feedbackStateByRequestId,
-                    appendCoordination,
+                    message: "Implementation exit contracts and component promotions are satisfied.",
                   });
-                  failures = closureResult.failures;
-                  timedOut = timedOut || closureResult.timedOut;
-                  materializeAgentExecutionSummaries(wave, agentRuns);
-                  failures = annotateFailuresWithRecoveryHints(failures, agentRuns);
-                  refreshDerivedState(attempt);
                 }
-              } else {
-                recordCombinedEvent({
-                  message: "Implementation exit contracts and component promotions are satisfied.",
-                });
               }
             }
           }

package/scripts/wave-orchestrator/traces.mjs

@@ -10,6 +10,8 @@ import {
 import { readControlPlaneEvents } from "./control-plane.mjs";
 import {
   isContEvalReportOnlyAgent,
+  resolveDesignReportPath,
+  isDesignAgent,
   isSecurityReviewAgent,
   resolveSecurityReviewReportPath,
 } from "./role-helpers.mjs";
@@ -702,6 +704,11 @@ function resolveRunSummaryPayload(wave, run) {
       ? path.resolve(REPO_ROOT, wave.contQaReportPath || wave.evaluatorReportPath)
       : run.agent?.agentId === (wave?.contEvalAgentId || "E0") && wave?.contEvalReportPath
         ? path.resolve(REPO_ROOT, wave.contEvalReportPath)
+        : isDesignAgent(run.agent)
+          ? (() => {
+              const designReportPath = resolveDesignReportPath(run.agent);
+              return designReportPath ? path.resolve(REPO_ROOT, designReportPath) : null;
+            })()
         : isSecurityReviewAgent(run.agent)
           ? (() => {
               const securityReportPath = resolveSecurityReviewReportPath(run.agent);

package/scripts/wave-orchestrator/wave-state-reducer.mjs

@@ -23,7 +23,10 @@ import {
 import { buildHumanInputRequests } from "./human-input-workflow.mjs";
 import { projectLegacySummaryFromEnvelope } from "./result-envelope.mjs";
 import { buildRequestAssignments } from "./routing-state.mjs";
-import { resolveSecurityReviewReportPath } from "./role-helpers.mjs";
+import {
+  resolveDesignReportPath,
+  resolveSecurityReviewReportPath,
+} from "./role-helpers.mjs";
 
 const REDUCER_VERSION = 2;
 
@@ -37,6 +40,10 @@ function resolveReducerReportPath(waveDefinition, agent) {
   if (agent.agentId === (waveDefinition.contEvalAgentId || "E0")) {
     return waveDefinition.contEvalReportPath || null;
   }
+  const designReportPath = resolveDesignReportPath(agent);
+  if (designReportPath) {
+    return designReportPath;
+  }
   return resolveSecurityReviewReportPath(agent);
 }