agents-inc 0.170.1 → 0.170.2

package/dist/hooks/init.js

@@ -1,33 +1,32 @@
 #!/usr/bin/env node
 import {
   runDashboardFlow
-} from "../chunk-NCWDK6L7.js";
-import "../chunk-44TE3RKH.js";
-import "../chunk-6HNXYYVF.js";
-import "../chunk-OYJQUA3D.js";
-import "../chunk-4AAOOAIN.js";
+} from "../chunk-YXKTY5WM.js";
+import "../chunk-3ED3KHHD.js";
+import "../chunk-PLFANHRZ.js";
+import "../chunk-YGDWHDOY.js";
+import "../chunk-P6CYS4JK.js";
 import "../chunk-OZXAJNLA.js";
-import "../chunk-F5EBEATU.js";
-import "../chunk-7RDMTR64.js";
-import "../chunk-F2BHT5C4.js";
-import "../chunk-HED2DAXZ.js";
-import "../chunk-3G7X2WKI.js";
-import "../chunk-BMRUNMPV.js";
-import "../chunk-JFLVEFFP.js";
-import "../chunk-RIPSGNLU.js";
+import "../chunk-PSUTNOQ2.js";
+import "../chunk-66AEVERM.js";
+import "../chunk-IWY5IR4F.js";
+import "../chunk-THO7LO5B.js";
+import "../chunk-5BNX73OU.js";
+import "../chunk-2YA4DDRM.js";
+import "../chunk-KIK5EZYD.js";
+import "../chunk-OCAVW6N5.js";
 import {
   EXIT_CODES
-} from "../chunk-V3KTSP3Q.js";
-import "../chunk-CLPUWOSA.js";
+} from "../chunk-GEMW5RQ2.js";
 import {
   findConfigLoadFailures,
   installationConfigsUnreadable,
   retiredSourceFolderIn,
   retiredSourceFolderUnsupported
-} from "../chunk-MQ6CGZNJ.js";
-import "../chunk-52HDHJ7I.js";
-import "../chunk-PJWGTNOX.js";
-import "../chunk-NQW25DCF.js";
+} from "../chunk-GAKVZNTX.js";
+import "../chunk-AUNRHWH4.js";
+import "../chunk-7C3PFRBU.js";
+import "../chunk-GHHJYNAN.js";
 
 // src/cli/hooks/init.ts
 import os from "os";

package/dist/hooks/init.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../src/cli/hooks/init.ts"],"sourcesContent":["import os from \"os\";\n\nimport { flush, type Hook } from \"@oclif/core\";\nimport { runDashboardFlow } from \"../commands/init.js\";\nimport { findConfigLoadFailures } from \"../lib/configuration/project-config.js\";\nimport { retiredSourceFolderIn } from \"../lib/installation/install-layout.js\";\nimport { EXIT_CODES } from \"../lib/exit-codes.js\";\nimport {\n  installationConfigsUnreadable,\n  retiredSourceFolderUnsupported,\n} from \"../utils/messages.js\";\n\nconst hook: Hook<\"init\"> = async function (options) {\n  sayTheRetiredSourceFolderIsUnsupported(process.cwd());\n\n  // No command: the dashboard, over the project's installation or else the global one\n  if (options.id === undefined) {\n    const projectDir = process.cwd();\n    // Left to the dashboard, the load error was swallowed by oclif's hook runner and the run\n    // printed the root help, as though nothing were installed.\n    const unreadable = await findConfigLoadFailures(projectDir);\n    if (unreadable.length > 0) {\n      this.error(installationConfigsUnreadable(unreadable), { exit: EXIT_CODES.ERROR });\n    }\n\n    const dashboard = await runDashboardFlow(projectDir, options.config);\n    if (dashboard === \"cancelled\") this.error(\"Cancelled\", { exit: EXIT_CODES.CANCELLED });\n    if (dashboard === \"shown\") await endRun(EXIT_CODES.SUCCESS);\n  }\n};\n\n/**\n * One bare line, once per run, while the project or HOME holds the retired source folder.\n *\n * Here because every command passes through this hook exactly once, before it runs — so the line\n * is said once however many scopes hold the folder, and by every command alike. It is a notice\n * and nothing more: the run goes on exactly as it would without the folder, which no command\n * reads or writes. On stderr, so a command whose output is piped somewhere is not changed by it.\n */\nfunction sayTheRetiredSourceFolderIsUnsupported(cwd: string): void {\n  const replacement = retiredSourceFolderIn([cwd, os.homedir()]);\n  if (replacement === null) return;\n  process.stderr.write(`${retiredSourceFolderUnsupported(replacement)}\\n`);\n}\n\n/**\n * Ends the run here, once the dashboard is done with it.\n *\n * `this.exit(0)` cannot: oclif swallows an exit 0 thrown from a hook and carries on with the run\n * the hook interrupted — and a run with no command is a request for the root help, so the full help\n * listing printed under every dashboard that was left with Escape or a chosen command. A non-zero\n * exit is not swallowed, which is why Ctrl+C's `this.error` already ended the run. This is the\n * ending oclif's own error handler gives a command's `this.exit()`, with the output flushed first.\n */\nasync function endRun(code: number): Promise<never> {\n  await flush();\n  process.exit(code);\n}\n\nexport default hook;\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,OAAO,QAAQ;AAEf,SAAS,aAAwB;AAUjC,IAAM,OAAqB,eAAgB,SAAS;AAClD,yCAAuC,QAAQ,IAAI,CAAC;AAGpD,MAAI,QAAQ,OAAO,QAAW;AAC5B,UAAM,aAAa,QAAQ,IAAI;AAG/B,UAAM,aAAa,MAAM,uBAAuB,UAAU;AAC1D,QAAI,WAAW,SAAS,GAAG;AACzB,WAAK,MAAM,8BAA8B,UAAU,GAAG,EAAE,MAAM,WAAW,MAAM,CAAC;AAAA,IAClF;AAEA,UAAM,YAAY,MAAM,iBAAiB,YAAY,QAAQ,MAAM;AACnE,QAAI,cAAc,YAAa,MAAK,MAAM,aAAa,EAAE,MAAM,WAAW,UAAU,CAAC;AACrF,QAAI,cAAc,QAAS,OAAM,OAAO,WAAW,OAAO;AAAA,EAC5D;AACF;AAUA,SAAS,uCAAuC,KAAmB;AACjE,QAAM,cAAc,sBAAsB,CAAC,KAAK,GAAG,QAAQ,CAAC,CAAC;AAC7D,MAAI,gBAAgB,KAAM;AAC1B,UAAQ,OAAO,MAAM,GAAG,+BAA+B,WAAW,CAAC;AAAA,CAAI;AACzE;AAWA,eAAe,OAAO,MAA8B;AAClD,QAAM,MAAM;AACZ,UAAQ,KAAK,IAAI;AACnB;AAEA,IAAO,eAAQ;","names":[]}
+{"version":3,"sources":["../../src/cli/hooks/init.ts"],"sourcesContent":["import os from \"os\";\n\nimport { flush, type Hook } from \"@oclif/core\";\nimport { runDashboardFlow } from \"../commands/init.js\";\nimport { findConfigLoadFailures } from \"../lib/configuration/project-config.js\";\nimport { retiredSourceFolderIn } from \"../lib/installation/install-layout.js\";\nimport { EXIT_CODES } from \"../lib/exit-codes.js\";\nimport {\n  installationConfigsUnreadable,\n  retiredSourceFolderUnsupported,\n} from \"../utils/messages.js\";\n\nconst hook: Hook<\"init\"> = async function (options) {\n  sayTheRetiredSourceFolderIsUnsupported(process.cwd());\n\n  // No command: the dashboard.\n  if (options.id === undefined) {\n    const projectDir = process.cwd();\n    // Checked here: oclif's hook runner swallows a load error thrown inside the dashboard.\n    const unreadable = await findConfigLoadFailures(projectDir);\n    if (unreadable.length > 0) {\n      this.error(installationConfigsUnreadable(unreadable), { exit: EXIT_CODES.ERROR });\n    }\n\n    const dashboard = await runDashboardFlow(projectDir, options.config);\n    if (dashboard === \"cancelled\") this.error(\"Cancelled\", { exit: EXIT_CODES.CANCELLED });\n    if (dashboard === \"shown\") await endRun(EXIT_CODES.SUCCESS);\n  }\n};\n\n/** Notice only, once per run; stderr so piped output is unchanged. */\nfunction sayTheRetiredSourceFolderIsUnsupported(cwd: string): void {\n  const replacement = retiredSourceFolderIn([cwd, os.homedir()]);\n  if (replacement === null) return;\n  process.stderr.write(`${retiredSourceFolderUnsupported(replacement)}\\n`);\n}\n\n/** Not `this.exit(0)`: oclif swallows an exit 0 from a hook and goes on to print the root help. */\nasync function endRun(code: number): Promise<never> {\n  await flush();\n  process.exit(code);\n}\n\nexport default hook;\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,OAAO,QAAQ;AAEf,SAAS,aAAwB;AAUjC,IAAM,OAAqB,eAAgB,SAAS;AAClD,yCAAuC,QAAQ,IAAI,CAAC;AAGpD,MAAI,QAAQ,OAAO,QAAW;AAC5B,UAAM,aAAa,QAAQ,IAAI;AAE/B,UAAM,aAAa,MAAM,uBAAuB,UAAU;AAC1D,QAAI,WAAW,SAAS,GAAG;AACzB,WAAK,MAAM,8BAA8B,UAAU,GAAG,EAAE,MAAM,WAAW,MAAM,CAAC;AAAA,IAClF;AAEA,UAAM,YAAY,MAAM,iBAAiB,YAAY,QAAQ,MAAM;AACnE,QAAI,cAAc,YAAa,MAAK,MAAM,aAAa,EAAE,MAAM,WAAW,UAAU,CAAC;AACrF,QAAI,cAAc,QAAS,OAAM,OAAO,WAAW,OAAO;AAAA,EAC5D;AACF;AAGA,SAAS,uCAAuC,KAAmB;AACjE,QAAM,cAAc,sBAAsB,CAAC,KAAK,GAAG,QAAQ,CAAC,CAAC;AAC7D,MAAI,gBAAgB,KAAM;AAC1B,UAAQ,OAAO,MAAM,GAAG,+BAA+B,WAAW,CAAC;AAAA,CAAI;AACzE;AAGA,eAAe,OAAO,MAA8B;AAClD,QAAM,MAAM;AACZ,UAAQ,KAAK,IAAI;AACnB;AAEA,IAAO,eAAQ;","names":[]}

package/dist/index.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../src/cli/index.ts"],"sourcesContent":["import { run, flush, Errors } from \"@oclif/core\";\n\nrun(undefined, import.meta.url)\n  .then(() => flush())\n  // oclif's handler takes an `Error`, and a rejection reason is `unknown` — a\n  // throw of a non-Error would otherwise reach it and fail inside the handler,\n  // losing the message it was carrying.\n  .catch((error: unknown) =>\n    Errors.handle(error instanceof Error ? error : new Error(String(error))),\n  );\n"],"mappings":";;;AAAA,SAAS,KAAK,OAAO,cAAc;AAEnC,IAAI,QAAW,YAAY,GAAG,EAC3B,KAAK,MAAM,MAAM,CAAC,EAIlB;AAAA,EAAM,CAAC,UACN,OAAO,OAAO,iBAAiB,QAAQ,QAAQ,IAAI,MAAM,OAAO,KAAK,CAAC,CAAC;AACzE;","names":[]}
+{"version":3,"sources":["../src/cli/index.ts"],"sourcesContent":["import { run, flush, Errors } from \"@oclif/core\";\n\nrun(undefined, import.meta.url)\n  .then(() => flush())\n  // Errors.handle needs an Error; a non-Error rejection would fail inside it.\n  .catch((error: unknown) =>\n    Errors.handle(error instanceof Error ? error : new Error(String(error))),\n  );\n"],"mappings":";;;AAAA,SAAS,KAAK,OAAO,cAAc;AAEnC,IAAI,QAAW,YAAY,GAAG,EAC3B,KAAK,MAAM,MAAM,CAAC,EAElB;AAAA,EAAM,CAAC,UACN,OAAO,OAAO,iBAAiB,QAAQ,QAAQ,IAAI,MAAM,OAAO,KAAK,CAAC,CAAC;AACzE;","names":[]}

package/dist/load-agent-defs-6QUUMGHK.js

@@ -0,0 +1,14 @@
+#!/usr/bin/env node
+import {
+  loadAgentDefs
+} from "./chunk-THO7LO5B.js";
+import "./chunk-5BNX73OU.js";
+import "./chunk-2YA4DDRM.js";
+import "./chunk-GAKVZNTX.js";
+import "./chunk-AUNRHWH4.js";
+import "./chunk-7C3PFRBU.js";
+import "./chunk-GHHJYNAN.js";
+export {
+  loadAgentDefs
+};
+//# sourceMappingURL=load-agent-defs-6QUUMGHK.js.map

package/dist/recompile-project-agents-I33KQJFB.js

@@ -0,0 +1,65 @@
+#!/usr/bin/env node
+import {
+  compileAgents,
+  discoverInstalledSkills,
+  withCatalogueSeatedFor
+} from "./chunk-IWY5IR4F.js";
+import {
+  loadAgentDefs
+} from "./chunk-THO7LO5B.js";
+import "./chunk-5BNX73OU.js";
+import "./chunk-2YA4DDRM.js";
+import {
+  getErrorMessage,
+  resolveInstallPaths
+} from "./chunk-GAKVZNTX.js";
+import "./chunk-AUNRHWH4.js";
+import "./chunk-7C3PFRBU.js";
+import "./chunk-GHHJYNAN.js";
+
+// src/cli/lib/operations/project/recompile-project-agents.ts
+async function recompileRegisteredProjectAgents(projectDir) {
+  return withCatalogueSeatedFor(projectDir, async () => {
+    const { allSkills } = await discoverInstalledSkills(projectDir);
+    const { sourcePath } = await loadAgentDefs();
+    return compileAgents({
+      projectDir,
+      sourcePath,
+      skills: allSkills,
+      scopeFilter: "project",
+      outputDir: resolveInstallPaths(projectDir, "project").agentsDir
+    });
+  });
+}
+async function recompilePropagatedProjectAgents(projectDirs, pairsRewritten) {
+  const outcomes = [];
+  for (const dir of projectDirs) {
+    outcomes.push(await recompileOutcomeFor(dir, pairsRewritten));
+  }
+  return summarizeRecompiles(outcomes);
+}
+async function recompileOutcomeFor(dir, pairsRewritten) {
+  try {
+    const result = await recompileRegisteredProjectAgents(dir);
+    if (result.failed.length > 0) return { kind: "failed", warnings: result.warnings };
+    const changed = result.rewritten.length > 0 || pairsRewritten.has(dir);
+    return { kind: changed ? "rewritten" : "unchanged" };
+  } catch (error) {
+    return {
+      kind: "failed",
+      warnings: [`Could not recompile agents in ${dir}: ${getErrorMessage(error)}`]
+    };
+  }
+}
+function summarizeRecompiles(outcomes) {
+  return {
+    rewrittenCount: outcomes.filter((outcome) => outcome.kind === "rewritten").length,
+    unchangedCount: outcomes.filter((outcome) => outcome.kind === "unchanged").length,
+    failedCount: outcomes.filter((outcome) => outcome.kind === "failed").length,
+    warnings: outcomes.flatMap((outcome) => outcome.kind === "failed" ? outcome.warnings : [])
+  };
+}
+export {
+  recompilePropagatedProjectAgents
+};
+//# sourceMappingURL=recompile-project-agents-I33KQJFB.js.map

package/dist/recompile-project-agents-I33KQJFB.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/cli/lib/operations/project/recompile-project-agents.ts"],"sourcesContent":["import { compileAgents, type CompilationResult } from \"./compile-agents.js\";\nimport { loadAgentDefs } from \"./load-agent-defs.js\";\nimport { discoverInstalledSkills } from \"../skills/index.js\";\nimport { resolveInstallPaths } from \"../../installation/index.js\";\nimport { withCatalogueSeatedFor } from \"../../loading/catalogue-seat.js\";\nimport { getErrorMessage } from \"../../../utils/errors.js\";\n\n/**\n * Project scope only: the triggering command already recompiled the global agents. Skills and\n * catalogue are resolved from this project; without explicit `skills`, `recompileAgents` would\n * see plugin skills only.\n */\nasync function recompileRegisteredProjectAgents(projectDir: string): Promise<CompilationResult> {\n  return withCatalogueSeatedFor(projectDir, async () => {\n    const { allSkills } = await discoverInstalledSkills(projectDir);\n    const { sourcePath } = await loadAgentDefs();\n\n    return compileAgents({\n      projectDir,\n      sourcePath,\n      skills: allSkills,\n      scopeFilter: \"project\",\n      outputDir: resolveInstallPaths(projectDir, \"project\").agentsDir,\n    });\n  });\n}\n\nexport type PropagatedRecompileSummary = {\n  /** Projects whose config pair or compiled sub-agents changed. */\n  rewrittenCount: number;\n  /** Projects visited where neither did. */\n  unchangedCount: number;\n  failedCount: number;\n  warnings: string[];\n};\n\n/**\n * One project's failure must not stop the rest; sequential so warnings keep a stable order.\n * `pairsRewritten` names the projects whose config pair the fan-out changed.\n */\nexport async function recompilePropagatedProjectAgents(\n  projectDirs: string[],\n  pairsRewritten: ReadonlySet<string>,\n): Promise<PropagatedRecompileSummary> {\n  const outcomes: ProjectRecompileOutcome[] = [];\n  for (const dir of projectDirs) {\n    outcomes.push(await recompileOutcomeFor(dir, pairsRewritten));\n  }\n  return summarizeRecompiles(outcomes);\n}\n\ntype ProjectRecompileOutcome =\n  { kind: \"rewritten\" } | { kind: \"unchanged\" } | { kind: \"failed\"; warnings: string[] };\n\nasync function recompileOutcomeFor(\n  dir: string,\n  pairsRewritten: ReadonlySet<string>,\n): Promise<ProjectRecompileOutcome> {\n  try {\n    const result = await recompileRegisteredProjectAgents(dir);\n    if (result.failed.length > 0) return { kind: \"failed\", warnings: result.warnings };\n\n    const changed = result.rewritten.length > 0 || pairsRewritten.has(dir);\n    return { kind: changed ? \"rewritten\" : \"unchanged\" };\n  } catch (error) {\n    return {\n      kind: \"failed\",\n      warnings: [`Could not recompile agents in ${dir}: ${getErrorMessage(error)}`],\n    };\n  }\n}\n\nfunction summarizeRecompiles(outcomes: ProjectRecompileOutcome[]): PropagatedRecompileSummary {\n  return {\n    rewrittenCount: outcomes.filter((outcome) => outcome.kind === \"rewritten\").length,\n    unchangedCount: outcomes.filter((outcome) => outcome.kind === \"unchanged\").length,\n    failedCount: outcomes.filter((outcome) => outcome.kind === \"failed\").length,\n    warnings: outcomes.flatMap((outcome) => (outcome.kind === \"failed\" ? outcome.warnings : [])),\n  };\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;AAYA,eAAe,iCAAiC,YAAgD;AAC9F,SAAO,uBAAuB,YAAY,YAAY;AACpD,UAAM,EAAE,UAAU,IAAI,MAAM,wBAAwB,UAAU;AAC9D,UAAM,EAAE,WAAW,IAAI,MAAM,cAAc;AAE3C,WAAO,cAAc;AAAA,MACnB;AAAA,MACA;AAAA,MACA,QAAQ;AAAA,MACR,aAAa;AAAA,MACb,WAAW,oBAAoB,YAAY,SAAS,EAAE;AAAA,IACxD,CAAC;AAAA,EACH,CAAC;AACH;AAeA,eAAsB,iCACpB,aACA,gBACqC;AACrC,QAAM,WAAsC,CAAC;AAC7C,aAAW,OAAO,aAAa;AAC7B,aAAS,KAAK,MAAM,oBAAoB,KAAK,cAAc,CAAC;AAAA,EAC9D;AACA,SAAO,oBAAoB,QAAQ;AACrC;AAKA,eAAe,oBACb,KACA,gBACkC;AAClC,MAAI;AACF,UAAM,SAAS,MAAM,iCAAiC,GAAG;AACzD,QAAI,OAAO,OAAO,SAAS,EAAG,QAAO,EAAE,MAAM,UAAU,UAAU,OAAO,SAAS;AAEjF,UAAM,UAAU,OAAO,UAAU,SAAS,KAAK,eAAe,IAAI,GAAG;AACrE,WAAO,EAAE,MAAM,UAAU,cAAc,YAAY;AAAA,EACrD,SAAS,OAAO;AACd,WAAO;AAAA,MACL,MAAM;AAAA,MACN,UAAU,CAAC,iCAAiC,GAAG,KAAK,gBAAgB,KAAK,CAAC,EAAE;AAAA,IAC9E;AAAA,EACF;AACF;AAEA,SAAS,oBAAoB,UAAiE;AAC5F,SAAO;AAAA,IACL,gBAAgB,SAAS,OAAO,CAAC,YAAY,QAAQ,SAAS,WAAW,EAAE;AAAA,IAC3E,gBAAgB,SAAS,OAAO,CAAC,YAAY,QAAQ,SAAS,WAAW,EAAE;AAAA,IAC3E,aAAa,SAAS,OAAO,CAAC,YAAY,QAAQ,SAAS,QAAQ,EAAE;AAAA,IACrE,UAAU,SAAS,QAAQ,CAAC,YAAa,QAAQ,SAAS,WAAW,QAAQ,WAAW,CAAC,CAAE;AAAA,EAC7F;AACF;","names":[]}

package/dist/{source-loader-C5SQXZXI.js → source-loader-TTJVW2ER.js}

@@ -5,10 +5,10 @@ import {
   loadMarketplaceMatrix,
   loadSkillsMatrixFromSource,
   mergeLocalSkillsIntoMatrix
-} from "./chunk-MQ6CGZNJ.js";
-import "./chunk-52HDHJ7I.js";
-import "./chunk-PJWGTNOX.js";
-import "./chunk-NQW25DCF.js";
+} from "./chunk-GAKVZNTX.js";
+import "./chunk-AUNRHWH4.js";
+import "./chunk-7C3PFRBU.js";
+import "./chunk-GHHJYNAN.js";
 export {
   MarketplaceManifestRequiredError,
   convertStackToResolvedStack,
@@ -16,4 +16,4 @@ export {
   loadSkillsMatrixFromSource,
   mergeLocalSkillsIntoMatrix
 };
-//# sourceMappingURL=source-loader-C5SQXZXI.js.map
+//# sourceMappingURL=source-loader-TTJVW2ER.js.map

package/dist/src/agents/developer/ai-developer/playbook.md

@@ -59,11 +59,8 @@ spec names. Before calling the step done, check the pipeline against this list:
 then the tests `ai-tester` wrote for this feature. Mock the model API rather than calling it — a test
 that hits a live model is non-deterministic and costs money per run. Cover malformed output: empty,
 truncated, and valid JSON of the wrong shape. Cover the token-limit boundary and the retry path with
-simulated failures. Run the project's linter, and put a real request through the pipeline where a
-mocked test cannot tell you whether the prompt actually works.
-
-**Your stop hook runs the project's typecheck and nothing else.** Lint and tests are
-deliberately outside it, so a clean stop says the code compiles — never that it works.
+simulated failures. Run the project's typecheck and linter, and put a real request through the
+pipeline where a mocked test cannot tell you whether the prompt actually works.
 
 **Step 5 — Verify.** Take the success criteria one at a time: state the criterion, mark it PASS or
 FAIL, and give the evidence — the test name, the command, or what you observed. Fix and re-verify

package/dist/src/agents/developer/api-developer/playbook.md

@@ -54,11 +54,8 @@ spec names. Before calling the step done, check the endpoint against this list:
 
 **Step 4 — Test, lint, and call it.** Run the existing tests to confirm nothing broke, then the
 tests `api-tester` wrote for this feature. A test that passes without exercising the requirement
-covers nothing, so check what each one actually asserts. Run the project's linter, and send a real
-request to the endpoint where a test cannot reach what a caller would get.
-
-**Your stop hook runs the project's typecheck and nothing else.** Lint and tests are
-deliberately outside it, so a clean stop says the code compiles — never that it works.
+covers nothing, so check what each one actually asserts. Run the project's typecheck and linter, and
+send a real request to the endpoint where a test cannot reach what a caller would get.
 
 **Step 5 — Verify.** Take the success criteria one at a time: state the criterion, mark it PASS or
 FAIL, and give the evidence — the test name, the request you made, or what you observed. Fix and

package/dist/src/agents/developer/cli-developer/playbook.md

@@ -55,11 +55,8 @@ spec names. Before calling the step done, check the command against this list:
 
 **Step 4 — Test, lint, and run the command.** Run the existing tests to confirm nothing broke,
 then the tests `cli-tester` wrote for this feature, and check that the cancellation paths are among
-them. Run the project's linter, and drive the command yourself — including Ctrl+C — where a test
-cannot reach what a user would see.
-
-**Your stop hook runs the project's typecheck and nothing else.** Lint and tests are
-deliberately outside it, so a clean stop says the code compiles — never that it works.
+them. Run the project's typecheck and linter, and drive the command yourself — including Ctrl+C —
+where a test cannot reach what a user would see.
 
 **Step 5 — Verify.** Take the success criteria one at a time: state the criterion, mark it PASS or
 FAIL, and give the evidence — the test name, the command, or what you observed. Fix and re-verify

package/dist/src/agents/developer/web-developer/playbook.md

@@ -45,11 +45,8 @@ spec names.
 
 **Step 4 — Test, lint, and see it run.** Run the existing tests to confirm nothing broke, then the
 tests `web-tester` wrote for this feature. A test that passes without exercising the requirement
-covers nothing, so check what each one actually asserts. Run the project's linter, and exercise the
-feature yourself where a test cannot reach what a user would see.
-
-**Your stop hook runs the project's typecheck and nothing else.** Lint and tests are
-deliberately outside it, so a clean stop says the code compiles — never that it works.
+covers nothing, so check what each one actually asserts. Run the project's typecheck and linter, and
+exercise the feature yourself where a test cannot reach what a user would see.
 
 **Step 5 — Verify.** Take the success criteria one at a time: state the criterion, mark it PASS or
 FAIL, and give the evidence — the test name, the command, or what you observed. Fix and re-verify

package/dist/src/agents/meta/agent-summoner/output.md

@@ -13,8 +13,8 @@ Report the directory, then each file's content, then the config entry, then the
 `tools` are required; every other key is optional, whatever its position in the file. Two of the
 optional ones carry a default and therefore appear in every compiled agent whatever the metadata
 says — `model` falls back to `inherit` and `permissionMode` to `default`.
-`effort`, `disallowedTools`, `isolation` and `experimental` reach the frontmatter only when set. `hooks` reaches it either from `metadata.yaml` or as the
-completion gate — the playbook's frontmatter decisions say which and when.
+`effort`, `disallowedTools`, `isolation`, `experimental` and `hooks` reach the frontmatter only
+when set.
 
 ```yaml
 # yaml-language-server: $schema=https://raw.githubusercontent.com/agents-inc/agents-inc/main/packages/cli/src/schemas/agent.schema.json

package/dist/src/agents/meta/agent-summoner/playbook.md

@@ -103,7 +103,7 @@ follows: `<domain_scope>` in `identity.md`, `<self_correction_triggers>` in
 The compiled file, in order:
 
 ```
-frontmatter                metadata.yaml, plus the Skill grant and the completion gate
+frontmatter                metadata.yaml, plus the Skill grant
 provenance marker          an HTML comment the compile step stamps
 # Title                    the title from metadata.yaml
 <role>                     identity.md
@@ -226,18 +226,6 @@ because this repository does not use worktrees. Leave it off unless the project
 for has asked for it — a researcher in particular wants the working tree itself, since the tree is
 what the question is about.
 
-**The completion gate arrives on its own.** Every agent holding `Write` or `Edit` gets a `Stop`
-hook — logged by Claude Code as `SubagentStop` — that runs the project's typecheck
-before the agent may stop; a failing
-check comes back as the compiler's own output, so the agent iterates on it instead of reporting
-done, and the hook exits quietly in a project that declares no such scripts. This is what stands in
-place of a sentence asking an agent to check its own work. Declaring `hooks:` in `metadata.yaml` merges
-with the gate rather than displacing it: a stop hook of your own — `Stop` or `SubagentStop`, which
-Claude Code treats as one event for a sub-agent — replaces the emitted gate, and every other event is
-added beside it. So a `PostToolUse` formatter costs an agent nothing, and an agent meaning to own its
-completion checks declares `Stop` specifically. It has to declare an actual hook to do so:
-`declaresOwnGate` tests for a non-empty array, so `Stop: []` states nothing and the gate stands.
-
 </frontmatter_decisions>
 
 ---

package/dist/src/agents/meta/codex-keeper/critical-requirements.md

@@ -3,11 +3,8 @@ document is a claim about source, and agents act on it without checking. Glob an
 claim about what a file contains comes from reading it.
 
 **Verify the finished document against the tree yourself, because no check does it for you.**
-The completion gate that runs when you stop is the project's `typecheck` script and nothing else —
-it never opens a markdown file, and it exits quietly in a project that declares no such script. A
-reference document whose every path has rotted stops the agent green. Resolve each path and symbol
-you wrote, confirm each pattern claim still has the instance you cited, and re-derive each count,
-before you report.
+Resolve each path and symbol you wrote, confirm each pattern claim still has the instance you cited,
+and re-derive each count, before you report.
 
 **Cite a path and a symbol, never a line number.** A symbol survives every edit above it and is
 greppable; a line number rots on the next unrelated insertion, silently, while still reading as

package/dist/src/agents/meta/convention-keeper/critical-requirements.md

@@ -12,10 +12,8 @@ proposal that describes a change leaves the wording to whoever applies it, and t
 approved rule turns into a different one.
 
 **Confirm the target file and section exist before you propose an edit, and read the rule back in
-place after you apply one.** No check does this for you: the completion gate that runs when you stop
-is the project's `typecheck` script and nothing else — it never opens a markdown file, and it exits
-quietly in a project that declares no such script. A rule that read correctly in the proposal can
-contradict the one above it once it lands, and a proposal naming a section that no longer exists
+place after you apply one.** No check does this for you. A rule that read correctly in the proposal
+can contradict the one above it once it lands, and a proposal naming a section that no longer exists
 cannot be applied at all.
 
 **Mark a processed finding resolved in its own file, at its own path** — `status: resolved` plus a

package/dist/src/agents/tester/ai-tester/critical-requirements.md

@@ -34,8 +34,7 @@ pass threshold.** An eval in the blocking suite fails for reasons no one can rep
 **Watch each test fail for the right reason before the implementation exists, then pass after it.**
 A test that has never failed has not been shown to test anything.
 
-**Run the suite and report its actual output before claiming completion.** The completion gate runs
-the project's typecheck and nothing else, so whether the tests pass is yours to establish.
+**Run the suite and report its actual output before claiming completion.**
 
 <self_correction_triggers>
 

package/dist/src/agents/tester/ai-tester/playbook.md

@@ -144,6 +144,8 @@ the code does rather than what the feature owes.
 2. Run with a randomized test order if the runner supports it
 3. Confirm no test leaks timers, streams, or unclosed handles
 4. Confirm the eval suite is excluded from the default run
+5. Run the project's typecheck once the implementation exists, and fix every error it reports in a
+   test file — a runner that strips types runs a test file the compiler rejects
 
 **ITERATE: Fix causes, not symptoms**
 1. Flaky test? Find the nondeterminism (clock, ordering, shared fixture, live call) and remove it

package/dist/src/agents/tester/api-tester/critical-requirements.md

@@ -24,8 +24,7 @@ somewhere else entirely, which is where the debugging time goes.
 data-integrity bugs — a handler that returns 201 and persists nothing passes an
 HTTP-only assertion.
 
-**Run the suite and report its actual output before claiming completion.** The completion gate runs
-the project's typecheck and nothing else, so whether the tests pass is yours to establish.
+**Run the suite and report its actual output before claiming completion.**
 
 **Record a finding the way this project's conventions direct** when you fix an anti-pattern or
 discover a missing standard, so the next agent inherits it rather than rediscovering it.

package/dist/src/agents/tester/api-tester/playbook.md

@@ -63,6 +63,8 @@ nothing to do with the endpoint under test.
 2. Verify tests fail for expected reasons (not setup errors)
 3. Check tests pass after implementation exists
 4. Confirm database cleanup prevents test pollution
+5. Run the project's typecheck once the implementation exists, and fix every error it reports in a
+   test file — a runner that strips types runs a test file the compiler rejects
 
 **ITERATE: Fix and Improve**
 1. If tests are flaky, check for shared database state

package/dist/src/agents/tester/cli-tester/critical-requirements.md

@@ -26,8 +26,7 @@ removed rather than deprecated.
 A test that passes immediately has not been shown to test anything.
 
 **Run the suite with the project's own test command — the `test` script in its `package.json` — and
-report the actual output before claiming completion.** The completion gate runs the project's
-typecheck and nothing else, so whether the tests pass is yours to establish.
+report the actual output before claiming completion.**
 
 <self_correction_triggers>
 

package/dist/src/agents/tester/cli-tester/playbook.md

@@ -60,6 +60,8 @@ file for a reason none of them names.
 2. Verify tests fail for expected reasons (not syntax errors)
 3. Check tests pass after implementation exists
 4. Confirm cleanup prevents memory leaks
+5. Run the project's typecheck once the implementation exists, and fix every error it reports in a
+   test file — a runner that strips types runs a test file the compiler rejects
 
 **ITERATE: Fix and Improve**
 1. If tests are flaky, find what they race — an unfired effect, a missing unmount, a shared store —

package/dist/src/agents/tester/web-tester/critical-requirements.md

@@ -17,8 +17,7 @@ drifts from it.
 **Mock the boundaries — APIs, databases, external services — so no test reaches a real one.** A
 suite that talks to a live service fails for reasons that have nothing to do with the code.
 
-**Run the suite and report its actual output before claiming completion.** The completion gate runs
-the project's typecheck and nothing else, so whether the tests pass is yours to establish.
+**Run the suite and report its actual output before claiming completion.**
 
 <self_correction_triggers>
 

package/dist/src/agents/tester/web-tester/playbook.md

@@ -54,6 +54,8 @@ result.
 1. web-developer cleans up the implementation without changing behavior
 2. Re-run the suite - it must still pass, unedited
 3. A test that reddens on a behavior-preserving refactor was testing implementation; fix that test
+4. Run the project's typecheck, and fix every error it reports in a test file - a runner that strips
+   types runs a test file the compiler rejects
 
 **Hand Off to Developer:**
 - Provide complete test file

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "agents-inc",
-  "version": "0.170.1",
+  "version": "0.170.2",
   "description": "CLI for managing Agents Inc. skills, stacks, and agents for Claude Code",
-  "//generate": "The write path for all four generators, in dependency order: generate:types reads the skills marketplace and writes src/cli/types/generated/, then generate:schemas copies SKILL_SLUGS and CATEGORIES out of it into metadata.schema.json's enums, then generate:matrix vendors the same directory into packages/matrix, then generate:compile vendors this package's own src/agents/ partials and templates into packages/compile. A marketplace change drifts the first three, and .github/workflows/regenerate-catalog.yml runs those three step by step; generate:compile is not on that chain, because an agent-partial edit drifts it and a marketplace change does not. It replaces the write path only: the :check variants stay separate because CI deliberately runs different subsets of them in different jobs.",
-  "//no-shared-vitest-config": "A three-project suite — unit, integration and commands, each with its own include and the retry that separates them — behind one root config that also carries vitest.setup.ts, disableConsoleIntercept for @oclif/test and ink-testing-library, and its own timeouts. @workspace/vitest-config is a single-project node config that turns globals off, which this suite needs on, so merging it in would contradict as much as it contributed. e2e/vitest.config.ts stands under the same decision. Read by scripts/check-shared-vitest-config.ts in packages/cli.",
-  "//test:smoke": "The second half of e2e/vitest.config.ts, which is now two named projects over one tree: `test:e2e` runs `*.e2e.test.ts` and this runs `*.smoke.test.ts`. Before this pair existed no command ran the smoke files at all — the old single `include` excluded them, vitest has no `--include` flag, and reaching them took a hand-written config nobody had. They sat outside every gate for months and rotted exactly as you would expect: a marketplace fixture the Claude CLI has always rejected sat under a spec named 'should add a marketplace from a local directory source' that had never once added one. It DOES run in CI, and deliberately, and what it proves there now has TWO halves that must not be conflated. The Claude probes are `describe.skipIf(!claudeAvailable)` and the runner has no `claude`, so nothing they assert is coverage of the Claude CLI and must not be reported as such — for that, run them on a machine that has the binary. What a skipped run still proves is that the files collect, import and resolve their helpers, which is the whole of what rotted. The Codex probe does NOT skip: `e2e/smoke/codex-lane.smoke.test.ts` runs the pinned @openai/codex devDependency for real on every runner, so its assertions are coverage. `grep -L 'describe.skipIf' e2e/smoke/*.smoke.test.ts` is which files are which — a bare `skipIf` does not separate them, because codex-lane's docblock says in prose that it carries none.",
+  "//generate": "Runs all four generators in dependency order; the :check variants stay separate because CI runs different subsets.",
+  "//no-shared-vitest-config": "A three-project suite with globals on and its own setup and timeouts; the shared single-project, globals-off config would contradict it.",
+  "//test:smoke": "Runs e2e *.smoke.test.ts; the Claude probes skip without the binary, the Codex probe runs for real.",
   "type": "module",
   "main": "dist/index.js",
   "exports": {
@@ -44,7 +44,7 @@
     "prompt-engineering",
     "ai-tools"
   ],
-  "//sideEffects": "compile-seat.ts is imported bare to seat @workspace/compile's warnings; with plain false, esbuild drops that import and every warning the compile package raises goes nowhere.",
+  "//sideEffects": "compile-seat.ts is imported bare for its side effect, which plain false would let esbuild drop.",
   "sideEffects": [
     "./src/cli/lib/compile-seat.ts"
   ],
@@ -76,7 +76,7 @@
     "dev": "tsup --watch",
     "agentsinc": "node dist/index.js",
     "agentsinc:dev": "bun src/cli/index.ts",
-    "//test": "No `pretest` hook, deliberately, and removing it fixed a real defect. turbo.json already orders `build` before `test` and `test:e2e` via dependsOn, so an npm pre-hook is a SECOND build — and turbo runs those tasks concurrently, so `turbo run test test:e2e` fired three tsup builds and two of them raced on one dist/. tsup builds with clean:true, so the loser died with `ENOENT ... unlink dist/chunk-*.js` out of pretest:e2e; measured 2026-08-23 at 3 tsup invocations per invocation, now 1. That race aborted a push with no legible error, four hundred lines up in interleaved output. Running vitest directly is unaffected and stays a refusal rather than a rebuild: assertDistIsFresh in src/cli/lib/testing/dist-staleness.ts names a stale or absent dist and says to run `bun run build` — which is the posture that file argues for, since a direct `vitest run` should stay fast and stay something you asked for. A SECOND thing the two suites share, and it is not the dist/ one: each keeps a fixture at a FIXED os.tmpdir() path — the E2E source tree, and the unit suite's checkout of the default marketplace — because globalSetup runs in vitest's own process while the specs run in forked workers, so neither side can be handed the location and both compute it. A fixed path belongs to the machine and not to the run, so the rule it costs is that a fixture is written by the runner that owns it and by nothing else. shared-source.test.ts broke that for months: collected by the `unit` project, it rebuilt and removed the E2E fixture on the real path in six specs and an afterEach, and both suites stayed green while it deleted the tree the E2E specs read. src/cli/lib/__tests__/shared-fixture-writers.test.ts holds the rule against a walk of the tree, and src/cli/lib/__tests__/helpers/shared-source.ts states it in full.",
+    "//test": "No pretest hook: turbo already builds before test, and a second build races tsup on dist/.",
     "test": "vitest run",
     "test:e2e": "vitest --config e2e/vitest.config.ts --run --project e2e",
     "test:smoke": "vitest --config e2e/vitest.config.ts --run --project smoke",
@@ -122,7 +122,6 @@
     "fast-glob": "^3.3.0",
     "fs-extra": "^11.2.0",
     "giget": "^1.2.0",
-    "gray-matter": "^4.0.3",
     "ink": "^7",
     "jiti": "2.4.2",
     "liquidjs": "^10.24.0",
@@ -131,7 +130,7 @@
     "yaml": "^2.9.0",
     "zod": "^4.4.3"
   },
-  "//devDependencies": "@workspace/matrix, @workspace/compile and @workspace/api are private and never installed by a consumer, so all three are devDependencies and tsup bundles them (see `noExternal`). matrix is the one home of the seed wire contract, which src/cli/lib/seed/ used to hand-vendor; compile is the one home of the config-pair and compiled-agent renderers, which the editor's output preview draws with; api is the one home of the typed client both front doors reach the worker through, which src/cli/lib/seed/fetch-seed.ts used to hand-write a fetch for. api pulls `hono/client` in with it, and `hono` is deliberately NOT a dependency here: tsup externalises exactly what `dependencies` names, so leaving it out is what inlines it into the bundle rather than adding a runtime install to a CLI that makes one GET. The cost of that was measured before it was accepted — `find dist -name '*.js' -not -name '*.map' | xargs du -cb | tail -1` is the number. @workspace/api-mocks and msw are a different case and are named in neither `noExternal` nor this rule: nothing under src/cli/ imports them, so they reach no bundle at all — they are the one description of the worker this suite's network mocks are resolved from, and the editor's suites read the same one.",
+  "//devDependencies": "The private @workspace packages are devDependencies so tsup bundles them (see noExternal); hono is omitted from dependencies so it is inlined too.",
   "devDependencies": {
     "@eslint/js": "^10",
     "@lydell/node-pty": "^1.2.0-beta.3",
@@ -148,6 +147,8 @@
     "@workspace/matrix": "workspace:*",
     "@workspace/typescript-config": "workspace:*",
     "@xterm/headless": "^6.0.0",
+    "ansis": "^3.17.0",
+    "esbuild": "^0.28.1",
     "eslint": "^10",
     "eslint-config-prettier": "^10",
     "eslint-plugin-react-hooks": "^7.1.1",

package/src/agents/developer/ai-developer/playbook.md

@@ -59,11 +59,8 @@ spec names. Before calling the step done, check the pipeline against this list:
 then the tests `ai-tester` wrote for this feature. Mock the model API rather than calling it — a test
 that hits a live model is non-deterministic and costs money per run. Cover malformed output: empty,
 truncated, and valid JSON of the wrong shape. Cover the token-limit boundary and the retry path with
-simulated failures. Run the project's linter, and put a real request through the pipeline where a
-mocked test cannot tell you whether the prompt actually works.
-
-**Your stop hook runs the project's typecheck and nothing else.** Lint and tests are
-deliberately outside it, so a clean stop says the code compiles — never that it works.
+simulated failures. Run the project's typecheck and linter, and put a real request through the
+pipeline where a mocked test cannot tell you whether the prompt actually works.
 
 **Step 5 — Verify.** Take the success criteria one at a time: state the criterion, mark it PASS or
 FAIL, and give the evidence — the test name, the command, or what you observed. Fix and re-verify

package/src/agents/developer/api-developer/playbook.md

@@ -54,11 +54,8 @@ spec names. Before calling the step done, check the endpoint against this list:
 
 **Step 4 — Test, lint, and call it.** Run the existing tests to confirm nothing broke, then the
 tests `api-tester` wrote for this feature. A test that passes without exercising the requirement
-covers nothing, so check what each one actually asserts. Run the project's linter, and send a real
-request to the endpoint where a test cannot reach what a caller would get.
-
-**Your stop hook runs the project's typecheck and nothing else.** Lint and tests are
-deliberately outside it, so a clean stop says the code compiles — never that it works.
+covers nothing, so check what each one actually asserts. Run the project's typecheck and linter, and
+send a real request to the endpoint where a test cannot reach what a caller would get.
 
 **Step 5 — Verify.** Take the success criteria one at a time: state the criterion, mark it PASS or
 FAIL, and give the evidence — the test name, the request you made, or what you observed. Fix and

package/src/agents/developer/cli-developer/playbook.md

@@ -55,11 +55,8 @@ spec names. Before calling the step done, check the command against this list:
 
 **Step 4 — Test, lint, and run the command.** Run the existing tests to confirm nothing broke,
 then the tests `cli-tester` wrote for this feature, and check that the cancellation paths are among
-them. Run the project's linter, and drive the command yourself — including Ctrl+C — where a test
-cannot reach what a user would see.
-
-**Your stop hook runs the project's typecheck and nothing else.** Lint and tests are
-deliberately outside it, so a clean stop says the code compiles — never that it works.
+them. Run the project's typecheck and linter, and drive the command yourself — including Ctrl+C —
+where a test cannot reach what a user would see.
 
 **Step 5 — Verify.** Take the success criteria one at a time: state the criterion, mark it PASS or
 FAIL, and give the evidence — the test name, the command, or what you observed. Fix and re-verify

package/src/agents/developer/web-developer/playbook.md

@@ -45,11 +45,8 @@ spec names.
 
 **Step 4 — Test, lint, and see it run.** Run the existing tests to confirm nothing broke, then the
 tests `web-tester` wrote for this feature. A test that passes without exercising the requirement
-covers nothing, so check what each one actually asserts. Run the project's linter, and exercise the
-feature yourself where a test cannot reach what a user would see.
-
-**Your stop hook runs the project's typecheck and nothing else.** Lint and tests are
-deliberately outside it, so a clean stop says the code compiles — never that it works.
+covers nothing, so check what each one actually asserts. Run the project's typecheck and linter, and
+exercise the feature yourself where a test cannot reach what a user would see.
 
 **Step 5 — Verify.** Take the success criteria one at a time: state the criterion, mark it PASS or
 FAIL, and give the evidence — the test name, the command, or what you observed. Fix and re-verify

package/src/agents/meta/agent-summoner/output.md

@@ -13,8 +13,8 @@ Report the directory, then each file's content, then the config entry, then the
 `tools` are required; every other key is optional, whatever its position in the file. Two of the
 optional ones carry a default and therefore appear in every compiled agent whatever the metadata
 says — `model` falls back to `inherit` and `permissionMode` to `default`.
-`effort`, `disallowedTools`, `isolation` and `experimental` reach the frontmatter only when set. `hooks` reaches it either from `metadata.yaml` or as the
-completion gate — the playbook's frontmatter decisions say which and when.
+`effort`, `disallowedTools`, `isolation`, `experimental` and `hooks` reach the frontmatter only
+when set.
 
 ```yaml
 # yaml-language-server: $schema=https://raw.githubusercontent.com/agents-inc/agents-inc/main/packages/cli/src/schemas/agent.schema.json

package/src/agents/meta/agent-summoner/playbook.md

@@ -103,7 +103,7 @@ follows: `<domain_scope>` in `identity.md`, `<self_correction_triggers>` in
 The compiled file, in order:
 
 ```
-frontmatter                metadata.yaml, plus the Skill grant and the completion gate
+frontmatter                metadata.yaml, plus the Skill grant
 provenance marker          an HTML comment the compile step stamps
 # Title                    the title from metadata.yaml
 <role>                     identity.md
@@ -226,18 +226,6 @@ because this repository does not use worktrees. Leave it off unless the project
 for has asked for it — a researcher in particular wants the working tree itself, since the tree is
 what the question is about.
 
-**The completion gate arrives on its own.** Every agent holding `Write` or `Edit` gets a `Stop`
-hook — logged by Claude Code as `SubagentStop` — that runs the project's typecheck
-before the agent may stop; a failing
-check comes back as the compiler's own output, so the agent iterates on it instead of reporting
-done, and the hook exits quietly in a project that declares no such scripts. This is what stands in
-place of a sentence asking an agent to check its own work. Declaring `hooks:` in `metadata.yaml` merges
-with the gate rather than displacing it: a stop hook of your own — `Stop` or `SubagentStop`, which
-Claude Code treats as one event for a sub-agent — replaces the emitted gate, and every other event is
-added beside it. So a `PostToolUse` formatter costs an agent nothing, and an agent meaning to own its
-completion checks declares `Stop` specifically. It has to declare an actual hook to do so:
-`declaresOwnGate` tests for a non-empty array, so `Stop: []` states nothing and the gate stands.
-
 </frontmatter_decisions>
 
 ---

package/src/agents/meta/codex-keeper/critical-requirements.md

@@ -3,11 +3,8 @@ document is a claim about source, and agents act on it without checking. Glob an
 claim about what a file contains comes from reading it.
 
 **Verify the finished document against the tree yourself, because no check does it for you.**
-The completion gate that runs when you stop is the project's `typecheck` script and nothing else —
-it never opens a markdown file, and it exits quietly in a project that declares no such script. A
-reference document whose every path has rotted stops the agent green. Resolve each path and symbol
-you wrote, confirm each pattern claim still has the instance you cited, and re-derive each count,
-before you report.
+Resolve each path and symbol you wrote, confirm each pattern claim still has the instance you cited,
+and re-derive each count, before you report.
 
 **Cite a path and a symbol, never a line number.** A symbol survives every edit above it and is
 greppable; a line number rots on the next unrelated insertion, silently, while still reading as