@chllming/wave-orchestration 0.7.0 → 0.7.2

package/CHANGELOG.md

@@ -2,6 +2,40 @@
 
 ## Unreleased
 
+## 0.7.2 - 2026-03-23
+
+### Changed
+
+- Updated the shipped package metadata, release manifest, README, migration guide, sample-wave docs, and npm publishing runbook to advertise `0.7.2` as the current release surface.
+- Implementation prompts now require incomplete work to stay inside the final proof, doc-delta, and component markers with `state=gap`, and route unresolved issues through `wave coord post` instead of trailing `[wave-gap]` markers.
+
+### Fixed And Hardened
+
+- Implementation summary parsing now accepts final `[wave-proof]`, `[wave-doc-delta]`, and `[wave-component]` markers when the final structured block is emitted as Markdown list items.
+- Validation now distinguishes missing markers from rejected marker syntax with `invalid-wave-proof-format`, `invalid-doc-delta-format`, and `invalid-wave-component-format`.
+- Proof-centric summary repair now refreshes legacy `.summary.json` files from source logs only when the stored summary is actually missing required proof/doc/component data, preserving valid historical summaries.
+- `reconcile-status` now backfills missing `deliverables` and `proofArtifacts` arrays in older agent summaries before validation, so previously authoritative completed waves can survive summary-schema drift without weakening live closure.
+- Codex launch previews now expose `effectiveTurnLimit` and `effectiveTurnLimitSource`, making unresolved external turn ceilings machine-readable before the runtime later reports an observed limit.
+
+## 0.7.1 - 2026-03-23
+
+### Changed
+
+- Updated the shipped package metadata, release manifest, README, migration guide, sample-wave docs, and npm publishing runbook to advertise `0.7.1` as the current release surface.
+- Clarified the adopted-repo `0.7.x` upgrade path with explicit planner-corpus remediation, stable dashboard reattach guidance, and current-release examples that match the package tag.
+
+### Fixed And Hardened
+
+- Fresh live launches now clear stale auto-generated relaunch plans by default, with `--resume-control-state` as the explicit opt-in when an operator intentionally wants to preserve prior relaunch intent.
+- Fixed `wave control status` so an already-running attempt remains the authoritative live fan-out instead of letting stale relaunch metadata or unrelated closure blockers dominate the wave-level view.
+- Fixed `reconcile-status` so waves with prior authoritative closure stay complete as `completed_with_drift` when the only mismatch is historical prompt-hash drift.
+- Fixed live executor overlays so `launch-preview.json` is written for real runs as well as dry-runs, and Codex previews record observed turn ceilings when the runtime logs one.
+- Updated dashboard, CLI reference, and terminal-surface docs to consistently point operators at the shipped `wave dashboard --attach current|global` surface.
+
+### Testing And Validation
+
+- Updated release-surface regression coverage so package metadata, README, changelog, release manifest, migration guidance, and CLI docs all stay aligned on the current release version.
+
 ## 0.7.0 - 2026-03-23
 
 ### Added
@@ -41,12 +75,18 @@
 - Wave Control storage and queries now support durable Postgres-backed filtering by `workspaceId`, `projectId`, `orchestratorId`, and `runtimeVersion`.
 - Skill resolution description and documentation now accurately reflects the merge-then-resolve code path (base → role → runtime → deploy-kind → explicit).
 - Updated all documentation to reflect `0.7.0` release surface, including the operational runbook, coordination reference, sample waves, and live-proof examples.
+- Dashboard docs and CLI reference now document the stable `wave dashboard --attach current|global` surface instead of older speculative flags.
+- Upgrade and planner docs now call out the repo-owned planner corpus required by adopted `0.7.x` repos and explain that `wave upgrade` stays non-destructive.
+- Fresh live launches now clear stale auto-generated relaunch plans by default, with an explicit `--resume-control-state` escape hatch when an operator intentionally wants to preserve the previous relaunch selection.
 
 ### Fixed And Hardened
 
 - Fixed executor-profile inheritance so a Claude profile that only overrides `claude.effort` or other scalar runtime fields now keeps the inherited global Claude command and runtime settings instead of nulling them out.
 - Fixed shared promoted-component retries so landed owners stay reusable, stale relaunch plans are invalidated against current sibling ownership, and continuation can advance to the remaining owners without burning another retry on the already-clean agent.
 - Fixed clarification triage so routed follow-up work supersedes stale human escalations, keeps the routed chain blocking through the linked request, and only opens human escalation after orchestrator-side routing is actually exhausted.
+- Fixed `reconcile-status` so waves with prior authoritative closure stay complete as `completed_with_drift` when the only mismatch is historical prompt-hash drift.
+- Fixed live executor overlays so `launch-preview.json` is written for real runs as well as dry-runs, and Codex previews record an observed turn ceiling when the runtime logs one.
+- Fixed `wave control status` so an already-running attempt is treated as the authoritative live fan-out instead of letting stale relaunch metadata or unrelated closure blockers dominate the wave-level view.
 - Hardened proof registry projections from the control-plane so revoked and superseded bundles are excluded from closure evaluation.
 - Hardened the "What The Launcher Writes" path reference to correctly place `run-state.json` at the state root (not under `status/`), and added `control-plane/`, `proof/`, and `control/` directories.
 - Closed 11 documentation-to-code gaps identified by end-to-end audit, including trace contract completeness, skill pack enumeration, benchmark CLI surface, and steward coordination kinds.

package/README.md

@@ -79,18 +79,18 @@ Wave is built to mitigate those failures with canonical shared state, generated
 
 Current release:
 
-- `@chllming/wave-orchestration@0.7.0`
-- Release tag: [`v0.7.0`](https://github.com/chllming/agent-wave-orchestrator/releases/tag/v0.7.0)
+- `@chllming/wave-orchestration@0.7.2`
+- Release tag: [`v0.7.2`](https://github.com/chllming/agent-wave-orchestrator/releases/tag/v0.7.2)
 - Public install path: npmjs
 - Authenticated fallback: GitHub Packages
 
-Highlights in `0.7.0`:
+Highlights in `0.7.2`:
 
-- Unified `wave control` operator CLI with `status`, `task`, `rerun`, `proof`, and `telemetry` surfaces, replacing the separate `wave coord`/`wave retry`/`wave proof` commands (which remain as compatibility surfaces).
-- Canonical control-plane event log under `.tmp/<lane>-wave-launcher/control-plane/` with event-sourced materialization for proof bundles, rerun requests, operator tasks, and attempt lifecycle.
-- Wave Control telemetry: local-first event queueing with best-effort batch delivery to a Railway-hosted analysis endpoint, configurable report modes, selective artifact upload, and durable Postgres-backed querying by workspace, project, orchestrator, and runtime version.
-- Live-wave orchestration refresh that keeps coordination surfaces current during execution, including overdue acknowledgement tracking and stale clarification rerouting.
-- Resident orchestrator support via `--resident-orchestrator` for long-running non-owning monitoring sessions.
+- Final implementation markers now parse correctly when agents emit the structured proof/doc/component block as Markdown list items.
+- Runtime validation now distinguishes truly missing markers from malformed marker syntax, so proof-centric failures surface actionable parse errors.
+- Legacy proof-centric summaries repair themselves from source logs only when the stored summary is actually missing required closure markers.
+- Implementation prompts now keep incomplete work inside the required final markers with `state=gap` and route unresolved issues through `wave coord post`.
+- Upgrade and operator docs now cover the full `0.7.2` package surface end to end.
 
 Requirements:
 
@@ -181,6 +181,7 @@ codex mcp list
 - [docs/guides/terminal-surfaces.md](./docs/guides/terminal-surfaces.md): tmux, VS Code terminal registry, and dry-run surfaces
 - [docs/reference/sample-waves.md](./docs/reference/sample-waves.md): showcase-first authored waves, including a high-fidelity repo-landed rollout example
 - [docs/plans/examples/wave-example-rollout-fidelity.md](./docs/plans/examples/wave-example-rollout-fidelity.md): concrete example of what good wave fidelity looks like for a narrow, closure-ready outcome
+- [docs/reference/cli-reference.md](./docs/reference/cli-reference.md): complete CLI syntax for all commands and flags
 - [docs/plans/wave-orchestrator.md](./docs/plans/wave-orchestrator.md): operator runbook
 - [docs/plans/context7-wave-orchestrator.md](./docs/plans/context7-wave-orchestrator.md): Context7 setup and bundle authoring
 - [docs/reference/runtime-config/README.md](./docs/reference/runtime-config/README.md): executor, runtime, and skill-projection configuration

package/docs/guides/planner.md

@@ -21,6 +21,25 @@ It reduces repeated setup questions, stores project defaults, and generates wave
 - rendered markdown waves in `docs/plans/waves/wave-<n>.md`
 - candidate matrix previews plus canonical component matrix updates on apply
 
+## Upgrading Adopted 0.6.x Repos
+
+`wave upgrade` updates the installed runtime and records `.wave/install-state.json`, but it does not copy newer planner starter files into an already-adopted repo.
+
+If `pnpm exec wave doctor` starts failing after a `0.7.x` upgrade, sync these repo-owned planner surfaces from the packaged release:
+
+- `docs/agents/wave-planner-role.md`
+- `skills/role-planner/`
+- `docs/context7/planner-agent/`
+- `docs/reference/wave-planning-lessons.md`
+- the `planner-agentic` bundle entry in `docs/context7/bundles.json`
+
+Then rerun:
+
+```bash
+pnpm exec wave doctor
+pnpm exec wave launch --lane main --dry-run --no-dashboard
+```
+
 ## What The Planner Does Not Yet Ship
 
 - forward replanning of later waves

package/docs/guides/terminal-surfaces.md

@@ -45,6 +45,17 @@ Use `tmux` when:
 
 By default the launcher can start per-wave dashboard sessions in tmux.
 
+Wave now maintains stable tmux attach targets for both the current-wave dashboard and the global dashboard on the lane socket.
+
+Use:
+
+```bash
+pnpm exec wave dashboard --lane main --attach current
+pnpm exec wave dashboard --lane main --attach global
+```
+
+Those commands work for both `tmux` and `vscode` terminal surfaces because the live sessions still run on the lane tmux socket.
+
 When `--terminal-surface vscode` is active, Wave also maintains a stable current-wave dashboard terminal entry instead of creating a new wave-numbered dashboard attach target for every wave transition.
 
 Important flags:
@@ -63,6 +74,7 @@ Important flags:
 - Use `vscode` for local interactive operator work when the temporary terminal registry is useful.
 - Use `tmux` for remote, CI-like, or editor-independent operation.
 - Use `none` only with `--dry-run`.
+- Prefer `wave dashboard --attach current|global` over manual `tmux -L <socket> attach ...` lookups.
 - Pair `--keep-sessions` with incident review or deep debugging, not as a default steady-state mode.
 - Pair `--no-dashboard` with scripted dry-runs or when the board and summaries are sufficient.
 

package/docs/plans/component-cutover-matrix.json

@@ -23,6 +23,14 @@
         {
           "wave": 0,
           "target": "repo-landed"
+        },
+        {
+          "wave": 1,
+          "target": "baseline-proved"
+        },
+        {
+          "wave": 6,
+          "target": "pilot-live"
         }
       ],
       "proofSurfaces": [
@@ -38,7 +46,16 @@
         "docs/plans/context7-wave-orchestrator.md"
       ],
       "currentLevel": "repo-landed",
-      "promotions": [],
+      "promotions": [
+        {
+          "wave": 3,
+          "target": "baseline-proved"
+        },
+        {
+          "wave": 6,
+          "target": "pilot-live"
+        }
+      ],
       "proofSurfaces": [
         "executor launch specs",
         "runtime overlays",
@@ -53,7 +70,20 @@
         "docs/agents/wave-documentation-role.md"
       ],
       "currentLevel": "repo-landed",
-      "promotions": [],
+      "promotions": [
+        {
+          "wave": 1,
+          "target": "baseline-proved"
+        },
+        {
+          "wave": 3,
+          "target": "baseline-proved"
+        },
+        {
+          "wave": 6,
+          "target": "pilot-live"
+        }
+      ],
       "proofSurfaces": [
         "structured gate markers",
         "closure sweep",
@@ -81,7 +111,24 @@
         "docs/plans/current-state.md"
       ],
       "currentLevel": "repo-landed",
-      "promotions": [],
+      "promotions": [
+        {
+          "wave": 1,
+          "target": "repo-landed"
+        },
+        {
+          "wave": 2,
+          "target": "baseline-proved"
+        },
+        {
+          "wave": 4,
+          "target": "pilot-live"
+        },
+        {
+          "wave": 5,
+          "target": "qa-proved"
+        }
+      ],
       "proofSurfaces": [
         "status summaries",
         "dashboards",

package/docs/plans/current-state.md

@@ -1,6 +1,6 @@
 # Current State
 
-- The starter workspace in this source repo reflects the `0.7.0` package release surface.
+- The starter workspace in this source repo reflects the `0.7.2` package release surface.
 - 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/`.
 - 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.