@chllming/wave-orchestration 0.7.2 → 0.7.3

package/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 ## 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

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.2`
-- Release tag: [`v0.7.2`](https://github.com/chllming/agent-wave-orchestrator/releases/tag/v0.7.2)
+- `@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.2`:
+Highlights in `0.7.3`:
 
-- 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.
+- 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.2` package surface end to end.
+- Upgrade and operator docs now cover the full `0.7.3` package surface end to end.
 
 Requirements:
 

package/docs/plans/current-state.md

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

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

package/docs/plans/migration.md

@@ -22,13 +22,13 @@ 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.2
+## Upgrading From 0.6.x To 0.7.3
 
 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.2` also hardens proof-centric closure handling: final implementation markers now parse when emitted as Markdown list items, malformed marker syntax now surfaces explicit parse errors instead of generic missing-marker failures, and incomplete implementation work should stay inside the required final markers with `state=gap` instead of trailing `[wave-gap]` lines.
+`0.7.3` keeps the proof-centric closure hardening from `0.7.2` and closes the remaining parser hole: malformed unmatched end-of-tail fenced blocks no longer hide later final implementation markers, stale summaries rebuild when required proof/doc/component fields are still missing even if diagnostics already exist, malformed marker syntax still surfaces explicit parse errors, and incomplete implementation work should stay inside the required final markers with `state=gap` instead of trailing `[wave-gap]` lines.
 
 ### Required Repo Changes
 

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.7.2` release procedure publishes through a repository Actions secret named `NPM_TOKEN`.
+The current `0.7.3` release procedure publishes through a repository Actions secret named `NPM_TOKEN`.
 
 ## What This Repo Already Does
 
@@ -47,6 +47,6 @@ If this repo later needs private npm dependencies during CI, consider a separate
 1. Confirm [publish-npm.yml](../../.github/workflows/publish-npm.yml) is on the default branch.
 2. Confirm `NPM_TOKEN` exists in the GitHub repo secrets.
 3. Confirm the package version has been bumped and committed.
-4. Push the release commit and release tag, for example `v0.7.2`.
+4. Push the release commit and release tag, for example `v0.7.3`.
 5. Verify both `publish-npm.yml` and `publish-package.yml` start from the tag push.
 6. Verify the npmjs publish completes successfully for the tagged source.

package/docs/reference/sample-waves.md

@@ -1,11 +1,11 @@
 ---
 title: "Sample Waves"
-summary: "Showcase-first sample waves that demonstrate the current 0.7.2 Wave surface."
+summary: "Showcase-first sample waves that demonstrate the current 0.7.3 Wave surface."
 ---
 
 # Sample Waves
 
-This guide points to showcase-first sample waves that demonstrate the current `0.7.2` authored Wave surface.
+This guide points to showcase-first sample waves that demonstrate the current `0.7.3` 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.7.2` 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.7.3` 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.
 
 ## What These Examples Teach
 
@@ -38,7 +38,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 for `0.7.2`:
+Together these samples cover the main surfaces added or hardened for `0.7.3`:
 
 - repo-landed maturity discipline and anti-overclaim framing
 - explicit shared-plan closure for future-wave safety

package/package.json

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

package/releases/manifest.json

@@ -2,6 +2,23 @@
   "schemaVersion": 1,
   "packageName": "@chllming/wave-orchestration",
   "releases": [
+    {
+      "version": "0.7.3",
+      "date": "2026-03-23",
+      "summary": "Unmatched-fence structured-signal recovery, stale-summary rebuild hardening, and 0.7.3 release-surface alignment.",
+      "features": [
+        "Implementation summaries now recover final `[wave-proof]`, `[wave-doc-delta]`, and `[wave-component]` markers even when the log tail ends inside a malformed unmatched fenced block.",
+        "Legacy proof-centric summaries now refresh from source logs when required proof, doc-delta, or owned-component fields are still missing, even if stale `structuredSignalDiagnostics` data already exists.",
+        "Regression coverage now exercises unmatched end-of-tail fence handling and stale diagnostics-backed summary refresh directly.",
+        "Shipped package metadata, README, migration guidance, sample-wave docs, and npm publishing instructions now point at the `0.7.3` release surface."
+      ],
+      "manualSteps": [
+        "If an older lane still contains proof-centric `.summary.json` files with missing proof/doc/component fields, rerun the relevant launcher or status surface once after upgrading so the summaries can self-refresh from the source logs.",
+        "If an adopted `0.6.x` repo fails `wave doctor` after the `0.7.x` upgrade, sync the repo-owned planner starter surface (`docs/agents/wave-planner-role.md`, `skills/role-planner/`, `docs/context7/planner-agent/`, `docs/reference/wave-planning-lessons.md`, and the `planner-agentic` bundle entry) before relying on planner-aware validation.",
+        "Run `pnpm exec wave doctor` and `pnpm exec wave launch --lane main --dry-run --no-dashboard` after upgrading once your repo-owned wave files satisfy the current validation contract."
+      ],
+      "breaking": false
+    },
     {
       "version": "0.7.2",
       "date": "2026-03-23",

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

@@ -140,6 +140,21 @@ function parseStructuredSignalCandidate(line) {
   };
 }
 
+function appendParsedStructuredSignalCandidates(lines, candidates, { requireAll = false } = {}) {
+  const parsedCandidates = [];
+  for (const line of lines || []) {
+    const candidate = parseStructuredSignalCandidate(line);
+    if (candidate) {
+      parsedCandidates.push(candidate);
+      continue;
+    }
+    if (requireAll) {
+      return;
+    }
+  }
+  candidates.push(...parsedCandidates);
+}
+
 function collectStructuredSignalCandidates(text) {
   if (!text) {
     return [];
@@ -153,12 +168,7 @@ function collectStructuredSignalCandidates(text) {
         fenceLines = [];
         continue;
       }
-      const fenceCandidates = fenceLines
-        .map((line) => parseStructuredSignalCandidate(line))
-        .filter(Boolean);
-      if (fenceCandidates.length > 0 && fenceCandidates.length === fenceLines.length) {
-        candidates.push(...fenceCandidates);
-      }
+      appendParsedStructuredSignalCandidates(fenceLines, candidates, { requireAll: true });
       fenceLines = null;
       continue;
     }
@@ -174,6 +184,9 @@ function collectStructuredSignalCandidates(text) {
       candidates.push(candidate);
     }
   }
+  if (fenceLines !== null) {
+    appendParsedStructuredSignalCandidates(fenceLines, candidates);
+  }
   return candidates;
 }
 
@@ -576,27 +589,27 @@ function summaryNeedsStructuredSignalRefresh(payload, options = {}) {
   if (!payload || typeof payload !== "object" || Array.isArray(payload)) {
     return false;
   }
-  if (payload.structuredSignalDiagnostics && typeof payload.structuredSignalDiagnostics === "object") {
-    return false;
-  }
   const agent = options.agent;
   const contract = normalizeExitContract(agent?.exitContract);
   if (!contract) {
     return false;
   }
-  if (!payload.proof || !payload.docDelta) {
-    return true;
-  }
+  const missingProofOrDocDelta = !payload.proof || !payload.docDelta;
   const ownedComponents = Array.isArray(agent?.components) ? agent.components : [];
-  if (ownedComponents.length === 0) {
-    return false;
-  }
   const componentMarkers = new Map(
     Array.isArray(payload.components)
       ? payload.components.map((component) => [component.componentId, component])
       : [],
   );
-  return ownedComponents.some((componentId) => !componentMarkers.has(componentId));
+  const missingOwnedComponents =
+    ownedComponents.length > 0 && ownedComponents.some((componentId) => !componentMarkers.has(componentId));
+  if (missingProofOrDocDelta || missingOwnedComponents) {
+    return true;
+  }
+  if (payload.structuredSignalDiagnostics && typeof payload.structuredSignalDiagnostics === "object") {
+    return false;
+  }
+  return false;
 }
 
 function refreshExecutionSummaryIfStale(summaryPathOrStatusPath, payload, options = {}) {