@chllming/wave-orchestration 0.8.0 → 0.8.1

package/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 ## Unreleased
 
+## 0.8.1 - 2026-03-24
+
+### Changed
+
+- Updated the shipped package metadata, release manifest, README, migration guide, sample-wave docs, and npm publishing runbook to advertise `0.8.1` as the current release surface.
+
+### Fixed And Hardened
+
+- Helper-assignment policy resolution now treats `resolved-by-policy` follow-up as authoritative closure without requiring the original request to be rewritten.
+- Manual `wave coord post --kind resolved-by-policy` now defaults to `status=resolved`, so operator-authored policy closures stop reopening the assignment they are meant to close.
+- Multi-target helper requests now require assignment-specific policy evidence before closure, preventing one request-level `resolved-by-policy` note from accidentally closing sibling assignments.
+
+### Testing And Validation
+
+- Added regression coverage for default `resolved-by-policy` status handling and for multi-target assignment resolution that must not over-close sibling helper assignments.
+
 ## 0.8.0 - 2026-03-24
 
 ### Changed

package/README.md

@@ -79,18 +79,18 @@ Wave is built to mitigate those failures with a canonical authority set, generat
 
 Current release:
 
-- `@chllming/wave-orchestration@0.8.0`
-- Release tag: [`v0.8.0`](https://github.com/chllming/agent-wave-orchestrator/releases/tag/v0.8.0)
+- `@chllming/wave-orchestration@0.8.1`
+- Release tag: [`v0.8.1`](https://github.com/chllming/agent-wave-orchestrator/releases/tag/v0.8.1)
 - Public install path: npmjs
 - Authenticated fallback: GitHub Packages
 
-Highlights in `0.8.0`:
+Highlights in `0.8.1`:
 
-- Reducer and task replay hardening now keeps coordination-derived task identity deterministic and strengthens authoritative replay of live wave state.
-- Gate evaluation, contradiction or fact schema wiring, and resume planning are aligned around control-plane state plus typed result-envelope reads.
-- Live launcher evaluation now computes reducer snapshots during real runs instead of leaving that path effectively test-only.
-- The package now ships a dedicated architecture hardening migration plan and aligns the active README, guides, role prompts, and starter skills to the canonical authority-set and thin-launcher model.
-- Upgrade and operator docs now cover the full `0.8.0` package surface end to end.
+- `resolved-by-policy` helper follow-up now closes single-target helper assignments authoritatively instead of leaving stale helper-assignment barriers open.
+- Manual `wave coord post --kind resolved-by-policy` now defaults to `status=resolved`, which matches the intended policy-closure semantics.
+- Multi-target helper requests no longer over-close sibling assignments from a request-level policy note; assignment-specific evidence is required.
+- The architecture-hardening migration plan, reducer or envelope wiring, and aligned docs or skills from the prior release remain intact.
+- Upgrade and operator docs now cover the full `0.8.1` 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.8.0` package release surface.
+- The starter workspace in this source repo reflects the `0.8.1` package release surface.
 - The staged architecture cutover from launcher-centric decisions to reducer and phase-engine ownership is tracked in `docs/plans/architecture-hardening-migration.md`.
 - 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/`.

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

package/docs/plans/migration.md

@@ -24,13 +24,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.8.0
+## Upgrading From 0.6.x To 0.8.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.8.0` carries forward the `0.7.3` proof-centric closure hardening and adds the first architecture-hardening release surface: reducer and retry parity fixes, result-envelope-first gate wiring, contradiction or fact schema alignment, a dedicated architecture migration plan, and starter docs or skills that now describe the canonical authority-set model instead of the old launcher-centric wording.
+`0.8.1` carries forward the `0.8.0` architecture-hardening release surface and tightens helper-assignment closure handling: `resolved-by-policy` records now default to `resolved`, single-target helper requests can close from policy follow-up without mutating the original request, and multi-target helper requests only close from assignment-specific policy evidence so sibling assignments stay honest.
 
 ### Required Repo Changes
 
@@ -42,7 +42,7 @@ If the repo adopted Wave before the planner corpus became a tracked required sur
 - `docs/reference/wave-planning-lessons.md`
 - the `planner-agentic` bundle entry in `docs/context7/bundles.json`
 
-If the repo copied the shipped starter architecture docs or skills and wants the `0.8.0` authority-model language, also sync:
+If the repo copied the shipped starter architecture docs or skills and wants the `0.8.1` authority-model language, also sync:
 
 - `docs/agents/wave-launcher-role.md`
 - `docs/agents/wave-orchestrator-role.md`

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.8.0` release procedure publishes through a repository Actions secret named `NPM_TOKEN`.
+The current `0.8.1` 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.8.0`.
+4. Push the release commit and release tag, for example `v0.8.1`.
 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.8.0 Wave surface."
+summary: "Showcase-first sample waves that demonstrate the current 0.8.1 Wave surface."
 ---
 
 # Sample Waves
 
-This guide points to showcase-first sample waves that demonstrate the current `0.8.0` authored Wave surface.
+This guide points to showcase-first sample waves that demonstrate the current `0.8.1` 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.8.0` 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.8.1` 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.8.0`:
+Together these samples cover the main surfaces added or hardened for `0.8.1`:
 
 - 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.8.0",
+  "version": "0.8.1",
   "license": "MIT",
   "description": "Generic wave-based multi-agent orchestration for repository work.",
   "repository": {

package/releases/manifest.json

@@ -2,6 +2,26 @@
   "schemaVersion": 1,
   "packageName": "@chllming/wave-orchestration",
   "releases": [
+    {
+      "version": "0.8.1",
+      "date": "2026-03-24",
+      "summary": "Helper-assignment policy-closure hardening, multi-target assignment-safety repair, and 0.8.1 release-surface alignment.",
+      "features": [
+        "`resolved-by-policy` follow-up now closes single-target helper assignments authoritatively without forcing the original request record itself to be rewritten.",
+        "Manual `wave coord post --kind resolved-by-policy` now defaults to `status=resolved`, so operator-entered policy closures stop behaving like fresh open coordination records.",
+        "Multi-target helper requests now require assignment-specific policy evidence before closure, which prevents a request-level policy note from accidentally closing sibling assignments that were not actually completed.",
+        "Regression coverage now exercises default `resolved-by-policy` status handling and the multi-target helper-assignment over-closure edge case directly.",
+        "Shipped package metadata, README, migration guidance, sample-wave docs, and npm publishing instructions now point at the `0.8.1` release surface."
+      ],
+      "manualSteps": [
+        "Run `pnpm exec wave doctor` and `pnpm exec wave launch --lane main --dry-run --no-dashboard` after upgrading so the repo validates against the `0.8.1` runtime and helper-assignment closure contract.",
+        "If an adopted repo fails `wave doctor` after the 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.",
+        "If a repo carries custom operator docs for `wave coord post --kind resolved-by-policy`, update that guidance so policy-closure examples either omit `--status` or use `--status resolved` explicitly.",
+        "If an adopted repo copied the starter architecture docs or skill bundles, sync the updated role prompts, `skills/wave-core/`, runtime skills, and closure-role skills so local guidance matches the `0.8.1` authority model and helper-assignment behavior.",
+        "Review `docs/plans/architecture-hardening-migration.md` before continuing reducer-authoritative cutover work in repos that extend the shipped starter surface."
+      ],
+      "breaking": false
+    },
     {
       "version": "0.8.0",
       "date": "2026-03-24",

package/scripts/wave-orchestrator/coord-cli.mjs

@@ -69,7 +69,7 @@ function parseArgs(argv) {
     priority: "normal",
     dependsOn: [],
     artifactRefs: [],
-    status: "open",
+    status: "",
     id: "",
     to: "",
     response: "",
@@ -309,6 +309,10 @@ function appendCoordinationStatusUpdate(logPath, record, status, options = {}) {
   });
 }
 
+function defaultStatusForKind(kind) {
+  return String(kind || "").trim().toLowerCase() === "resolved-by-policy" ? "resolved" : "open";
+}
+
 function appendTriageEscalationUpdateIfPresent(lanePaths, waveNumber, record) {
   const triagePath = coordinationTriagePath(lanePaths, waveNumber);
   if (!fs.existsSync(triagePath) || record?.kind !== "human-escalation") {
@@ -436,7 +440,7 @@ export async function runCoordinationCli(argv) {
       priority: options.priority,
       dependsOn: options.dependsOn,
       artifactRefs: options.artifactRefs,
-      status: options.status,
+      status: options.status || defaultStatusForKind(options.kind),
       source: "agent",
     });
     console.log(JSON.stringify(record, null, 2));

package/scripts/wave-orchestrator/coordination-store.mjs

@@ -88,7 +88,9 @@ export function normalizeCoordinationRecord(rawRecord, defaults = {}) {
   const lane = normalizeString(rawRecord.lane || defaults.lane);
   const wave = Number.parseInt(String(rawRecord.wave ?? defaults.wave ?? ""), 10);
   const agentId = normalizeString(rawRecord.agentId || defaults.agentId);
-  const status = normalizeString(rawRecord.status || defaults.status || "open").toLowerCase();
+  const status = normalizeString(
+    rawRecord.status || defaults.status || (kind === "resolved-by-policy" ? "resolved" : "open"),
+  ).toLowerCase();
   const priority = normalizeString(rawRecord.priority || defaults.priority || "normal").toLowerCase();
   const confidence = normalizeString(rawRecord.confidence || defaults.confidence || "medium").toLowerCase();
   const createdAt = normalizeString(rawRecord.createdAt || defaults.createdAt || now);

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

@@ -155,6 +155,82 @@ function assignmentStateForRecord(record) {
   return "open";
 }
 
+function recordText(record) {
+  return `${String(record?.summary || "")}\n${String(record?.detail || "")}`.trim().toLowerCase();
+}
+
+function targetMatchesAgent(target, agentId) {
+  const normalizedTarget = String(target || "").trim();
+  const normalizedAgentId = String(agentId || "").trim();
+  if (!normalizedTarget || !normalizedAgentId) {
+    return false;
+  }
+  return normalizedTarget === normalizedAgentId || normalizedTarget === `agent:${normalizedAgentId}`;
+}
+
+function recordTargetsAgent(record, agentId) {
+  const normalizedAgentId = String(agentId || "").trim();
+  if (!normalizedAgentId) {
+    return false;
+  }
+  if (String(record?.agentId || "").trim() === normalizedAgentId) {
+    return true;
+  }
+  return Array.isArray(record?.targets)
+    ? record.targets.some((target) => targetMatchesAgent(target, normalizedAgentId))
+    : false;
+}
+
+function requestResolutionForAssignment({
+  coordinationState,
+  requestRecord,
+  assignmentId,
+  assignedAgentId,
+  target,
+}) {
+  const requestId = String(requestRecord?.id || "").trim();
+  if (!requestId) {
+    return null;
+  }
+  const requestIdLower = requestId.toLowerCase();
+  const assignmentIdLower = String(assignmentId || "").trim().toLowerCase();
+  const requestTargets = Array.isArray(requestRecord?.targets)
+    ? requestRecord.targets.filter((entry) => String(entry || "").trim())
+    : [];
+  const requiresAssignmentSpecificMatch = requestTargets.length > 1;
+  const resolvedRecords = [...(coordinationState?.resolvedByPolicy || [])].reverse();
+  for (const record of resolvedRecords) {
+    const dependsOn = Array.isArray(record?.dependsOn)
+      ? record.dependsOn.map((value) => String(value || "").trim().toLowerCase())
+      : [];
+    const assignmentDependsOnMatch = assignmentIdLower && dependsOn.includes(assignmentIdLower);
+    const requestDependsOnMatch = dependsOn.includes(requestIdLower);
+    if (assignmentDependsOnMatch || (!requiresAssignmentSpecificMatch && requestDependsOnMatch)) {
+      return record;
+    }
+    const closureCondition = String(record?.closureCondition || "").trim().toLowerCase();
+    const assignmentClosureMatch =
+      assignmentIdLower && closureCondition.includes(assignmentIdLower);
+    const requestClosureMatch = closureCondition.includes(requestIdLower);
+    if (
+      assignmentClosureMatch ||
+      (!requiresAssignmentSpecificMatch && requestClosureMatch)
+    ) {
+      return record;
+    }
+    if (!recordTargetsAgent(record, assignedAgentId) && !targetMatchesAgent(target, record?.agentId)) {
+      continue;
+    }
+    const text = recordText(record);
+    const assignmentTextMatch = assignmentIdLower && text.includes(assignmentIdLower);
+    const requestTextMatch = text.includes(requestIdLower);
+    if (assignmentTextMatch || (!requiresAssignmentSpecificMatch && requestTextMatch)) {
+      return record;
+    }
+  }
+  return null;
+}
+
 export function buildRequestAssignments({
   coordinationState,
   agents,
@@ -179,8 +255,18 @@ export function buildRequestAssignments({
     }
     for (const target of targets) {
       const resolution = resolveTargetAssignment(target, agents, ledger, capabilityRouting);
+      const assignmentId = `assignment:${record.id}:${targetSlug(target) || "target"}`;
+      const resolvedByPolicyRecord = requestResolutionForAssignment({
+        coordinationState,
+        requestRecord: record,
+        assignmentId,
+        assignedAgentId: resolution.assignedAgentId,
+        target,
+      });
+      const resolvedByPolicy = Boolean(resolvedByPolicyRecord);
+      const effectiveStatus = resolvedByPolicy ? "resolved" : record.status;
       assignments.push({
-        id: `assignment:${record.id}:${targetSlug(target) || "target"}`,
+        id: assignmentId,
         requestId: record.id,
         recordId: record.id,
         sourceKind: record.kind,
@@ -188,20 +274,21 @@ export function buildRequestAssignments({
         summary: record.summary || "",
         detail: record.detail || "",
         priority: record.priority || "normal",
-        requestStatus: record.status,
-        state: assignmentStateForRecord(record),
+        requestStatus: effectiveStatus,
+        state: assignmentStateForRecord({ ...record, status: effectiveStatus }),
         target: resolution.target,
         targetType: resolution.targetType,
         capability: resolution.capability,
         assignedAgentId: resolution.assignedAgentId,
         assignmentReason: resolution.assignmentReason,
         assignmentDetail: resolution.detail,
-        blocking: isOpenCoordinationStatus(record.status),
+        blocking: !resolvedByPolicy && isOpenCoordinationStatus(record.status),
         artifactRefs: Array.isArray(record.artifactRefs) ? record.artifactRefs : [],
         dependsOn: Array.isArray(record.dependsOn) ? record.dependsOn : [],
         closureCondition: String(record.closureCondition || ""),
         createdAt: record.createdAt,
         updatedAt: record.updatedAt,
+        resolvedByRecordId: resolvedByPolicyRecord?.id || null,
       });
     }
   }