@chllming/wave-orchestration 0.5.2 → 0.5.3

package/CHANGELOG.md

@@ -1,10 +1,18 @@
 # Changelog
 
+## 0.5.3 - 2026-03-22
+
+- Deferred integration, documentation, and evaluator agents until the closure sweep whenever implementation work is still pending, so the runtime now matches the documented closure model.
+- Scoped wave wait/progress and human-feedback monitoring to the runs actually launched in the current pass, preventing deferred closure agents from surfacing as false pending or missing-status failures.
+- Added regression coverage for mixed implementation/closure waves and for closure-only retry waves.
+- Published `@chllming/wave-orchestration@0.5.3` successfully to npmjs and GitHub Releases.
+
 ## 0.5.2 - 2026-03-22
 
 - Hardened structured closure marker parsing so fenced or prose example `[wave-*]` lines no longer satisfy implementation, integration, documentation, or evaluator gates.
 - Hardened `### Deliverables` so declared outputs must remain repo-relative file paths inside the implementation agent's declared file ownership before the exit contract can pass.
 - Added regression coverage for the fenced-marker false-positive path and for deliverables that escape ownership boundaries.
+- Published `@chllming/wave-orchestration@0.5.2` successfully to npmjs, making npmjs the working public install path instead of a pending rollout target.
 
 ## 0.5.1 - 2026-03-22
 

package/README.md

@@ -17,10 +17,11 @@ It includes:
 ## Quick Start
 
 Published package:
-- `@chllming/wave-orchestration@0.5.2`
+- `@chllming/wave-orchestration@0.5.3`
 - Primary public registry: `https://registry.npmjs.org`
-- Release: [v0.5.2](https://github.com/chllming/wave-orchestration/releases/tag/v0.5.2)
+- Release: [v0.5.3](https://github.com/chllming/wave-orchestration/releases/tag/v0.5.3)
 - npmjs publish workflow: [publish-npm.yml](./.github/workflows/publish-npm.yml)
+- npmjs install is now live for `0.5.3`; GitHub Packages is the authenticated fallback path only.
 
 Install from npmjs:
 
@@ -38,11 +39,18 @@ If your repo already has Wave config, docs, or waves you want to keep:
 pnpm exec wave init --adopt-existing
 ```
 
+## New In 0.5.3
+
+- The launcher now starts only implementation agents in the initial wave pass when implementation work is still pending.
+- Wait/progress tracking now scopes to the runs actually launched in the current pass, so deferred closure agents no longer look like missing or pending failures.
+- Closure-only retries still run through the existing `A8` -> `A9` -> `A0` sweep, with regression coverage for both mixed and closure-only cases.
+
 ## New In 0.5.2
 
 - Example `[wave-*]` markers inside fenced snippets or prose no longer satisfy closure; only real standalone structured signals count.
 - `### Deliverables` is now enforced as an ownership-scoped file contract, so declared outputs must stay inside that agent's `File ownership` block.
 - Regression coverage now includes both of those failure paths directly.
+- The npmjs package release is now live, so `pnpm add -D @chllming/wave-orchestration` works from the public registry without the older GitHub Packages auth setup.
 
 ## New In 0.5.1
 

package/package.json

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

package/releases/manifest.json

@@ -2,6 +2,21 @@
   "schemaVersion": 1,
   "packageName": "@chllming/wave-orchestration",
   "releases": [
+    {
+      "version": "0.5.3",
+      "date": "2026-03-22",
+      "summary": "Closure-sweep launch ordering fix for implementation-first wave execution.",
+      "features": [
+        "The launcher now starts only implementation agents in the initial wave pass when implementation work remains, deferring integration, documentation, and evaluator roles until closure sweep order.",
+        "Wave waiting, dashboard progress refresh, and human-feedback monitoring now scope to the runs launched in the current pass so deferred closure agents no longer create false pending or missing-status failures.",
+        "Regression coverage now exercises both mixed implementation/closure waves and closure-only retry waves directly."
+      ],
+      "manualSteps": [
+        "After upgrading, rerun `pnpm exec wave launch --lane main --dry-run --no-dashboard` on active lanes to confirm only implementation agents appear in the initial pass.",
+        "If a lane is mid-run, relaunch from the upgraded package so closure agents pick up the corrected launch ordering and wait behavior."
+      ],
+      "breaking": false
+    },
     {
       "version": "0.5.2",
       "date": "2026-03-22",

package/scripts/wave-orchestrator/launcher.mjs

@@ -2133,6 +2133,13 @@ function isClosureAgentId(agentId, lanePaths) {
   ].includes(agentId);
 }
 
+export function selectInitialWaveRuns(agentRuns, lanePaths) {
+  const implementationRuns = (agentRuns || []).filter(
+    (run) => !isClosureAgentId(run?.agent?.agentId, lanePaths),
+  );
+  return implementationRuns.length > 0 ? implementationRuns : agentRuns;
+}
+
 function isLauncherSeedRequest(record) {
   return (
     record?.source === "launcher" &&
@@ -3149,7 +3156,10 @@ export async function runLauncherCli(argv) {
           });
         }
 
-        let runsToLaunch = agentRuns.filter((run) => !preCompletedAgentIds.has(run.agent.agentId));
+        let runsToLaunch = selectInitialWaveRuns(
+          agentRuns.filter((run) => !preCompletedAgentIds.has(run.agent.agentId)),
+          lanePaths,
+        );
         let attempt = 1;
         const feedbackStateByRequestId = new Map();
 
@@ -3271,16 +3281,19 @@ export async function runLauncherCli(argv) {
 
             const waitResult = await waitForWaveCompletion(
               lanePaths,
-              agentRuns,
+              runsToLaunch,
               options.timeoutMinutes,
               ({ pendingAgentIds }) => {
-                refreshWaveDashboardAgentStates(dashboardState, agentRuns, pendingAgentIds, (event) =>
-                  recordCombinedEvent(event),
+                refreshWaveDashboardAgentStates(
+                  dashboardState,
+                  runsToLaunch,
+                  pendingAgentIds,
+                  (event) => recordCombinedEvent(event),
                 );
                 monitorWaveHumanFeedback({
                   lanePaths,
                   waveNumber: wave.wave,
-                  agentRuns,
+                  agentRuns: runsToLaunch,
                   orchestratorId: options.orchestratorId,
                   coordinationLogPath: derivedState.coordinationLogPath,
                   feedbackStateByRequestId,