create-cmp-cli 0.22.0 → 0.24.0

package/template/qa/lib/harness-region.mjs

@@ -53,17 +53,58 @@ import path from "node:path";
  */
 export const HARNESS_DIRS = ["qa", "qa/lib"];
 
+/**
+ * The lane's OWN tests, when a project carries them (payment-blueprint's
+ * qa/test/**, 2026-09-03). Every `.mjs` under it, recursively, is in the
+ * region: the tests that prove the gates are locked WITH the gates, or the
+ * lane can no longer tell you that the suite vouching for its verdicts is the
+ * one it was locked with — a narrower claim in the same words, which is the
+ * failure this mechanism exists to prevent. A Compose app has no qa/test and
+ * its region (and lock) is unchanged.
+ */
+export const HARNESS_TEST_DIR = "qa/test";
+
+/**
+ * DECLARATIONS the lane READS to decide what it attests — locked for the same
+ * reason verify.mjs is. payment-blueprint's planted proof (2026-09-03): remove
+ * one entry from qa/verified-surface.json and 203 files — the whole backend —
+ * stop being attested; the next lane run mints a fresh receipt over the smaller
+ * surface, harnessIntegrity PASS, nothing in the chain says the coverage moved.
+ * An edited checker and an edited definition of what the checker looks at are
+ * the same attack. State a lane WRITES (approvals.json, comments.json, the
+ * journal, evidence/) stays out — that is the EXCLUDED_PREFIXES distinction.
+ * Neither file exists in a Compose app by default; its region is unchanged.
+ */
+export const HARNESS_DECLARATIONS = ["qa/verified-surface.json", "qa/harness-manifest.json"];
+
 /**
  * Is this project-relative path part of the machine-owned harness region?
  * @param {string} relPath project-relative path, "/"-separated
  * @returns {boolean}
  */
 export function isHarnessFile(relPath) {
-  if (typeof relPath !== "string" || !relPath.endsWith(".mjs")) return false;
+  if (typeof relPath !== "string") return false;
+  if (HARNESS_DECLARATIONS.includes(relPath)) return true;
+  if (!relPath.endsWith(".mjs")) return false;
+  if (relPath.startsWith(`${HARNESS_TEST_DIR}/`)) return true;
   const dir = relPath.includes("/") ? relPath.slice(0, relPath.lastIndexOf("/")) : "";
   return HARNESS_DIRS.includes(dir);
 }
 
+function walkMjs(dirAbs, relPrefix, out) {
+  let entries;
+  try {
+    entries = fs.readdirSync(dirAbs, { withFileTypes: true });
+  } catch {
+    return;
+  }
+  for (const ent of entries) {
+    const rel = `${relPrefix}/${ent.name}`;
+    if (ent.isDirectory()) walkMjs(path.join(dirAbs, ent.name), rel, out);
+    else if (ent.isFile() && isHarnessFile(rel)) out.push(rel);
+  }
+}
+
 /**
  * Every machine-owned file present under `root`, as project-relative posix
  * paths, sorted — so the list (and any hash over it) is deterministic.
@@ -85,7 +126,14 @@ export function listHarnessFiles(root) {
       if (isHarnessFile(rel)) found.push(rel);
     }
   }
-  return found.sort();
+  walkMjs(path.join(root, HARNESS_TEST_DIR), HARNESS_TEST_DIR, found);
+  // A declaration directly under qa/ is already seen by the scan above (it is
+  // a harness file by name); the explicit loop covers one that lives deeper.
+  // Deduplicated so no path is hashed twice.
+  for (const rel of HARNESS_DECLARATIONS) {
+    if (fs.existsSync(path.join(root, ...rel.split("/")))) found.push(rel);
+  }
+  return [...new Set(found)].sort();
 }
 
 /** sha256 of one file's bytes, hex. */

package/template/qa/lib/inputs-hash.mjs

@@ -69,6 +69,11 @@ const EXCLUDED_PREFIXES = [
   "qa/.plan.json",
   "qa/.request.json",
   "qa/.plan-history.jsonl",
+  // Who is typing right now (qa/lib/agent-hold.mjs). A liveness declaration
+  // that could invalidate a receipt would mean an agent saying "I am here"
+  // un-proves the tree — the exact inversion this family of exclusions exists
+  // to prevent.
+  "qa/.agent-hold.json",
   "qa/evidence",
   "qa-artifacts",
   "qa/comments.json",

package/template/qa/lib/steps-cmp.mjs

@@ -1244,7 +1244,7 @@ const stepsForProfile = {
   // end-to-end lane — every pure-Node step through the REAL runner, marker,
   // receipt and journal, and NO Gradle, no device, no network. Its job is to
   // prove the framework RETURNS, fast, in both directions, before any real
-  // work is pointed at it. scripts/framework-check.mjs drives it: PASS on a
+  // work is pointed at it. qa/framework-check.mjs drives it: PASS on a
   // fresh scaffold, then FAIL BY NAME on one planted spec edit, each bounded
   // in seconds. Its receipt is refused as done-evidence (qa/receipt-check.mjs)
   // exactly like --fast: it proves the instrument, never the change.

package/template/qa/plan.mjs

@@ -10,6 +10,17 @@
 //   node qa/plan.mjs --done                            # close the chain
 //   node qa/plan.mjs --clear                           # a landed request leaves no stale windshield
 //
+//   node qa/plan.mjs --hold "adopting the ports" [--as <name>]   # I am working in this tree
+//   node qa/plan.mjs --beat ["what I am on now"]                 # still here (every few minutes)
+//   node qa/plan.mjs --release                                   # done, or gone
+//
+// The hold is LIVENESS, not a lock: nothing waits on it and it gates nothing.
+// It exists so "is the agent working or wedged?" is `tail` on a file instead of
+// filesystem archaeology — the question that got a healthy agent killed
+// mid-proof on 2026-09-04 — and so the Stop hook can say "wait for it" instead
+// of "run the lane" at a tree that would not compile. A heartbeat older than
+// five minutes is a crashed writer; a hold older than the ceiling is a wedge.
+//
 // Unlike walk-status (a fail-open status surface), this CLI is a WRITER the
 // agent invokes deliberately: bad input gets a refusal and exit 1, because a
 // silently-dropped declaration would leave the surfaces lying about position.
@@ -18,6 +29,7 @@ import path from "node:path";
 import { fileURLToPath } from "node:url";
 
 import { deriveChain, markStep, readPlan, renderChain, setPlan, clearPlan } from "./lib/plan.mjs";
+import { assessHold, beatHold, claimHold, describeHold, readHold, releaseHold } from "./lib/agent-hold.mjs";
 
 const ROOT = path.resolve(path.dirname(fileURLToPath(import.meta.url)), "..");
 const args = process.argv.slice(2);
@@ -37,7 +49,24 @@ function out(result) {
   process.exit(0);
 }
 
-if (args.includes("--set")) {
+function holdOut(result) {
+  if (!result.ok) {
+    process.stderr.write(`plan: ${result.error}\n`);
+    process.exit(1);
+  }
+  const line = describeHold(assessHold(readHold(ROOT)));
+  process.stdout.write(`${line ?? "No agent holds this tree."}\n`);
+  process.exit(0);
+}
+
+if (args.includes("--hold")) {
+  holdOut(claimHold(ROOT, { holder: valueOf("--as") ?? process.env.CMP_AGENT ?? "an agent", note: valueOf("--hold") ?? "" }));
+} else if (args.includes("--beat")) {
+  const note = valueOf("--beat");
+  holdOut(beatHold(ROOT, note === null ? {} : { note }));
+} else if (args.includes("--release")) {
+  holdOut(releaseHold(ROOT));
+} else if (args.includes("--set")) {
   const spec = valueOf("--set");
   if (spec === null) {
     process.stderr.write('plan: --set needs a value: --set "step | step | …"\n');

package/template/qa/receipt-check.mjs

@@ -21,6 +21,7 @@ import { fileURLToPath } from "node:url";
 
 import { computeInputsHash } from "./lib/inputs-hash.mjs";
 import { evaluateReceipt, readReceipt } from "./lib/receipt-validate.mjs";
+import { readHold, assessHold, describeHold, holdExplains } from "./lib/agent-hold.mjs";
 
 const ROOT = path.resolve(path.dirname(fileURLToPath(import.meta.url)), "..");
 
@@ -175,12 +176,24 @@ if (asHook) {
     // INSTRUCTION: "run the lane" is wrong advice when one is already running,
     // and a gate that tells you to do the thing you are doing trains you to
     // stop reading it.
+    //
+    // An agent HOLDING the tree is the same shape of correction one level out:
+    // a lane in flight explains a receipt that is about to arrive, a hold
+    // explains a tree that is mid-edit and would not compile if you ran one.
+    // Reported ~15 false alarms in one evening at payment-blueprint, every one
+    // of which should have said "wait". It only ever changes the instruction —
+    // and only for the two refusals a working agent legitimately causes
+    // (holdExplains), never for a FAIL, a forgery or a skipped device tier,
+    // where the hold is not the cause and offering it would misdirect.
     const flight = laneInFlight();
+    const hold = holdExplains(result, readReceipt(ROOT)) ? assessHold(readHold(ROOT)) : null;
     const act = flight
       ? `A full check is ALREADY RUNNING${flight.step ? ` (${flight.step}${flight.index && flight.total ? `, step ${flight.index} of ${flight.total}` : ""})` : ""} — ` +
         `wait for it to finish and commit its receipt. Do NOT start a second one; two lanes fight over the same build directory.`
-      : "Run `node qa/verify.mjs` (it checks every promise and writes the receipt), " +
-        "commit the receipt, or see README §Verification enforcement to bypass.";
+      : hold?.held
+        ? describeHold(hold)
+        : "Run `node qa/verify.mjs` (it checks every promise and writes the receipt), " +
+          "commit the receipt, or see README §Verification enforcement to bypass.";
     process.stderr.write(
       `■ Prove — not done: the promises are not yet checked against this tree. ${result.reason}. ${act}\n`,
     );

package/template/qa/verify.mjs

@@ -104,7 +104,7 @@ Profiles:
   smoke     the smallest end-to-end lane: every pure-Node gate through the real
             runner, receipt and journal — no Gradle, no device. Seconds. Proves the
             FRAMEWORK returns, both ways; never the change (its receipt is refused
-            as done-evidence). Driven by scripts/framework-check.mjs.
+            as done-evidence). Driven by qa/framework-check.mjs.
   scaffold  spec coverage + build + unit tests (what \`create-cmp --verify\`
             proves at stamp time)
   local     everything; device-dependent steps SKIP when no device is