@chllming/wave-orchestration 0.7.1 → 0.7.3

package/CHANGELOG.md

@@ -2,6 +2,36 @@
 
 ## Unreleased
 
+## 0.7.3 - 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.3` as the current release surface.
+
+### Fixed And Hardened
+
+- Implementation summary parsing now falls back to normal line-by-line structured-marker extraction when a log tail ends inside an unmatched fenced block, so malformed prompt or transcript tails cannot hide later final implementation markers.
+- Proof-centric summary repair now refreshes stale `.summary.json` files when required proof/doc/component fields are missing, even if a prior run already wrote a `structuredSignalDiagnostics` object with incorrect zero-count data.
+
+### Testing And Validation
+
+- Added regression coverage for unmatched end-of-tail fenced logs and stale diagnostics-backed implementation summaries.
+
+## 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

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.1`
-- Release tag: [`v0.7.1`](https://github.com/chllming/agent-wave-orchestrator/releases/tag/v0.7.1)
+- `@chllming/wave-orchestration@0.7.3`
+- Release tag: [`v0.7.3`](https://github.com/chllming/agent-wave-orchestrator/releases/tag/v0.7.3)
 - Public install path: npmjs
 - Authenticated fallback: GitHub Packages
 
-Highlights in `0.7.1`:
+Highlights in `0.7.3`:
 
-- 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.
+- Malformed end-of-tail fenced blocks no longer hide later final `[wave-proof]`, `[wave-doc-delta]`, and `[wave-component]` markers from the structured-signal collector.
+- Legacy proof-centric summaries now rebuild from source logs when required proof/doc/component fields are missing, even if a stale `structuredSignalDiagnostics` object already exists.
+- Final implementation marker diagnostics still distinguish truly missing markers from malformed marker syntax, so proof-centric failures stay actionable instead of collapsing into generic missing-marker noise.
+- 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.3` package surface end to end.
 
 Requirements:
 

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.1` package release surface.
+- The starter workspace in this source repo reflects the `0.7.3` 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.