audit-tools 0.53.0 → 0.54.0

package/dist/shared/prompts.d.ts

@@ -27,12 +27,27 @@ export interface CacheablePromptParts {
  */
 export declare function buildCacheablePrompt(parts: CacheablePromptParts): string;
 /**
- * Host instruction emitted in dispatch step prompts: each subagent should
- * receive its `prompt_path` file path and follow it directly. Loading worker
- * prompts into the main conversation inflates context for no benefit — the
- * worker executes in its own context and reports results back through its
- * assigned result path. Single-sourced so audit-code and remediate-code stay
- * in parity on the dispatch handoff policy.
+ * The host-facing vocabulary for where a lane runs. Every phrase names the
+ * NEED — a context, separate or independent — and never a delegation mechanism:
+ * hosts differ in how (or whether) they can open another context, and a
+ * mechanism noun is an instruction a host without that mechanism cannot follow.
+ * `tests/shared/host-prompt-vocabulary.test.ts` holds every string literal in
+ * the shipped code to this.
+ *
+ * - `INDEPENDENT_CONTEXT`: a review lane that must not be judged by the agent
+ *   that drove the work under review.
+ * - `SEPARATE_CONTEXT_OR_SELF`: an ordinary lane, run apart from the driving
+ *   conversation when the host can, else by the driver itself.
+ */
+export declare const INDEPENDENT_CONTEXT = "an independent context that did not drive this audit";
+export declare const SEPARATE_CONTEXT_OR_SELF = "in a separate context when the host can, else yourself";
+/**
+ * Host instruction emitted in dispatch step prompts: each lane handed to a
+ * separate context receives its `prompt_path` file path and follows it
+ * directly. Loading worker prompts into the main conversation inflates context
+ * for no benefit — the worker executes in its own context and reports results
+ * back through its assigned result path. Single-sourced so audit-code and
+ * remediate-code stay in parity on the dispatch handoff policy.
  */
 export declare const DISPATCH_PROMPT_HANDOFF_NOTE: string;
 /**
@@ -46,7 +61,7 @@ export declare const DISPATCH_PROMPT_HANDOFF_NOTE: string;
  *
  * ⚠ THE MANDATE STATES THE NEED, NEVER A MECHANISM. It used to say "dispatch it
  * to a fresh, independent sub-agent", which names one way to get independence
- * and presumes the host has it — in-process subagents are not universal, and a
+ * and presumes the host has it — in-process delegation is not universal, and a
  * host without them read an instruction it could not follow (the same defect the
  * former contract-pipeline fan-out carried). Independence is a property of the
  * CONTEXT, so that is what the text requires and the host owns the mechanism.
@@ -86,7 +101,7 @@ export declare function renderFanoutExecutionLines(params: {
         };
         reviewRequirement?: "ordinary" | "independent" | "degraded_allowed";
     }[];
-    /** Host-declared max concurrent subagents, when known. */
+    /** Host-declared max concurrent lanes, when known. */
     concurrencyHint?: number | null;
     /** A driver cannot execute these lanes itself; unavailable independence stops the step. */
     independenceRequired?: boolean;

package/dist/shared/prompts.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../../src/shared/prompts.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,+BAA+B,CAAC;AAIvE;;;;;;GAMG;AACH,MAAM,WAAW,oBAAoB;IACnC;;0BAEsB;IACtB,YAAY,EAAE,MAAM,CAAC;IACrB,uEAAuE;IACvE,eAAe,EAAE,MAAM,CAAC;CACzB;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,oBAAoB,CAAC,KAAK,EAAE,oBAAoB,GAAG,MAAM,CAMxE;AAED;;;;;;;GAOG;AACH,eAAO,MAAM,4BAA4B,QAG+C,CAAC;AAEzF;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,8BAA8B,CAC5C,KAAK,CAAC,EAAE,OAAO,GAAG,MAAM,EACxB,WAAW,GAAE,iBAA0E,GACtF,MAAM,CAcR;AAED;;;;;;;;GAQG;AAEH,wBAAgB,0BAA0B,CAAC,MAAM,EAAE;IACjD;;;;;;OAMG;IACH,KAAK,EAAE;QACL,KAAK,EAAE,MAAM,CAAC;QACd,UAAU,EAAE,MAAM,CAAC;QACnB,UAAU,CAAC,EAAE,MAAM,CAAC;QACpB,MAAM,CAAC,EAAE;YAAE,IAAI,EAAE,MAAM,CAAC;YAAC,UAAU,EAAE,MAAM,CAAC;YAAC,IAAI,EAAE,MAAM,CAAA;SAAE,CAAC;QAC5D,iBAAiB,CAAC,EAAE,UAAU,GAAG,aAAa,GAAG,kBAAkB,CAAC;KACrE,EAAE,CAAC;IACJ,0DAA0D;IAC1D,eAAe,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAChC,2FAA2F;IAC3F,oBAAoB,CAAC,EAAE,OAAO,CAAC;CAChC,GAAG,MAAM,EAAE,CA4CX;AAED;;;;;;;GAOG;AACH,wBAAgB,qBAAqB,CAAC,cAAc,EAAE,MAAM,GAAG,MAAM,CAMpE"}
+{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../../src/shared/prompts.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,+BAA+B,CAAC;AAIvE;;;;;;GAMG;AACH,MAAM,WAAW,oBAAoB;IACnC;;0BAEsB;IACtB,YAAY,EAAE,MAAM,CAAC;IACrB,uEAAuE;IACvE,eAAe,EAAE,MAAM,CAAC;CACzB;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,oBAAoB,CAAC,KAAK,EAAE,oBAAoB,GAAG,MAAM,CAMxE;AAED;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,mBAAmB,yDAAyD,CAAC;AAC1F,eAAO,MAAM,wBAAwB,2DAA2D,CAAC;AAEjG;;;;;;;GAOG;AACH,eAAO,MAAM,4BAA4B,QAG+C,CAAC;AAEzF;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,8BAA8B,CAC5C,KAAK,CAAC,EAAE,OAAO,GAAG,MAAM,EACxB,WAAW,GAAE,iBAA0E,GACtF,MAAM,CAcR;AAED;;;;;;;;GAQG;AAEH,wBAAgB,0BAA0B,CAAC,MAAM,EAAE;IACjD;;;;;;OAMG;IACH,KAAK,EAAE;QACL,KAAK,EAAE,MAAM,CAAC;QACd,UAAU,EAAE,MAAM,CAAC;QACnB,UAAU,CAAC,EAAE,MAAM,CAAC;QACpB,MAAM,CAAC,EAAE;YAAE,IAAI,EAAE,MAAM,CAAC;YAAC,UAAU,EAAE,MAAM,CAAC;YAAC,IAAI,EAAE,MAAM,CAAA;SAAE,CAAC;QAC5D,iBAAiB,CAAC,EAAE,UAAU,GAAG,aAAa,GAAG,kBAAkB,CAAC;KACrE,EAAE,CAAC;IACJ,sDAAsD;IACtD,eAAe,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAChC,2FAA2F;IAC3F,oBAAoB,CAAC,EAAE,OAAO,CAAC;CAChC,GAAG,MAAM,EAAE,CA4CX;AAED;;;;;;;GAOG;AACH,wBAAgB,qBAAqB,CAAC,cAAc,EAAE,MAAM,GAAG,MAAM,CAMpE"}

package/dist/shared/prompts.js

@@ -17,14 +17,29 @@ export function buildCacheablePrompt(parts) {
     return `${sharedPrefix}\n\n${perAgentPayload}`;
 }
 /**
- * Host instruction emitted in dispatch step prompts: each subagent should
- * receive its `prompt_path` file path and follow it directly. Loading worker
- * prompts into the main conversation inflates context for no benefit — the
- * worker executes in its own context and reports results back through its
- * assigned result path. Single-sourced so audit-code and remediate-code stay
- * in parity on the dispatch handoff policy.
+ * The host-facing vocabulary for where a lane runs. Every phrase names the
+ * NEED — a context, separate or independent — and never a delegation mechanism:
+ * hosts differ in how (or whether) they can open another context, and a
+ * mechanism noun is an instruction a host without that mechanism cannot follow.
+ * `tests/shared/host-prompt-vocabulary.test.ts` holds every string literal in
+ * the shipped code to this.
+ *
+ * - `INDEPENDENT_CONTEXT`: a review lane that must not be judged by the agent
+ *   that drove the work under review.
+ * - `SEPARATE_CONTEXT_OR_SELF`: an ordinary lane, run apart from the driving
+ *   conversation when the host can, else by the driver itself.
+ */
+export const INDEPENDENT_CONTEXT = "an independent context that did not drive this audit";
+export const SEPARATE_CONTEXT_OR_SELF = "in a separate context when the host can, else yourself";
+/**
+ * Host instruction emitted in dispatch step prompts: each lane handed to a
+ * separate context receives its `prompt_path` file path and follows it
+ * directly. Loading worker prompts into the main conversation inflates context
+ * for no benefit — the worker executes in its own context and reports results
+ * back through its assigned result path. Single-sourced so audit-code and
+ * remediate-code stay in parity on the dispatch handoff policy.
  */
-export const DISPATCH_PROMPT_HANDOFF_NOTE = "For each subagent, pass its `prompt_path` to the agent tool directly — " +
+export const DISPATCH_PROMPT_HANDOFF_NOTE = "For each lane handed to a separate context, pass its `prompt_path` as the instruction directly — " +
     "do not read the worker prompt file into this conversation. " +
     "Each worker executes in its own context and writes only to its assigned result path.";
 /**
@@ -38,7 +53,7 @@ export const DISPATCH_PROMPT_HANDOFF_NOTE = "For each subagent, pass its `prompt
  *
  * ⚠ THE MANDATE STATES THE NEED, NEVER A MECHANISM. It used to say "dispatch it
  * to a fresh, independent sub-agent", which names one way to get independence
- * and presumes the host has it — in-process subagents are not universal, and a
+ * and presumes the host has it — in-process delegation is not universal, and a
  * host without them read an instruction it could not follow (the same defect the
  * former contract-pipeline fan-out carried). Independence is a property of the
  * CONTEXT, so that is what the text requires and the host owns the mechanism.
@@ -95,8 +110,8 @@ export function renderFanoutExecutionLines(params) {
         : [];
     return [
         (params.independenceRequired || params.lanes.some(lane => lane.reviewRequirement === "independent"))
-            ? `Execute the ${n} lane prompt file${plural} below in an independent context that did not drive this audit. The host chooses how to obtain that context. If none is available, stop and report that this review could not be performed independently. Do not write a result or run the continue command in that case; this overrides the output and continuation instructions below. An unavailable review is not an empty findings result.`
-            : `Execute the ${n} lane prompt file${plural} below: dispatch one subagent per file if a subagent facility exists, else read and follow each file sequentially yourself. The same files and result paths apply either way.`,
+            ? `Execute the ${n} lane prompt file${plural} below in ${INDEPENDENT_CONTEXT}. The host chooses how to obtain that context. If none is available, stop and report that this review could not be performed independently. Do not write a result or run the continue command in that case; this overrides the output and continuation instructions below. An unavailable review is not an empty findings result.`
+            : `Execute the ${n} lane prompt file${plural} below, each ${SEPARATE_CONTEXT_OR_SELF} — run separate contexts in parallel where the host can; otherwise read and follow each file sequentially yourself. The same files and result paths apply either way.`,
         "",
         ...concurrency,
         ...(params.lanes.some((lane) => lane.demand !== undefined)
@@ -113,7 +128,7 @@ export function renderFanoutExecutionLines(params) {
         "",
         (params.independenceRequired || params.lanes.some(lane => lane.reviewRequirement === "independent"))
             ? "Pass each lane's prompt path verbatim to its independent executor. Lane prompt files carry no continue-command; return here once the independently produced lane results exist."
-            : "When dispatching a lane to a subagent, pass its prompt path verbatim as the instruction — do not read the lane file into this conversation. When executing a lane yourself, read and follow its file directly. Lane prompt files carry no continue-command; return here once the lane results exist.",
+            : "When handing a lane to a separate context, pass its prompt path verbatim as the instruction — do not read the lane file into this conversation. When executing a lane yourself, read and follow its file directly. Lane prompt files carry no continue-command; return here once the lane results exist.",
     ];
 }
 /**

package/dist/shared/prompts.js.map

@@ -1 +1 @@
-{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../../src/shared/prompts.ts"],"names":[],"mappings":"AAoBA;;;;;;;;;;GAUG;AACH,MAAM,UAAU,oBAAoB,CAAC,KAA2B;IAC9D,MAAM,EAAE,YAAY,EAAE,eAAe,EAAE,GAAG,KAAK,CAAC;IAChD,IAAI,YAAY,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QAC9B,OAAO,eAAe,CAAC;IACzB,CAAC;IACD,OAAO,GAAG,YAAY,OAAO,eAAe,EAAE,CAAC;AACjD,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,4BAA4B,GACvC,yEAAyE;IACzE,6DAA6D;IAC7D,sFAAsF,CAAC;AAEzF;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,8BAA8B,CAC5C,KAAwB,EACxB,cAAiC,KAAK,KAAK,OAAO,CAAC,CAAC,CAAC,kBAAkB,CAAC,CAAC,CAAC,aAAa;IAEvF,IAAI,WAAW,KAAK,UAAU;QAAE,OAAO,EAAE,CAAC;IAC1C,IAAI,WAAW,KAAK,kBAAkB,EAAE,CAAC;QACvC,OAAO;;;CAGV,CAAC;IACA,CAAC;IACD,OAAO;;;;;CAKR,CAAC;AACF,CAAC;AAED;;;;;;;;GAQG;AACH,yFAAyF;AACzF,MAAM,UAAU,0BAA0B,CAAC,MAmB1C;IACC,MAAM,CAAC,GAAG,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC;IAC9B,4EAA4E;IAC5E,6EAA6E;IAC7E,2EAA2E;IAC3E,wBAAwB;IACxB,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC;QACZ,OAAO;YACL,2GAA2G;SAC5G,CAAC;IACJ,CAAC;IACD,MAAM,MAAM,GAAG,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,CAAC;IAClC,MAAM,WAAW,GACf,MAAM,CAAC,eAAe,IAAI,IAAI,IAAI,CAAC,GAAG,CAAC;QACrC,CAAC,CAAC;YACE,iCAAiC,MAAM,CAAC,eAAe,qBAAqB;YAC5E,EAAE;SACH;QACH,CAAC,CAAC,EAAE,CAAC;IACT,OAAO;QACL,CAAC,MAAM,CAAC,oBAAoB,IAAI,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,iBAAiB,KAAK,aAAa,CAAC,CAAC;YAClG,CAAC,CAAC,eAAe,CAAC,oBAAoB,MAAM,iYAAiY;YAC7a,CAAC,CAAC,eAAe,CAAC,oBAAoB,MAAM,+KAA+K;QAC7N,EAAE;QACF,GAAG,WAAW;QACd,GAAG,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,MAAM,KAAK,SAAS,CAAC;YACxD,CAAC,CAAC;gBACE,mMAAmM;gBACnM,EAAE;aACH;YACH,CAAC,CAAC,EAAE,CAAC;QACP,GAAG,MAAM,CAAC,KAAK,CAAC,GAAG,CACjB,CAAC,IAAI,EAAE,EAAE,CACP,OAAO,IAAI,CAAC,KAAK,OAAO,IAAI,CAAC,UAAU,EAAE;YACzC,CAAC,IAAI,CAAC,MAAM;gBACV,CAAC,CAAC,kBAAkB,IAAI,CAAC,MAAM,CAAC,IAAI,gBAAgB,IAAI,CAAC,MAAM,CAAC,UAAU,UAAU,IAAI,CAAC,MAAM,CAAC,IAAI,GAAG;gBACvG,CAAC,CAAC,EAAE,CAAC;YACP,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC,CAAC,uBAAuB,IAAI,CAAC,UAAU,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,CACpE;QACD,EAAE;QACF,CAAC,MAAM,CAAC,oBAAoB,IAAI,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,iBAAiB,KAAK,aAAa,CAAC,CAAC;YAClG,CAAC,CAAC,iLAAiL;YACnL,CAAC,CAAC,sSAAsS;KAC3S,CAAC;AACJ,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,qBAAqB,CAAC,cAAsB;IAC1D,OAAO,CACL,0EAA0E;QAC1E,8CAA8C,cAAc,OAAO;QACnE,yEAAyE,CAC1E,CAAC;AACJ,CAAC"}
+{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../../src/shared/prompts.ts"],"names":[],"mappings":"AAoBA;;;;;;;;;;GAUG;AACH,MAAM,UAAU,oBAAoB,CAAC,KAA2B;IAC9D,MAAM,EAAE,YAAY,EAAE,eAAe,EAAE,GAAG,KAAK,CAAC;IAChD,IAAI,YAAY,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QAC9B,OAAO,eAAe,CAAC;IACzB,CAAC;IACD,OAAO,GAAG,YAAY,OAAO,eAAe,EAAE,CAAC;AACjD,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,sDAAsD,CAAC;AAC1F,MAAM,CAAC,MAAM,wBAAwB,GAAG,wDAAwD,CAAC;AAEjG;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,4BAA4B,GACvC,mGAAmG;IACnG,6DAA6D;IAC7D,sFAAsF,CAAC;AAEzF;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,8BAA8B,CAC5C,KAAwB,EACxB,cAAiC,KAAK,KAAK,OAAO,CAAC,CAAC,CAAC,kBAAkB,CAAC,CAAC,CAAC,aAAa;IAEvF,IAAI,WAAW,KAAK,UAAU;QAAE,OAAO,EAAE,CAAC;IAC1C,IAAI,WAAW,KAAK,kBAAkB,EAAE,CAAC;QACvC,OAAO;;;CAGV,CAAC;IACA,CAAC;IACD,OAAO;;;;;CAKR,CAAC;AACF,CAAC;AAED;;;;;;;;GAQG;AACH,yFAAyF;AACzF,MAAM,UAAU,0BAA0B,CAAC,MAmB1C;IACC,MAAM,CAAC,GAAG,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC;IAC9B,4EAA4E;IAC5E,6EAA6E;IAC7E,2EAA2E;IAC3E,wBAAwB;IACxB,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC;QACZ,OAAO;YACL,2GAA2G;SAC5G,CAAC;IACJ,CAAC;IACD,MAAM,MAAM,GAAG,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,CAAC;IAClC,MAAM,WAAW,GACf,MAAM,CAAC,eAAe,IAAI,IAAI,IAAI,CAAC,GAAG,CAAC;QACrC,CAAC,CAAC;YACE,iCAAiC,MAAM,CAAC,eAAe,qBAAqB;YAC5E,EAAE;SACH;QACH,CAAC,CAAC,EAAE,CAAC;IACT,OAAO;QACL,CAAC,MAAM,CAAC,oBAAoB,IAAI,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,iBAAiB,KAAK,aAAa,CAAC,CAAC;YAClG,CAAC,CAAC,eAAe,CAAC,oBAAoB,MAAM,aAAa,mBAAmB,mUAAmU;YAC/Y,CAAC,CAAC,eAAe,CAAC,oBAAoB,MAAM,gBAAgB,wBAAwB,uKAAuK;QAC7P,EAAE;QACF,GAAG,WAAW;QACd,GAAG,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,MAAM,KAAK,SAAS,CAAC;YACxD,CAAC,CAAC;gBACE,mMAAmM;gBACnM,EAAE;aACH;YACH,CAAC,CAAC,EAAE,CAAC;QACP,GAAG,MAAM,CAAC,KAAK,CAAC,GAAG,CACjB,CAAC,IAAI,EAAE,EAAE,CACP,OAAO,IAAI,CAAC,KAAK,OAAO,IAAI,CAAC,UAAU,EAAE;YACzC,CAAC,IAAI,CAAC,MAAM;gBACV,CAAC,CAAC,kBAAkB,IAAI,CAAC,MAAM,CAAC,IAAI,gBAAgB,IAAI,CAAC,MAAM,CAAC,UAAU,UAAU,IAAI,CAAC,MAAM,CAAC,IAAI,GAAG;gBACvG,CAAC,CAAC,EAAE,CAAC;YACP,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC,CAAC,uBAAuB,IAAI,CAAC,UAAU,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,CACpE;QACD,EAAE;QACF,CAAC,MAAM,CAAC,oBAAoB,IAAI,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,iBAAiB,KAAK,aAAa,CAAC,CAAC;YAClG,CAAC,CAAC,iLAAiL;YACnL,CAAC,CAAC,0SAA0S;KAC/S,CAAC;AACJ,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,qBAAqB,CAAC,cAAsB;IAC1D,OAAO,CACL,0EAA0E;QAC1E,8CAA8C,cAAc,OAAO;QACnE,yEAAyE,CAC1E,CAAC;AACJ,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "audit-tools",
-  "version": "0.53.0",
+  "version": "0.54.0",
   "private": false,
   "license": "ISC",
   "description": "Provider-neutral code auditing and remediation workflows for arbitrary repositories.",
@@ -116,6 +116,7 @@
     "generate:shard-baseline": "node scripts/shared/generate-vitest-shard-baseline.mjs",
     "check:orphan-modules": "node scripts/check-orphan-modules.mjs",
     "check:loop-core-closure": "node scripts/check-loop-core-closure.mjs",
+    "check:loop-core-attestations": "node scripts/check-loop-core-attestations.mjs",
     "check:pin-obligations": "node scripts/check-pin-obligations.mjs",
     "check:contract-sites": "node --import tsx/esm scripts/check-contract-sites.mjs",
     "check:sites-pinned": "node scripts/check-sites-pinned.mjs",

package/scripts/shared/primitives.mjs

@@ -21,6 +21,10 @@
 // The gate's rule tables list BOTH homes, so a re-roll anywhere in either tree
 // is red. Change one and change the other — the rules treat them as one home in
 // two files, which is what makes the divergence impossible to miss.
+//
+// `processAlive` is not a twin: it is the governance tree's one liveness probe,
+// imported by the prebuild guard and the dispatch lane and re-exported to the
+// test helpers.
 import { createHash } from "node:crypto";
 import { isAbsolute, relative, resolve, sep } from "node:path";
 
@@ -87,3 +91,19 @@ export function resolveWithinRoot(root, candidate, options = {}) {
   if (rel === ".." || rel.startsWith(`..${sep}`) || rel.startsWith("../")) return null;
   return absolutePath;
 }
+
+// sites-pinned: tests/shared/dispatch-lane-worktree.test.ts
+/**
+ * Whether a process with this pid exists. `kill(pid, 0)` sends no signal; it
+ * reports deliverability, so an EPERM answer still means the process EXISTS.
+ * A pid that is not a positive integer names no process.
+ */
+export function processAlive(pid) {
+  if (typeof pid !== "number" || !Number.isInteger(pid) || pid <= 0) return false;
+  try {
+    process.kill(pid, 0);
+    return true;
+  } catch (err) {
+    return /** @type {any} */ (err).code === "EPERM";
+  }
+}

package/skills/audit-code/SKILL.md

@@ -18,8 +18,8 @@ Normal usage should:
 
 audit-tools owns deterministic discovery, planning, persisted state, strict
 result ingestion, and synthesis. When semantic review is ready it emits a
-complete provider-neutral workload. Delegate those bounded items through the
-host's native subagent facilities when available, then return only the bound
+complete provider-neutral workload. Run those bounded items in separate
+contexts when the host can, then return only the bound
 result artifacts requested by the current prompt.
 
 If the host cannot delegate, complete exactly one emitted review item in the
@@ -36,21 +36,14 @@ audit-code ensure --quiet
 audit-code next-step
 ```
 
-When developing audit-tools itself, use the repository-local wrapper:
-
-```bash
-node audit-code.mjs ensure --quiet
-node audit-code.mjs next-step
-```
-
 The target-directory rule has one full statement in
 `skills/audit-code/audit-code.prompt.md` (whose absolute path `audit-code
 prompt-path` prints); follow it as written there. Do not add provider, model,
 quota, routing, or launch flags.
 
-Read the returned JSON only far enough to find `prompt_path`, then read and
-follow only that prompt. Do not inspect workload, result, schema, or state files
-unless the current prompt directs you to them. When it says to continue, call
+The command prints a JSON step record. Read the prompt file at its
+`prompt_path`, then follow only that prompt. Do not inspect workload, result,
+schema, or state files unless the current prompt directs you to them. When it says to continue, call
 `next-step` again. Stop when it says to stop.
 
 The package install seeds command and skill assets. Use `audit-code install`

package/skills/audit-code/audit-code.prompt.md

@@ -16,9 +16,6 @@ First bootstrap current assets:
 audit-code ensure --quiet
 ```
 
-When developing audit-tools itself, use `node audit-code.mjs` from the
-repository root.
-
 Preserve user arguments:
 
 - run from inside the target repository; every command resolves that repository's
@@ -32,12 +29,12 @@ Ask for exactly one step:
 audit-code next-step
 ```
 
-Read the returned JSON only far enough to find `prompt_path`, then read and
-follow only that prompt. Do not inspect workload, result, schema, or state files
-unless the current prompt directs you to them.
+The command prints a JSON step record. Read the prompt file at its
+`prompt_path`, then follow only that prompt. Do not inspect workload, result,
+schema, or state files unless the current prompt directs you to them.
 
-When the prompt emits semantic review items, assign them with the host's native
-subagent facilities when available. Do not send provider, model, quota,
+When the prompt emits semantic review items, run each in a separate context
+when the host can, else yourself, as the prompt directs. Do not send provider, model, quota,
 context-window, routing, or launch configuration to audit-tools. Write the
 prompt-bound result artifacts exactly where requested and let the next backend
 step validate and ingest them.

package/skills/audit-code/opencode-command-template.txt

@@ -3,10 +3,10 @@
 Use `audit-code next-step` as the primary interface to the audit workflow.
 
 1. Run `audit-code next-step` directly when shell access is available.
-2. Read the returned JSON far enough to find `prompt_path`, then read and follow the prompt file it points to.
+2. Read the prompt file at the returned step record's `prompt_path`, then follow it.
 3. When a step completes (not blocked), run `audit-code next-step` again.
 4. Stop when the step instructions say to stop.
 
-Use the `task` tool or equivalent for subagent dispatch when the step tells you to fan out review work.
+When the step tells you to fan out review work, run each lane in a separate context when the host can, else yourself.
 
 If shell access to `audit-code next-step` is unavailable, stop and report that no next-step interface is connected.

package/skills/remediate-code/SKILL.md

@@ -19,8 +19,7 @@ Normal usage should:
 The backend owns intake, contract planning, persisted state, dependency and
 phase safety, strict result ingestion, verification, and closeout. When
 implementation is ready it emits every eligible provider-neutral work item.
-Delegate bounded work through the host's native subagent facilities when
-available. The host returns prompt-bound commit and test evidence; the backend
+Run bounded work in separate contexts when the host can. The host returns prompt-bound commit and test evidence; the backend
 corroborates that evidence before it accepts completion.
 
 If the host cannot delegate, complete exactly one emitted work item in the
@@ -43,13 +42,12 @@ them as written there.
 Do not add capability, provider, model, quota, context-window, or concurrency
 flags.
 
-Read the returned JSON only far enough to find `prompt_path`, then read and
-follow only that prompt. Do not inspect workload, result, schema, or state files
-unless the current prompt directs you to them. When it says to continue, call
+The command prints a JSON step record. Read the prompt file at its
+`prompt_path`, then follow only that prompt. Do not inspect workload, result,
+schema, or state files unless the current prompt directs you to them. When it says to continue, call
 `next-step` again. Stop when it says to stop.
 
-When developing audit-tools itself, prefer `node remediate-code.mjs`. Use
-`remediate-code install` for repair or forced asset refresh.
+Use `remediate-code install` for repair or forced asset refresh.
 
 ## Development rule
 

package/skills/remediate-code/remediate-code.prompt.md

@@ -40,12 +40,12 @@ Then ask for exactly one step:
 remediate-code next-step
 ```
 
-Read the returned JSON only far enough to find `prompt_path`, then read and
-follow only that prompt. Do not inspect workload, result, schema, or state files
-unless the current prompt directs you to them.
+The command prints a JSON step record. Read the prompt file at its
+`prompt_path`, then follow only that prompt. Do not inspect workload, result,
+schema, or state files unless the current prompt directs you to them.
 
-When the prompt emits implementation items, assign them using the host's native
-subagent facilities when available. Do not send provider, model, quota,
+When the prompt emits implementation items, run each in a separate context
+when the host can, else yourself, as the prompt directs. Do not send provider, model, quota,
 context-window, routing, launch, or concurrency configuration to audit-tools.
 Write the bound result artifacts exactly where requested; the next backend step
 validates workload identity, worktree and commit evidence, changed files, and

package/dispatch/lens-definitions.json

@@ -1,46 +0,0 @@
-{
-  "correctness": {
-    "description": "Logic errors, incorrect algorithm implementations, off-by-one bugs, type mismatches, wrong return values, incorrect state transitions, missing null/undefined guards, misuse of APIs. Focus on code that does the wrong thing.",
-    "do_not_report": "Style issues, naming problems, missing tests, or findings that belong to other lenses."
-  },
-  "maintainability": {
-    "description": "Code that is hard to change safely: excessive function length, deep nesting, tight coupling between unrelated modules, poor naming, magic constants, duplicated logic, inconsistent abstractions, unclear public APIs. A specific high-value smell: the same logic, format, or contract implemented in two or more places and kept consistent by a test or by convention instead of extracted to one shared source — flag the duplication and recommend single-sourcing it (the sync test is a workaround for the missing abstraction, not the fix). The change-cost tell is 'every edit must be made in N places to stay correct.'",
-    "do_not_report": "Correctness bugs, test gaps, or operational concerns."
-  },
-  "tests": {
-    "description": "Test coverage gaps for important paths, tests that assert incorrect behavior (pinning bugs as expected), fragile or non-deterministic tests, missing negative/edge-case tests, tests that silently pass on stale builds (e.g. importing compiled dist/ rather than source). Also flag a test whose purpose is to keep two copies of logic/format/output in sync (a drift guard): the real defect is the duplication it polices, which should be extracted to one shared source so the guard is unnecessary — report the test as the symptom and call out the duplication to single-source.",
-    "do_not_report": "Source code bugs — report only issues with the tests themselves."
-  },
-  "security": {
-    "description": "Injection vulnerabilities (SQL, shell, path traversal), authentication/authorization flaws, secret exposure, insecure deserialization, privilege escalation, unsafe use of eval or child processes with user input.",
-    "do_not_report": "Performance or correctness issues that are not security-relevant."
-  },
-  "reliability": {
-    "description": "Failure modes without recovery, missing timeouts, unhandled promise rejections, race conditions, resource leaks (file handles, sockets, timers), incorrect retry logic, cascading failure risks.",
-    "do_not_report": "Correctness bugs that do not affect reliability under failure conditions."
-  },
-  "performance": {
-    "description": "Algorithmic inefficiencies (O(n²) where O(n) is possible), unnecessary re-computation, missing caching, synchronous blocking in hot paths, excessive memory allocation.",
-    "do_not_report": "Correctness bugs unrelated to performance."
-  },
-  "data_integrity": {
-    "description": "Missing input validation at trust boundaries, schema violations, inconsistent field naming across related schemas, data loss scenarios, missing required fields, enum values that are present in some schemas but not others.",
-    "do_not_report": "UI or presentation issues; operational or deployment concerns."
-  },
-  "operability": {
-    "description": "Missing or low-quality log output, error messages that don't help operators diagnose problems, missing progress indicators for long operations, no elapsed-time reporting, lack of dry-run or preview modes for destructive operations.",
-    "do_not_report": "Correctness bugs or deployment configuration."
-  },
-  "config_deployment": {
-    "description": "CI/CD pipeline correctness (wrong triggers, missing branch filters, floating version pins), deployment safety (no gate before publish, missing rollback), insecure secret handling in configs, mutable action tags that should be pinned to commit SHAs.",
-    "do_not_report": "Runtime code issues; findings that belong to other lenses."
-  },
-  "architecture": {
-    "description": "Big-picture design, conceptual elegance, over-engineering, under-engineering, appropriate use of abstractions, and identifying opportunities where custom code should be replaced by third-party tools or standard libraries. Flag a missing single source of truth: the same logic, format, or contract realized in multiple components where it should live in one shared module — the durable fix is extraction to that shared source, not a test or convention that keeps the copies in sync. Flag structural findings that span multiple components as 'systemic: true'.",
-    "do_not_report": "Minor style issues, localized logic bugs, or formatting."
-  },
-  "observability": {
-    "description": "Logging quality, telemetry, distributed tracing context, meaningful metrics, and error reporting context.",
-    "do_not_report": "Correctness bugs or deployment configuration."
-  }
-}