@chllming/wave-orchestration 0.8.4 → 0.8.6

package/docs/reference/cli-reference.md

@@ -96,7 +96,7 @@ Unified operator control surface. Preferred over legacy `wave coord`, `wave retr
 
 ### wave control status
 
-Read-only view: blocking edges, logical agent state, tasks, dependencies, rerun intent, proof bundles, and next timers.
+Read-only view: blocking edges, logical agent state, tasks, dependencies, rerun intent, proof bundles, next timers, and derived wave or agent signal snapshots.
 
 When a launcher attempt is already running, `wave control status` treats that active attempt as the authoritative current fan-out. Older relaunch plans or unrelated closure blockers remain visible in the payload, but they do not override the live attempt view.
 
@@ -104,6 +104,15 @@ When a launcher attempt is already running, `wave control status` treats that ac
 wave control status --lane <lane> --wave <n> [--agent <id>] [--run <id>] [--json]
 ```
 
+The JSON payload now includes:
+
+- `signals.wave`
+  Versioned wave-level signal state for wrappers and external operators.
+- `signals.agents`
+  Versioned per-agent signal state, including `shouldWake` plus any observed ack metadata.
+
+Starter repos also include `scripts/wave-status.sh` and `scripts/wave-watch.sh` as thin readers over this JSON payload. They use exit `0` for completed, `20` for input-required, `40` for failed, and `30` from `wave-watch.sh --until-change` when the signal changed but the wave stayed active. For the full wrapper contract, read [../guides/signal-wrappers.md](../guides/signal-wrappers.md).
+
 ### wave control telemetry
 
 Inspect and deliver the local Wave Control event queue.
@@ -534,6 +543,18 @@ wave draft --show-run <run-id>
 wave draft --apply-run <run-id>
 ```
 
+Interactive draft currently offers worker role kinds:
+
+- `design`
+- `implementation`
+- `qa`
+- `infra`
+- `deploy`
+- `research`
+- `security`
+
+Agentic planner payloads also accept `workerAgents[].roleKind = "design"`. The shipped `0.8.6` surface uses `design-pass` as the default executor profile for that role and typically assigns a packet path like `docs/plans/waves/design/wave-<n>-<agentId>.md`. Interactive draft scaffolds the docs-first default; hybrid design stewards are authored by explicitly adding implementation-owned paths and the normal implementation contract sections.
+
 ## Ad-Hoc Task Commands
 
 **Plan and run ad-hoc tasks:**

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.4` release procedure publishes through a repository Actions secret named `NPM_TOKEN`.
+The current `0.8.6` release procedure publishes through a repository Actions secret named `NPM_TOKEN`.
 
 ## What This Repo Already Does
 
@@ -48,6 +48,6 @@ If this repo later needs private npm dependencies during CI, consider a separate
 2. Confirm `NPM_TOKEN` exists in the GitHub repo secrets.
 3. Confirm the package version has been bumped and committed.
 4. Confirm `README.md`, `CHANGELOG.md`, `releases/manifest.json`, and `docs/plans/migration.md` all describe the same release surface.
-5. Push the release commit and release tag, for example `v0.8.4`.
+5. Push the release commit and release tag, for example `v0.8.6`.
 6. Verify both `publish-npm.yml` and `publish-package.yml` start from the tag push.
 7. 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.4 Wave surface."
+summary: "Showcase-first sample waves that demonstrate the shipped 0.8.6 authored surface, including the optional design-role path."
 ---
 
 # Sample Waves
 
-This guide points to showcase-first sample waves that demonstrate the current `0.8.4` authored Wave surface.
+This guide points to showcase-first sample waves that demonstrate the shipped `0.8.6` 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,10 @@ 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.4` 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.6` 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.
+
+- [Optional design-steward handoff wave](../plans/examples/wave-example-design-handoff.md)
+  Shows the shipped design-role surface: one pre-implementation design steward publishes a design packet, downstream implementation owners read that packet before coding, and normal closure roles still decide final completion. For terminal or operator-surface work, pair that shape with explicit `tui-design` in the design steward's `### Skills`. For the hybrid variant, explicitly give that same design agent implementation-owned paths and the normal implementation contract sections.
 
 ## What These Examples Teach
 
@@ -35,10 +38,11 @@ The examples are intentionally denser than typical production waves. Their job i
 - sticky retry for proof-bearing owners
 - deploy environments and provider-skill examples
 - infra and deploy-verifier specialist slices
+- optional pre-implementation design packets and design-to-implementation handoff
 
 ## Feature Coverage Map
 
-Together these samples cover the main surfaces added or hardened for `0.8.4`:
+Together these samples cover the main surfaces added or hardened through `0.8.6`:
 
 - repo-landed maturity discipline and anti-overclaim framing
 - explicit shared-plan closure for future-wave safety
@@ -56,6 +60,7 @@ Together these samples cover the main surfaces added or hardened for `0.8.4`:
 - proof-first live-wave prompts
 - deploy environments and deploy-kind-aware skills
 - integration, documentation, and cont-QA closure-role structure
+- optional `design` worker role and `design-pass` executor profile
 
 ## When To Copy Literally Vs Adapt
 
@@ -76,6 +81,7 @@ Adapt more aggressively when:
 ## How This Example Maps To Other Docs
 
 - Use [docs/guides/planner.md](../guides/planner.md) for the planner-generated baseline, then use these samples to see how a human would enrich the generated draft for either repo-landed or proof-first work.
+- Use [Optional design-steward handoff wave](../plans/examples/wave-example-design-handoff.md) when the wave should start with a reusable design packet before implementation begins.
 - Use [docs/evals/README.md](../evals/README.md) with the full modern sample when you need to see delegated and pinned benchmark targets in a real wave.
 - Use [docs/reference/live-proof-waves.md](./live-proof-waves.md) with the full modern sample when you need proof-first authoring for `pilot-live` and above.
 - Use [docs/plans/wave-orchestrator.md](../plans/wave-orchestrator.md) for the operational runbook that explains how the launcher interprets these sections.
@@ -83,9 +89,10 @@ Adapt more aggressively when:
 ## Suggested Reading Order
 
 1. Start with [High-fidelity repo-landed rollout wave](../plans/examples/wave-example-rollout-fidelity.md) if you want the clearest example of good closure-ready wave fidelity for a repo-only outcome.
-2. Read [Full modern sample wave](../plans/examples/wave-example-live-proof.md) if you want the denser proof-first and eval-heavy surface.
-3. Read [docs/evals/README.md](../evals/README.md) if you want more background on benchmark target selection.
-4. Read [docs/reference/live-proof-waves.md](./live-proof-waves.md) if you want more detail on proof-first `pilot-live` authoring.
+2. Read [Full modern sample wave](../plans/examples/wave-example-live-proof.md) if you want the denser proof-first and eval-heavy `0.8.6` surface.
+3. Read [Optional design-steward handoff wave](../plans/examples/wave-example-design-handoff.md) if the task needs a design packet before implementation fan-out.
+4. Read [docs/evals/README.md](../evals/README.md) if you want more background on benchmark target selection.
+5. Read [docs/reference/live-proof-waves.md](./live-proof-waves.md) if you want more detail on proof-first `pilot-live` authoring.
 
 ## Why These Examples Live In `docs/plans/examples/`
 

package/docs/reference/skills.md

@@ -109,6 +109,7 @@ Top-level and lane-local skill attachment use the same shape:
     "dir": "skills",
     "base": ["wave-core", "repo-coding-rules"],
     "byRole": {
+      "design": ["role-design"],
       "deploy": ["role-deploy"]
     },
     "byRuntime": {
@@ -123,6 +124,10 @@ Top-level and lane-local skill attachment use the same shape:
 
 Lane-local `lanes.<lane>.skills` extends the global config instead of replacing it.
 
+Optional design workers in the shipped `0.8.6` surface normally attach `role-design`. That bundle is intended for docs/spec-first design packets and explicit implementation handoff work before implementation starts. When the design packet covers terminal UX, dashboards, or other operator surfaces, add `tui-design` explicitly in the wave's `### Skills`.
+
+Long-running agents that should stay resident and react only to orchestrator signal changes can add `signal-hygiene` explicitly in `### Skills`. That bundle is not auto-attached and is not meant for normal one-shot implementation agents.
+
 ## Resolution Order
 
 Resolved skills are gathered in this order:
@@ -195,6 +200,18 @@ Runtime delivery:
 
 These runtime projections are guidance surfaces. They should stay aligned with the canonical authority model, but they are not replay inputs or decision state on their own.
 
+For the optional `design` worker role, the default pattern is:
+
+- `role-design` for the design packet contract
+- `tui-design` only when the packet covers terminal UX, dashboards, or other operator surfaces
+- no runtime-specific coding bundle unless the wave explicitly gives the design steward code ownership and makes it a hybrid design steward
+
+For long-running watcher agents, the default pattern is:
+
+- no special bundle by default
+- add `signal-hygiene` only when the agent should stay alive and wait for signal-version changes
+- use the provided signal state path plus signal ack path instead of inventing a second wakeup loop
+
 ## Generated Artifacts
 
 Executor overlay directories can contain:
@@ -225,3 +242,4 @@ Missing or malformed bundles are configuration errors, not silent no-ops.
 - Use explicit per-agent `### Skills` for true exceptions, not as a substitute for missing activation metadata.
 - Keep provider skills role-scoped unless every role genuinely needs the provider context.
 - Keep bundle ids stable so traces and prompt fingerprints remain intelligible across runs.
+- Keep `role-design` docs/spec-first by default; add `tui-design` when terminal or operator-surface work is in scope, and only attach broader coding bundles when the wave explicitly assigns code ownership and expects the same design steward to return for implementation.

package/docs/reference/wave-control.md

@@ -19,6 +19,8 @@ Wave Control normalizes these entity types:
 
 - `wave_run`
 - `agent_run`
+- `wave_signal`
+- `agent_signal`
 - `coordination_record`
 - `task`
 - `attempt`

package/package.json

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

package/releases/manifest.json

@@ -2,6 +2,44 @@
   "schemaVersion": 1,
   "packageName": "@chllming/wave-orchestration",
   "releases": [
+    {
+      "version": "0.8.6",
+      "date": "2026-03-25",
+      "summary": "Signal-hygiene starter surface, versioned signal wrappers, terminal watcher hardening, and 0.8.6 release-surface alignment.",
+      "features": [
+        "Versioned wave and agent signal snapshots now ship as part of the operator surface under `.tmp/<lane>-wave-launcher/signals/`, with resident-orchestrator and long-running-agent ack loops built on the same model.",
+        "Starter repos now include `skills/signal-hygiene/`, `scripts/wave-status.sh`, and `scripts/wave-watch.sh` for long-running watcher agents plus shell-friendly operator automation.",
+        "Wrapper exit semantics now expose terminal failure with exit `40`, while `wave-watch.sh --until-change` still returns `30` only when a signal changed and the wave stayed active.",
+        "Agent signal materialization now treats completed and failed as terminal even when stale answered feedback or old coordination tasks still exist in the materialized status payload.",
+        "The migration guide now covers fresh adoption plus upgrades from `0.8.5`, `0.8.4`, `0.8.3`, `0.8.0`-`0.8.4`, `0.6.x`-`0.7.x`, and `0.5.x` or earlier, including repo-owned sync guidance for `skills/signal-hygiene/`, the wrapper scripts, and the `planner-agentic` corpus."
+      ],
+      "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.6` signal-hygiene, wrapper, and design-role behavior.",
+        "If your repo copied starter prompts, skills, scripts, or runbooks, sync `skills/signal-hygiene/`, `scripts/wave-status.sh`, `scripts/wave-watch.sh`, `docs/guides/signal-wrappers.md`, `docs/guides/terminal-surfaces.md`, `docs/reference/cli-reference.md`, and any local operator docs that describe waiting or failure handling.",
+        "If your repo uses planner workflows and copied the planner starter corpus, keep `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 in sync before relying on local planner docs.",
+        "If your repo uses long-running watcher agents or shell automation, update local loops so wrapper exit `40` is treated as terminal failure and confirm watchers can write their signal ack files under `.tmp/<lane>-wave-launcher/signals/`."
+      ],
+      "breaking": false
+    },
+    {
+      "version": "0.8.5",
+      "date": "2026-03-25",
+      "summary": "Shipped design-role support, hybrid design-steward execution, release-surface alignment, and a practical migration guide.",
+      "features": [
+        "The optional `design` worker role is now part of the published release surface, including the standing design prompt, `role-design`, and `tui-design` starter bundles.",
+        "Design stewards are docs-first by default, but waves can now explicitly give them implementation ownership so the same agent runs a design pass first and then rejoins implementation with normal proof obligations.",
+        "Design-aware validation, prompts, gates, retry or resume planning, reducer state, local-executor smoke behavior, and result-envelope projection now all agree on the same hybrid-design contract.",
+        "The migration guide now covers fresh adoption plus upgrades from `0.8.4`, `0.8.0`-`0.8.4`, `0.6.x`-`0.7.x`, and `0.5.x` or earlier, including repo-owned starter-surface sync guidance and `planner-agentic` corpus notes.",
+        "Shipped package metadata, README, current-state notes, sample-wave docs, and publishing guidance now point at the `0.8.5` 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.5` design-role and hybrid-design behavior.",
+        "If your repo copied starter prompts, skills, or authoring docs, sync `docs/agents/wave-design-role.md`, `skills/role-design/`, `skills/tui-design/`, `wave.config.json` design-role keys, and any local planner or runbook pages that should describe the new design-steward model.",
+        "If a repo uses hybrid design stewards, make sure each one still owns a design packet path and that any explicit implementation ownership also carries the expected exit contract, deliverables, proof artifacts, and component declarations where your lane validation requires them.",
+        "If your repo uses planner workflows and copied the planner starter corpus, keep `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 in sync before relying on local planner docs."
+      ],
+      "breaking": false
+    },
     {
       "version": "0.8.4",
       "date": "2026-03-25",

package/scripts/context7-api-check.sh

@@ -1,5 +1,4 @@
 #!/usr/bin/env bash
-# Minimal Context7 API smoke test (expects CONTEXT7_API_KEY in the environment).
 set -euo pipefail
 
 if [[ -z "${CONTEXT7_API_KEY:-}" ]]; then
@@ -7,15 +6,60 @@ if [[ -z "${CONTEXT7_API_KEY:-}" ]]; then
   exit 1
 fi
 
-URL='https://context7.com/api/v2/libs/search?libraryName=temporal&query=go%20workflow'
-echo "GET $URL" >&2
-RESP="$(curl -fsS "$URL" -H "Authorization: Bearer ${CONTEXT7_API_KEY}" -H "Accept: application/json")"
-RESP_JSON="$RESP" node -e "
-const j = JSON.parse(process.env.RESP_JSON || '{}');
-const list = Array.isArray(j) ? j : (j.results ?? j.items ?? []);
-const first = list[0];
-if (!first) { console.error('Unexpected response shape:', Object.keys(j)); process.exit(1); }
-const id = first.id ?? first.libraryId;
-const name = first.title ?? first.name;
-console.log('ok — first library:', id || name || JSON.stringify(first).slice(0, 120));
-"
+node <<'NODE'
+const fs = require("fs");
+const path = require("path");
+
+const apiKey = process.env.CONTEXT7_API_KEY || "";
+const repoRoot = process.cwd();
+const bundlePath = path.join(repoRoot, "docs/context7/bundles.json");
+const payload = JSON.parse(fs.readFileSync(bundlePath, "utf8"));
+
+const entries = [];
+for (const [bundleId, bundle] of Object.entries(payload.bundles || {})) {
+  for (const library of bundle.libraries || []) {
+    if (!library.libraryId) {
+      throw new Error(
+        `Bundle "${bundleId}" must pin exact Context7 libraryId values. Found libraryName=${JSON.stringify(library.libraryName || "")}.`,
+      );
+    }
+    entries.push({
+      bundleId,
+      libraryId: String(library.libraryId),
+      queryHint: String(library.queryHint || "overview"),
+    });
+  }
+}
+
+const uniqueEntries = [...new Map(entries.map((entry) => [entry.libraryId, entry])).values()];
+
+async function validate(entry) {
+  const url = new URL("https://context7.com/api/v2/context");
+  url.searchParams.set("libraryId", entry.libraryId);
+  url.searchParams.set("query", entry.queryHint);
+  url.searchParams.set("type", "txt");
+  const response = await fetch(url, {
+    headers: {
+      Authorization: "Bearer " + apiKey,
+      Accept: "text/plain, application/json",
+    },
+  });
+  const text = await response.text();
+  if (!response.ok) {
+    throw new Error(`Context7 ${entry.libraryId} failed (${response.status}): ${text.slice(0, 200)}`);
+  }
+  if (text.trim().length === 0) {
+    throw new Error(`Context7 ${entry.libraryId} returned empty context.`);
+  }
+  console.log(`ok -- ${entry.libraryId} (${entry.bundleId})`);
+}
+
+(async () => {
+  for (const entry of uniqueEntries) {
+    await validate(entry);
+  }
+})().catch((error) => {
+  console.error(error instanceof Error ? error.message : String(error));
+  process.exit(1);
+});
+NODE

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

@@ -47,6 +47,8 @@ const WAVE_EVAL_REGEX =
   /^\[wave-eval\]\s*state=(satisfied|needs-more-work|blocked)\s+targets=(\d+)\s+benchmarks=(\d+)\s+regressions=(\d+)(?:\s+target_ids=([^\s]+))?(?:\s+benchmark_ids=([^\s]+))?\s*(?:detail=(.*))?$/gim;
 const WAVE_SECURITY_REGEX =
   /^\[wave-security\]\s*state=(clear|concerns|blocked)\s+findings=(\d+)\s+approvals=(\d+)\s*(?:detail=(.*))?$/gim;
+const WAVE_DESIGN_REGEX =
+  /^\[wave-design\]\s*state=(ready-for-implementation|needs-clarification|blocked)\s+decisions=(\d+)\s+assumptions=(\d+)\s+open_questions=(\d+)\s*(?:detail=(.*))?$/gim;
 const WAVE_GATE_REGEX =
   /^\[wave-gate\]\s*architecture=(pass|concerns|blocked)\s+integration=(pass|concerns|blocked)\s+durability=(pass|concerns|blocked)\s+live=(pass|concerns|blocked)\s+docs=(pass|concerns|blocked)\s*(?:detail=(.*))?$/gim;
 const WAVE_GAP_REGEX =
@@ -64,6 +66,7 @@ const STRUCTURED_SIGNAL_KIND_BY_TAG = {
   integration: "integration",
   eval: "eval",
   security: "security",
+  design: "design",
   gate: "gate",
   gap: "gap",
   component: "component",
@@ -76,6 +79,7 @@ const STRUCTURED_SIGNAL_LINE_REGEX_BY_KIND = {
   integration: new RegExp(WAVE_INTEGRATION_REGEX.source, "i"),
   eval: new RegExp(WAVE_EVAL_REGEX.source, "i"),
   security: new RegExp(WAVE_SECURITY_REGEX.source, "i"),
+  design: new RegExp(WAVE_DESIGN_REGEX.source, "i"),
   gate: new RegExp(WAVE_GATE_REGEX.source, "i"),
   gap: new RegExp(WAVE_GAP_REGEX.source, "i"),
   component: new RegExp(WAVE_COMPONENT_REGEX.source, "i"),
@@ -89,6 +93,7 @@ function buildEmptyStructuredSignalDiagnostics() {
     integration: { rawCount: 0, acceptedCount: 0, rejectedSamples: [] },
     eval: { rawCount: 0, acceptedCount: 0, rejectedSamples: [] },
     security: { rawCount: 0, acceptedCount: 0, rejectedSamples: [] },
+    design: { rawCount: 0, acceptedCount: 0, rejectedSamples: [] },
     gate: { rawCount: 0, acceptedCount: 0, rejectedSamples: [] },
     gap: { rawCount: 0, acceptedCount: 0, rejectedSamples: [] },
     component: { rawCount: 0, acceptedCount: 0, rejectedSamples: [], seenComponentIds: [] },
@@ -509,6 +514,13 @@ export function buildAgentExecutionSummary({ agent, statusRecord, logPath, repor
       approvals: Number.parseInt(String(match[3] || "0"), 10) || 0,
       detail: cleanText(match[4]),
     })),
+    design: findLastMatch(signalText, WAVE_DESIGN_REGEX, (match) => ({
+      state: match[1],
+      decisions: Number.parseInt(String(match[2] || "0"), 10) || 0,
+      assumptions: Number.parseInt(String(match[3] || "0"), 10) || 0,
+      openQuestions: Number.parseInt(String(match[4] || "0"), 10) || 0,
+      detail: cleanText(match[5]),
+    })),
     gate: findLastMatch(signalText, WAVE_GATE_REGEX, (match) => ({
       architecture: match[1],
       integration: match[2],
@@ -951,6 +963,58 @@ export function validateSecuritySummary(agent, summary) {
   };
 }
 
+export function validateDesignSummary(agent, summary) {
+  if (!summary?.design) {
+    return {
+      ok: false,
+      statusCode: "missing-wave-design",
+      detail: appendTerminationHint(
+        `Missing [wave-design] marker for ${agent?.agentId || "D1"}.`,
+        summary,
+      ),
+    };
+  }
+  if (!summary.reportPath) {
+    return {
+      ok: false,
+      statusCode: "missing-design-packet",
+      detail: `Missing design packet path for ${agent?.agentId || "D1"}.`,
+    };
+  }
+  if (!fs.existsSync(path.resolve(REPO_ROOT, summary.reportPath))) {
+    return {
+      ok: false,
+      statusCode: "missing-design-packet",
+      detail: `Missing design packet at ${summary.reportPath}.`,
+    };
+  }
+  if (summary.design.state === "blocked") {
+    return {
+      ok: false,
+      statusCode: "design-blocked",
+      detail:
+        summary.design.detail ||
+        `Design packet reported blocked for ${agent?.agentId || "D1"}.`,
+    };
+  }
+  if (summary.design.state === "needs-clarification") {
+    return {
+      ok: false,
+      statusCode: "design-needs-clarification",
+      detail:
+        summary.design.detail ||
+        `Design packet requested clarification for ${agent?.agentId || "D1"}.`,
+    };
+  }
+  return {
+    ok: true,
+    statusCode: "pass",
+    detail:
+      summary.design.detail ||
+      "Design packet is ready for implementation.",
+  };
+}
+
 export function validateIntegrationSummary(agent, summary) {
   if (!summary?.integration) {
     return {

package/scripts/wave-orchestrator/config.mjs

@@ -28,6 +28,7 @@ export const DEFAULT_INTEGRATION_ROLE_PROMPT_PATH = "docs/agents/wave-integratio
 export const DEFAULT_DOCUMENTATION_ROLE_PROMPT_PATH =
   "docs/agents/wave-documentation-role.md";
 export const DEFAULT_SECURITY_ROLE_PROMPT_PATH = "docs/agents/wave-security-role.md";
+export const DEFAULT_DESIGN_ROLE_PROMPT_PATH = "docs/agents/wave-design-role.md";
 export const DEFAULT_TERMINALS_PATH = ".vscode/terminals.json";
 export const DEFAULT_DOCS_DIR = "docs";
 export const DEFAULT_STATE_ROOT = ".tmp";
@@ -348,6 +349,10 @@ function normalizeRoles(rawRoles = {}) {
       rawRoles.securityRolePromptPath || DEFAULT_SECURITY_ROLE_PROMPT_PATH,
       "roles.securityRolePromptPath",
     ),
+    designRolePromptPath: normalizeRepoRelativePath(
+      rawRoles.designRolePromptPath || DEFAULT_DESIGN_ROLE_PROMPT_PATH,
+      "roles.designRolePromptPath",
+    ),
   };
 }
 

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

@@ -36,6 +36,10 @@ import { readWaveRelaunchPlanSnapshot, readWaveRetryOverride, resolveRetryOverri
 import { flushWaveControlQueue, readWaveControlQueueState } from "./wave-control-client.mjs";
 import { readAgentExecutionSummary, validateImplementationSummary } from "./agent-state.mjs";
 import { isContEvalReportOnlyAgent, isSecurityReviewAgent } from "./role-helpers.mjs";
+import {
+  buildSignalStatusLine,
+  syncWaveSignalProjections,
+} from "./signals.mjs";
 
 function printUsage() {
   console.log(`Usage:
@@ -676,6 +680,7 @@ export function buildControlStatusPayload({ lanePaths, wave, agentId = "" }) {
     proofBundles: (proofRegistry?.entries || []).filter(
       (entry) => !agentId || entry.agentId === agentId,
     ),
+    feedbackRequests,
     selectionSource: selection.source,
     rerunRequest,
     relaunchPlan,
@@ -690,6 +695,7 @@ function ensureWaveStateDirs(lanePaths) {
   ensureDirectory(lanePaths.controlPlaneDir);
   ensureDirectory(lanePaths.assignmentsDir);
   ensureDirectory(lanePaths.inboxesDir);
+  ensureDirectory(lanePaths.signalsDir);
   ensureDirectory(lanePaths.messageboardsDir);
   ensureDirectory(lanePaths.docsQueueDir);
   ensureDirectory(lanePaths.ledgerDir);
@@ -714,6 +720,9 @@ function printStatus(payload) {
     ? `${payload.blockingEdge.kind} ${payload.blockingEdge.id}: ${payload.blockingEdge.detail}`
     : "none";
   console.log(`lane=${payload.lane} wave=${payload.wave} phase=${payload.phase}`);
+  if (payload.signals?.wave) {
+    console.log(buildSignalStatusLine(payload.signals.wave, payload));
+  }
   console.log(`blocking=${blocking}`);
   if (payload.nextTimer) {
     console.log(`next-timer=${payload.nextTimer.kind} ${payload.nextTimer.taskId} at ${payload.nextTimer.at}`);
@@ -901,6 +910,16 @@ export async function runControlCli(argv) {
       wave,
       agentId: options.agent || "",
     });
+    const signalSync = syncWaveSignalProjections({
+      lanePaths,
+      wave,
+      statusPayload: payload,
+      includeResident: Boolean(options.orchestratorId),
+    });
+    payload.signals = {
+      wave: signalSync.wave?.snapshot || null,
+      agents: (signalSync.agents || []).map((entry) => entry.snapshot),
+    };
     if (options.json) {
       console.log(JSON.stringify(payload, null, 2));
     } else {