@chllming/wave-orchestration 0.7.0 → 0.7.1

package/CHANGELOG.md

@@ -2,6 +2,25 @@
 
 ## Unreleased
 
+## 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 +60,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.1`
+- Release tag: [`v0.7.1`](https://github.com/chllming/agent-wave-orchestrator/releases/tag/v0.7.1)
 - Public install path: npmjs
 - Authenticated fallback: GitHub Packages
 
-Highlights in `0.7.0`:
+Highlights in `0.7.1`:
 
-- 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.
+- Fresh live launches now clear stale auto-generated relaunch plans by default, so explicit wave restarts seed a clean implementation fan-out unless `--resume-control-state` is passed.
+- `wave control status` now treats the active attempt as the authoritative live fan-out instead of replaying stale rerun intent or unrelated closure blockers.
+- `reconcile-status` now preserves previously authoritative completed waves as `completed_with_drift` when the only mismatch is historical prompt-hash drift.
+- Live `launch-preview.json` artifacts now exist for real runs as well as dry-runs, and Codex summaries record observed turn ceilings when the runtime reveals them.
+- Upgrade and operator docs now cover stable dashboard attach, adopted-repo planner corpus migration, and the full `0.7.1` 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/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.1` 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.

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.7.0` Wave surface.
+Use it as the single reference example for the current `0.7.1` Wave surface.
 
 It intentionally combines more sections than a normal production wave so one file can demonstrate:
 

package/docs/plans/migration.md

@@ -22,6 +22,32 @@ GitHub Packages remains available as an authenticated fallback path, and maintai
 - Fresh `wave init` seeds the starter `skills/` library. `wave init --adopt-existing` records existing repo-owned skill bundles when they are already present, but does not replace or rewrite them.
 - The current runtime expects the post-roadmap model: typed coordination, compiled inboxes, `A8` integration, staged closure, orchestrator-first clarification, and operational runtime policy.
 
+## Upgrading From 0.6.x To 0.7.1
+
+Read `CHANGELOG.md` first, then treat this section as the repo-owned migration checklist for adopted `0.6.x` workspaces.
+
+`wave upgrade` updates the installed runtime only. It does not copy planner starter files into a repo that already owns its docs, skills, and Context7 bundles.
+
+`0.7.1` also hardens run-control behavior for manual relaunches: fresh live starts clear stale auto-generated relaunch plans by default unless `--resume-control-state` is passed, and `wave control status` now treats the active attempt as the authoritative live fan-out while that attempt is running.
+
+### Required Repo Changes
+
+If the repo adopted Wave before the planner corpus became a tracked required surface, sync:
+
+- `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`
+
+### Recommended Upgrade Validation
+
+After syncing those repo-owned files:
+
+1. Run `pnpm exec wave doctor`.
+2. Run `pnpm exec wave launch --lane main --dry-run --no-dashboard`.
+3. Use `pnpm exec wave dashboard --lane <lane> --attach current` or `--attach global` when you need to reattach to a live tmux-backed dashboard without reverse-engineering the socket or session name.
+
 ## Upgrading From 0.5.4 To 0.6.1
 
 Read `CHANGELOG.md` first, then treat the rest of this page as the manual repo-owned migration checklist for the `0.6.1` release. `wave upgrade` will update package-owned runtime code only; it will not rewrite the docs, prompts, config, or wave files that your repo already owns.

package/docs/plans/wave-orchestrator.md

@@ -134,6 +134,7 @@ pnpm exec wave launch --lane main --start-wave 0 --end-wave 0 --executor codex -
 
 - `wave control status` is the read-only projection for "why blocked / why retrying" at wave or agent scope. It returns blocking edges, logical agent state, tasks, dependencies, rerun intent, active proof bundles, and next timers from one materialized control-plane view.
 - `wave control task create|get|list|act` is the operator task surface for blocking requests, blockers, clarification chains, human-input tickets, escalations, and informative handoffs, evidence, claims, and decisions. `wave control status` only treats requests, blockers, clarifications, human-input, escalations, helper assignments, and required dependencies as blocking edges.
+- A fresh live `wave launch --start-wave <n> --end-wave <n>` now clears the previous auto-generated relaunch plan for that wave before selecting the initial implementation fan-out. Pass `--resume-control-state` only when you intentionally want to keep that persisted relaunch selection.
 - `wave control rerun request|get|clear` manages targeted rerun intent under `.tmp/<lane>-wave-launcher/control-plane/` and projects compatible retry overrides under `.tmp/<lane>-wave-launcher/control/`, including selected agents, reuse selectors, invalidated components, and clear or preserve reuse lists.
 - `wave control proof register|get|supersede|revoke` manages authoritative proof bundles in the same control-plane log and projects compatible proof registries under `.tmp/<lane>-wave-launcher/proof/`.
 - `wave control telemetry status|flush` inspects and delivers the local Wave Control event queue. Pass `--no-telemetry` on `wave launch` to disable event publication for a single run.
@@ -308,13 +309,9 @@ The launcher entrypoint in `scripts/wave-orchestrator/launcher.mjs` now delegate
   [claude.md](../reference/runtime-config/claude.md),
   [opencode.md](../reference/runtime-config/opencode.md).
 
-## Benchmark CLI
+## CLI Reference
 
-- `wave benchmark list` lists local benchmark cases from the catalog.
-- `wave benchmark show --case <id>` shows a single case definition.
-- `wave benchmark run --case <id>` executes a local deterministic case.
-- `wave benchmark adapters` lists available external benchmark adapters.
-- `wave benchmark external-list|external-show|external-run|external-pilots` manage external benchmark targets (e.g., SWE-bench Pro).
+For the complete syntax of every command, flag, and subcommand, see [docs/reference/cli-reference.md](../reference/cli-reference.md).
 
 ## Executor Modes
 
@@ -328,7 +325,7 @@ The launcher entrypoint in `scripts/wave-orchestrator/launcher.mjs` now delegate
 - Skills resolve only after that executor choice is known. Runtime-specific skill overlays are regenerated whenever retry-time fallback changes the selected executor.
 - Runtime mix targets are enforced before launch and again before any retry-time fallback reassignment.
 - Fallbacks are declared in profiles or lane policy, can be applied automatically on retry when the next executor is available and still satisfies mix targets, and are recorded in the ledger, integration summary, and traces when used.
-- Generic `budget.minutes` caps per-agent attempt timeouts. Generic `budget.turns` seeds `claude.maxTurns` and `opencode.steps` when executor-specific values are not set; Codex turn ceilings remain external to Wave and show up in preview metadata as opaque when Wave cannot inspect them.
+- Generic `budget.minutes` caps per-agent attempt timeouts. Generic `budget.turns` seeds `claude.maxTurns` and `opencode.steps` when executor-specific values are not set; Codex turn ceilings remain external to Wave and show up in preview metadata as opaque when Wave cannot inspect them, though live previews now record an observed ceiling if the Codex runtime later logs one explicitly.
 - The launcher writes runtime overlay files under `.tmp/<lane>-wave-launcher/executors/`; these should stay ignored and local.
 
 Runtime authoring examples: