@ybotok/loam 0.2.0-alpha.1 → 0.2.0-alpha.13

package/dist/core/agent/agents-stamp.js.map

@@ -1 +1 @@
-{"version":3,"file":"agents-stamp.js","sourceRoot":"","sources":["../../../src/core/agent/agents-stamp.ts"],"names":[],"mappings":"AAgBA,4DAA4D;AAC5D,MAAM,UAAU,eAAe,CAAC,OAAe;IAC7C,OAAO,2BAA2B,OAAO,MAAM,CAAC;AAClD,CAAC;AAED,kFAAkF;AAClF,MAAM,QAAQ,GAAG,wCAAwC,CAAC;AAE1D;;;;GAIG;AACH,MAAM,UAAU,kBAAkB,CAAC,IAAY;IAC7C,MAAM,CAAC,GAAG,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAC9B,OAAO,CAAC,KAAK,IAAI,IAAI,YAAY,CAAC,CAAC,CAAC,CAAC,CAAE,CAAC,KAAK,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAE,CAAC,CAAC,CAAC,IAAI,CAAC;AACnE,CAAC;AAaD,uFAAuF;AACvF,SAAS,YAAY,CAAC,CAAS;IAC7B,MAAM,CAAC,GAAG,kEAAkE,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IACrF,IAAI,CAAC,KAAK,IAAI;QAAE,OAAO,IAAI,CAAC;IAC5B,OAAO;QACL,OAAO,EAAE,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;QACnD,GAAG,EAAE,CAAC,CAAC,CAAC,CAAC,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC;KAC/C,CAAC;AACJ,CAAC;AAED;;;;GAIG;AACH,SAAS,UAAU,CAAC,CAAW,EAAE,CAAW;IAC1C,+EAA+E;IAC/E,kFAAkF;IAClF,IAAI,CAAC,CAAC,MAAM,KAAK,CAAC,IAAI,CAAC,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;IACjG,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,IAAI,CAAC,EAAE,CAAC;QACzD,MAAM,CAAC,CAAC,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAE,EAAE,CAAC,CAAC,CAAC,CAAE,CAAC,CAAC;QAC9B,IAAI,CAAC,KAAK,CAAC;YAAE,SAAS;QACtB,MAAM,CAAC,EAAE,EAAE,EAAE,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC;QACpD,IAAI,EAAE,IAAI,EAAE;YAAE,OAAO,MAAM,CAAC,CAAC,CAAC,GAAG,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;QACpD,IAAI,EAAE,KAAK,EAAE;YAAE,OAAO,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;QAClC,OAAO,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;IACxB,CAAC;IACD,OAAO,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;AAClE,CAAC;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,UAAU,aAAa,CAAC,KAAa,EAAE,MAAc;IACzD,MAAM,CAAC,GAAG,YAAY,CAAC,KAAK,CAAC,CAAC;IAC9B,MAAM,CAAC,GAAG,YAAY,CAAC,MAAM,CAAC,CAAC;IAC/B,IAAI,CAAC,KAAK,IAAI,IAAI,CAAC,KAAK,IAAI;QAAE,OAAO,KAAK,CAAC;IAC3C,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,CAAC,EAAE,CAAC,IAAI,CAAC,EAAE,CAAC;QAC9B,IAAI,CAAC,CAAC,OAAO,CAAC,CAAC,CAAE,KAAK,CAAC,CAAC,OAAO,CAAC,CAAC,CAAE;YAAE,OAAO,CAAC,CAAC,OAAO,CAAC,CAAC,CAAE,GAAG,CAAC,CAAC,OAAO,CAAC,CAAC,CAAE,CAAC;IAC5E,CAAC;IACD,OAAO,UAAU,CAAC,CAAC,CAAC,GAAG,EAAE,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;AACtC,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,YAAY,CAAC,KAAa,EAAE,MAAc;IACxD,OAAO,aAAa,CAAC,MAAM,EAAE,KAAK,CAAC,CAAC;AACtC,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,MAAM,UAAU,mBAAmB,CAAC,IAAmB,EAAE,MAAc;IACrE,IAAI,IAAI,KAAK,IAAI;QAAE,OAAO,IAAI,CAAC;IAC/B,MAAM,KAAK,GAAG,kBAAkB,CAAC,IAAI,CAAC,CAAC;IACvC,IAAI,KAAK,KAAK,IAAI,IAAI,CAAC,YAAY,CAAC,KAAK,EAAE,MAAM,CAAC;QAAE,OAAO,IAAI,CAAC;IAChE,OAAO;QACL,QAAQ,EAAE,MAAM;QAChB,IAAI,EAAE,oBAAoB;QAC1B,OAAO,EACL,uCAAuC,KAAK,qBAAqB,MAAM,2BAA2B;YAClG,8FAA8F;YAC9F,2FAA2F;YAC3F,2DAA2D,KAAK,yCAAyC;YACzG,sEAAsE;KACzE,CAAC;AACJ,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,kBAAkB,CAAC,IAAmB,EAAE,MAAc;IACpE,IAAI,IAAI,KAAK,IAAI;QAAE,OAAO,IAAI,CAAC;IAC/B,MAAM,KAAK,GAAG,kBAAkB,CAAC,IAAI,CAAC,CAAC;IACvC,IAAI,KAAK,KAAK,IAAI,EAAE,CAAC;QACnB,OAAO;YACL,QAAQ,EAAE,MAAM;YAChB,IAAI,EAAE,cAAc;YACpB,OAAO,EACL,6FAA6F;gBAC7F,6FAA6F;gBAC7F,cAAc,eAAe,CAAC,MAAM,CAAC,yDAAyD;gBAC9F,iDAAiD;SACpD,CAAC;IACJ,CAAC;IACD,IAAI,CAAC,aAAa,CAAC,KAAK,EAAE,MAAM,CAAC;QAAE,OAAO,IAAI,CAAC;IAC/C,OAAO;QACL,QAAQ,EAAE,MAAM;QAChB,IAAI,EAAE,cAAc;QACpB,OAAO,EACL,kCAAkC,KAAK,qBAAqB,MAAM,8BAA8B;YAChG,2FAA2F;YAC3F,6BAA6B,MAAM,mEAAmE;KACzG,CAAC;AACJ,CAAC","sourcesContent":["/**\n * The AGENTS.md version stamp: detection, never refresh.\n *\n * AGENTS.md is written once by `loam init` and never touched again — that is\n * the ownership contract (agent.ts): it is a starting point, and a team's edits\n * to it outrank ours. But the file tells agents to branch on flag and code\n * tables, and those tables describe the binary that wrote them. OpenSpec hit\n * the same wall and answered with auto-refresh, which teaches everyone the file\n * belongs to the tool after all; loam answers with the smallest honest thing —\n * a version stamp in the generated file, and one warning when the stamp is\n * missing or trails the running binary. Reviewing the file and bumping the\n * stamp is a human act, and a hand-curated file silences the warning the same\n * way: by saying, in the stamp, that someone has looked.\n */\nimport type { Finding } from \"../vocabulary/report.js\";\n\n/** The stamp `loam init` writes at the top of AGENTS.md. */\nexport function agentsStampLine(version: string): string {\n  return `<!-- generated by loam v${version} -->`;\n}\n\n/** Matches a stamp line anywhere in the file; the capture is the version text. */\nconst STAMP_RE = /<!--\\s*generated by loam v(\\S+?)\\s*-->/;\n\n/**\n * The version the stamp names, or null when there is no stamp (or one whose\n * version does not read as numbers — unparseable is indistinguishable from\n * absent, and both get the same advice).\n */\nexport function agentsStampVersion(text: string): string | null {\n  const m = STAMP_RE.exec(text);\n  return m !== null && parseVersion(m[1]!) !== null ? m[1]! : null;\n}\n\n/** A version split the way precedence is decided: the triple, then the prerelease identifiers. */\ninterface ParsedVersion {\n  release: [number, number, number];\n  /**\n   * The dot-separated identifiers of a `-beta.2` suffix, empty for a final\n   * release. Build metadata (`+sha`) is dropped — semver excludes it from\n   * precedence, and two builds of one version are the same instructions.\n   */\n  pre: string[];\n}\n\n/** `X.Y.Z[-pre][+build]`, or null when the leading triple does not read as numbers. */\nfunction parseVersion(v: string): ParsedVersion | null {\n  const m = /^(\\d+)\\.(\\d+)\\.(\\d+)(?:-([0-9A-Za-z.-]+))?(?:\\+[0-9A-Za-z.-]+)?$/.exec(v);\n  if (m === null) return null;\n  return {\n    release: [Number(m[1]), Number(m[2]), Number(m[3])],\n    pre: m[4] === undefined ? [] : m[4].split(\".\"),\n  };\n}\n\n/**\n * Semver identifier precedence: numeric identifiers compare numerically and\n * rank below alphanumeric ones, and a longer identifier list outranks a prefix\n * of itself. -1 / 0 / 1, so the caller reads like the triple comparison above.\n */\nfunction comparePre(a: string[], b: string[]): number {\n  // No prerelease outranks any prerelease — `1.2.0` is newer than `1.2.0-beta.9`\n  // — which is why this cannot be the plain lexicographic walk the identifiers get.\n  if (a.length === 0 || b.length === 0) return a.length === b.length ? 0 : a.length === 0 ? 1 : -1;\n  for (let i = 0; i < Math.min(a.length, b.length); i += 1) {\n    const [x, y] = [a[i]!, b[i]!];\n    if (x === y) continue;\n    const [nx, ny] = [/^\\d+$/.test(x), /^\\d+$/.test(y)];\n    if (nx && ny) return Number(x) < Number(y) ? -1 : 1;\n    if (nx !== ny) return nx ? -1 : 1;\n    return x < y ? -1 : 1;\n  }\n  return a.length === b.length ? 0 : a.length < b.length ? -1 : 1;\n}\n\n/**\n * Does `stamp` name an older version than `binary`? A stamp NEWER than the\n * binary does not trail: that is an old binary, not a stale file, and the fix\n * (upgrade loam) is not an AGENTS.md edit.\n *\n * Prerelease identifiers are compared, not ignored, and the difference is the\n * whole reason this check exists. Comparing the numeric triple alone made\n * `0.1.0-beta.1` and `0.1.0-beta.2` indistinguishable — and beta.2 is precisely\n * the release that changed the FORM of every generated file (embedded protocol\n * text became a pointer at `loam instructions`), with a CHANGELOG telling\n * readers to delete the files and re-run `loam init`. The one upgrade that most\n * needed the warning was the one bump shape that could not raise it. A\n * prerelease line is where a generated file's form actually moves, because that\n * is what a prerelease is for.\n */\nexport function versionTrails(stamp: string, binary: string): boolean {\n  const s = parseVersion(stamp);\n  const b = parseVersion(binary);\n  if (s === null || b === null) return false;\n  for (let i = 0; i < 3; i += 1) {\n    if (s.release[i]! !== b.release[i]!) return s.release[i]! < b.release[i]!;\n  }\n  return comparePre(s.pre, b.pre) < 0;\n}\n\n/**\n * Does `stamp` name a version NEWER than the binary reading it? The mirror of\n * {@link versionTrails}, and a different subject rather than its negation:\n * equal versions are neither.\n */\nexport function versionAhead(stamp: string, binary: string): boolean {\n  return versionTrails(binary, stamp);\n}\n\n/**\n * `docs.binary-behind` — this loam is OLDER than the loam that wrote the docs\n * repo it is reading.\n *\n * The false-green this closes is the sharpest one in the product, because it\n * inverts the meaning of a passing run rather than merely missing a defect.\n * loam's whole promise is that a token spelled here must be spelled there — so\n * every check is an existence constraint over a value the parser recognised.\n * A binary that predates a grammar addition does not FAIL on the newer\n * directive; it does not see it, produces no value, has nothing to join, and\n * reports green. The corpus is checked less than it looks, and nothing anywhere\n * says so. `agents.stale` is the opposite direction and explicitly declines\n * this case (\"that is an old binary, not a stale file\") — correctly, because\n * the fix is different: upgrade loam, do not edit the file.\n *\n * A WARNING, not an error, and the reasoning is the `sources.stale` doctrine.\n * A mixed-version fleet is ordinary — one engineer's global install trails a\n * release by a week — and failing every command in that repo would be a\n * refusal aimed at the wrong person on the wrong day. What the message must do\n * instead is say plainly that a green run from this binary is worth less than\n * it appears, which no other finding says. A fleet that wants it to gate has\n * `--strict`, which is exactly the lever that doctrine reserves for this.\n *\n * Silent when there is no file, no stamp, or the stamp is equal or older —\n * every one of those is somebody else's finding.\n */\nexport function binaryBehindFinding(text: string | null, binary: string): Finding | null {\n  if (text === null) return null;\n  const stamp = agentsStampVersion(text);\n  if (stamp === null || !versionAhead(stamp, binary)) return null;\n  return {\n    severity: \"warn\",\n    code: \"docs.binary-behind\",\n    message:\n      `This docs repo was written by loam v${stamp}; this binary is v${binary}. A newer loam may check ` +\n      \"joins this one cannot parse — an unrecognised directive is read as prose, so it produces no \" +\n      \"join to fail and this run reports green without having graded it. Treat a pass from this \" +\n      `binary as incomplete rather than clean, and upgrade to v${stamp} or later (\\`npm i -g @ybotok/loam\\`). ` +\n      \"Nothing here is wrong with the documents; the reader is behind them.\",\n  };\n}\n\n/**\n * The one finding `loam validate --all` owes the agent contract. `text` is the\n * docs repo's AGENTS.md, or null when there is none — no file means no contract\n * to have drifted, and this check stays silent rather than inventing a second\n * meaning for its code. Returns null when the stamp is current (or newer).\n */\nexport function agentsStaleFinding(text: string | null, binary: string): Finding | null {\n  if (text === null) return null;\n  const stamp = agentsStampVersion(text);\n  if (stamp === null) {\n    return {\n      severity: \"warn\",\n      code: \"agents.stale\",\n      message:\n        \"AGENTS.md has no version stamp — it predates stamping or was hand-created, so nothing says \" +\n        \"which loam its flag and code tables describe. Review it against the current `loam --help`, \" +\n        `then add \\`${agentsStampLine(binary)}\\` near the top; a hand-curated file keeps the warning ` +\n        \"off the same way, by keeping the stamp current.\",\n    };\n  }\n  if (!versionTrails(stamp, binary)) return null;\n  return {\n    severity: \"warn\",\n    code: \"agents.stale\",\n    message:\n      `AGENTS.md was written by loam v${stamp}; this binary is v${binary} — the flag and code tables ` +\n      \"agents branch on may have moved. Review the file against the current `loam --help`, then \" +\n      `update the stamp line to v${binary} (a hand-curated file silences this by bumping the stamp itself).`,\n  };\n}\n"]}
+{"version":3,"file":"agents-stamp.js","sourceRoot":"","sources":["../../../src/core/agent/agents-stamp.ts"],"names":[],"mappings":"AAgBA,4DAA4D;AAC5D,MAAM,UAAU,eAAe,CAAC,OAAe;IAC7C,OAAO,2BAA2B,OAAO,MAAM,CAAC;AAClD,CAAC;AAED,kFAAkF;AAClF,MAAM,QAAQ,GAAG,wCAAwC,CAAC;AAE1D;;;;;;GAMG;AACH,MAAM,UAAU,SAAS,CAAC,IAAY,EAAE,OAAe;IACrD,OAAO,IAAI,CAAC,OAAO,CAAC,QAAQ,EAAE,eAAe,CAAC,OAAO,CAAC,CAAC,CAAC;AAC1D,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,kBAAkB,CAAC,IAAY;IAC7C,MAAM,CAAC,GAAG,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAC9B,OAAO,CAAC,KAAK,IAAI,IAAI,YAAY,CAAC,CAAC,CAAC,CAAC,CAAE,CAAC,KAAK,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAE,CAAC,CAAC,CAAC,IAAI,CAAC;AACnE,CAAC;AAaD,uFAAuF;AACvF,SAAS,YAAY,CAAC,CAAS;IAC7B,MAAM,CAAC,GAAG,kEAAkE,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IACrF,IAAI,CAAC,KAAK,IAAI;QAAE,OAAO,IAAI,CAAC;IAC5B,OAAO;QACL,OAAO,EAAE,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;QACnD,GAAG,EAAE,CAAC,CAAC,CAAC,CAAC,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC;KAC/C,CAAC;AACJ,CAAC;AAED;;;;GAIG;AACH,SAAS,UAAU,CAAC,CAAW,EAAE,CAAW;IAC1C,+EAA+E;IAC/E,kFAAkF;IAClF,IAAI,CAAC,CAAC,MAAM,KAAK,CAAC,IAAI,CAAC,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;IACjG,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,IAAI,CAAC,EAAE,CAAC;QACzD,MAAM,CAAC,CAAC,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAE,EAAE,CAAC,CAAC,CAAC,CAAE,CAAC,CAAC;QAC9B,IAAI,CAAC,KAAK,CAAC;YAAE,SAAS;QACtB,MAAM,CAAC,EAAE,EAAE,EAAE,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC;QACpD,IAAI,EAAE,IAAI,EAAE;YAAE,OAAO,MAAM,CAAC,CAAC,CAAC,GAAG,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;QACpD,IAAI,EAAE,KAAK,EAAE;YAAE,OAAO,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;QAClC,OAAO,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;IACxB,CAAC;IACD,OAAO,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;AAClE,CAAC;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,UAAU,aAAa,CAAC,KAAa,EAAE,MAAc;IACzD,MAAM,CAAC,GAAG,YAAY,CAAC,KAAK,CAAC,CAAC;IAC9B,MAAM,CAAC,GAAG,YAAY,CAAC,MAAM,CAAC,CAAC;IAC/B,IAAI,CAAC,KAAK,IAAI,IAAI,CAAC,KAAK,IAAI;QAAE,OAAO,KAAK,CAAC;IAC3C,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,CAAC,EAAE,CAAC,IAAI,CAAC,EAAE,CAAC;QAC9B,IAAI,CAAC,CAAC,OAAO,CAAC,CAAC,CAAE,KAAK,CAAC,CAAC,OAAO,CAAC,CAAC,CAAE;YAAE,OAAO,CAAC,CAAC,OAAO,CAAC,CAAC,CAAE,GAAG,CAAC,CAAC,OAAO,CAAC,CAAC,CAAE,CAAC;IAC5E,CAAC;IACD,OAAO,UAAU,CAAC,CAAC,CAAC,GAAG,EAAE,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;AACtC,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,YAAY,CAAC,KAAa,EAAE,MAAc;IACxD,OAAO,aAAa,CAAC,MAAM,EAAE,KAAK,CAAC,CAAC;AACtC,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,MAAM,UAAU,mBAAmB,CAAC,IAAmB,EAAE,MAAc;IACrE,IAAI,IAAI,KAAK,IAAI;QAAE,OAAO,IAAI,CAAC;IAC/B,MAAM,KAAK,GAAG,kBAAkB,CAAC,IAAI,CAAC,CAAC;IACvC,IAAI,KAAK,KAAK,IAAI,IAAI,CAAC,YAAY,CAAC,KAAK,EAAE,MAAM,CAAC;QAAE,OAAO,IAAI,CAAC;IAChE,OAAO;QACL,QAAQ,EAAE,MAAM;QAChB,IAAI,EAAE,oBAAoB;QAC1B,OAAO,EACL,uCAAuC,KAAK,qBAAqB,MAAM,2BAA2B;YAClG,8FAA8F;YAC9F,2FAA2F;YAC3F,2DAA2D,KAAK,yCAAyC;YACzG,sEAAsE;KACzE,CAAC;AACJ,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,kBAAkB,CAAC,IAAmB,EAAE,MAAc;IACpE,IAAI,IAAI,KAAK,IAAI;QAAE,OAAO,IAAI,CAAC;IAC/B,MAAM,KAAK,GAAG,kBAAkB,CAAC,IAAI,CAAC,CAAC;IACvC,IAAI,KAAK,KAAK,IAAI,EAAE,CAAC;QACnB,OAAO;YACL,QAAQ,EAAE,MAAM;YAChB,IAAI,EAAE,cAAc;YACpB,OAAO,EACL,6FAA6F;gBAC7F,6FAA6F;gBAC7F,cAAc,eAAe,CAAC,MAAM,CAAC,yDAAyD;gBAC9F,iDAAiD;SACpD,CAAC;IACJ,CAAC;IACD,IAAI,CAAC,aAAa,CAAC,KAAK,EAAE,MAAM,CAAC;QAAE,OAAO,IAAI,CAAC;IAC/C,OAAO;QACL,QAAQ,EAAE,MAAM;QAChB,IAAI,EAAE,cAAc;QACpB,OAAO,EACL,kCAAkC,KAAK,qBAAqB,MAAM,8BAA8B;YAChG,2FAA2F;YAC3F,6BAA6B,MAAM,mEAAmE;KACzG,CAAC;AACJ,CAAC","sourcesContent":["/**\n * The AGENTS.md version stamp: detection, never refresh.\n *\n * AGENTS.md is written once by `loam init` and never touched again — that is\n * the ownership contract (agent.ts): it is a starting point, and a team's edits\n * to it outrank ours. But the file tells agents to branch on flag and code\n * tables, and those tables describe the binary that wrote them. OpenSpec hit\n * the same wall and answered with auto-refresh, which teaches everyone the file\n * belongs to the tool after all; loam answers with the smallest honest thing —\n * a version stamp in the generated file, and one warning when the stamp is\n * missing or trails the running binary. Reviewing the file and bumping the\n * stamp is a human act, and a hand-curated file silences the warning the same\n * way: by saying, in the stamp, that someone has looked.\n */\nimport type { Finding } from \"../vocabulary/report.js\";\n\n/** The stamp `loam init` writes at the top of AGENTS.md. */\nexport function agentsStampLine(version: string): string {\n  return `<!-- generated by loam v${version} -->`;\n}\n\n/** Matches a stamp line anywhere in the file; the capture is the version text. */\nconst STAMP_RE = /<!--\\s*generated by loam v(\\S+?)\\s*-->/;\n\n/**\n * `text` with its stamp, when it has one, rewritten to name `version` — every\n * other byte untouched. What lets a caller ask whether a generated file differs\n * from what a binary would write in anything BUT the stamp: the pointer files\n * carry this same line, and a release that changes nothing in their body still\n * changes it.\n */\nexport function restamped(text: string, version: string): string {\n  return text.replace(STAMP_RE, agentsStampLine(version));\n}\n\n/**\n * The version the stamp names, or null when there is no stamp (or one whose\n * version does not read as numbers — unparseable is indistinguishable from\n * absent, and both get the same advice).\n */\nexport function agentsStampVersion(text: string): string | null {\n  const m = STAMP_RE.exec(text);\n  return m !== null && parseVersion(m[1]!) !== null ? m[1]! : null;\n}\n\n/** A version split the way precedence is decided: the triple, then the prerelease identifiers. */\ninterface ParsedVersion {\n  release: [number, number, number];\n  /**\n   * The dot-separated identifiers of a `-beta.2` suffix, empty for a final\n   * release. Build metadata (`+sha`) is dropped — semver excludes it from\n   * precedence, and two builds of one version are the same instructions.\n   */\n  pre: string[];\n}\n\n/** `X.Y.Z[-pre][+build]`, or null when the leading triple does not read as numbers. */\nfunction parseVersion(v: string): ParsedVersion | null {\n  const m = /^(\\d+)\\.(\\d+)\\.(\\d+)(?:-([0-9A-Za-z.-]+))?(?:\\+[0-9A-Za-z.-]+)?$/.exec(v);\n  if (m === null) return null;\n  return {\n    release: [Number(m[1]), Number(m[2]), Number(m[3])],\n    pre: m[4] === undefined ? [] : m[4].split(\".\"),\n  };\n}\n\n/**\n * Semver identifier precedence: numeric identifiers compare numerically and\n * rank below alphanumeric ones, and a longer identifier list outranks a prefix\n * of itself. -1 / 0 / 1, so the caller reads like the triple comparison above.\n */\nfunction comparePre(a: string[], b: string[]): number {\n  // No prerelease outranks any prerelease — `1.2.0` is newer than `1.2.0-beta.9`\n  // — which is why this cannot be the plain lexicographic walk the identifiers get.\n  if (a.length === 0 || b.length === 0) return a.length === b.length ? 0 : a.length === 0 ? 1 : -1;\n  for (let i = 0; i < Math.min(a.length, b.length); i += 1) {\n    const [x, y] = [a[i]!, b[i]!];\n    if (x === y) continue;\n    const [nx, ny] = [/^\\d+$/.test(x), /^\\d+$/.test(y)];\n    if (nx && ny) return Number(x) < Number(y) ? -1 : 1;\n    if (nx !== ny) return nx ? -1 : 1;\n    return x < y ? -1 : 1;\n  }\n  return a.length === b.length ? 0 : a.length < b.length ? -1 : 1;\n}\n\n/**\n * Does `stamp` name an older version than `binary`? A stamp NEWER than the\n * binary does not trail: that is an old binary, not a stale file, and the fix\n * (upgrade loam) is not an AGENTS.md edit.\n *\n * Prerelease identifiers are compared, not ignored, and the difference is the\n * whole reason this check exists. Comparing the numeric triple alone made\n * `0.1.0-beta.1` and `0.1.0-beta.2` indistinguishable — and beta.2 is precisely\n * the release that changed the FORM of every generated file (embedded protocol\n * text became a pointer at `loam instructions`), with a CHANGELOG telling\n * readers to delete the files and re-run `loam init`. The one upgrade that most\n * needed the warning was the one bump shape that could not raise it. A\n * prerelease line is where a generated file's form actually moves, because that\n * is what a prerelease is for.\n */\nexport function versionTrails(stamp: string, binary: string): boolean {\n  const s = parseVersion(stamp);\n  const b = parseVersion(binary);\n  if (s === null || b === null) return false;\n  for (let i = 0; i < 3; i += 1) {\n    if (s.release[i]! !== b.release[i]!) return s.release[i]! < b.release[i]!;\n  }\n  return comparePre(s.pre, b.pre) < 0;\n}\n\n/**\n * Does `stamp` name a version NEWER than the binary reading it? The mirror of\n * {@link versionTrails}, and a different subject rather than its negation:\n * equal versions are neither.\n */\nexport function versionAhead(stamp: string, binary: string): boolean {\n  return versionTrails(binary, stamp);\n}\n\n/**\n * `docs.binary-behind` — this loam is OLDER than the loam that wrote the docs\n * repo it is reading.\n *\n * The false-green this closes is the sharpest one in the product, because it\n * inverts the meaning of a passing run rather than merely missing a defect.\n * loam's whole promise is that a token spelled here must be spelled there — so\n * every check is an existence constraint over a value the parser recognised.\n * A binary that predates a grammar addition does not FAIL on the newer\n * directive; it does not see it, produces no value, has nothing to join, and\n * reports green. The corpus is checked less than it looks, and nothing anywhere\n * says so. `agents.stale` is the opposite direction and explicitly declines\n * this case (\"that is an old binary, not a stale file\") — correctly, because\n * the fix is different: upgrade loam, do not edit the file.\n *\n * A WARNING, not an error, and the reasoning is the `sources.stale` doctrine.\n * A mixed-version fleet is ordinary — one engineer's global install trails a\n * release by a week — and failing every command in that repo would be a\n * refusal aimed at the wrong person on the wrong day. What the message must do\n * instead is say plainly that a green run from this binary is worth less than\n * it appears, which no other finding says. A fleet that wants it to gate has\n * `--strict`, which is exactly the lever that doctrine reserves for this.\n *\n * Silent when there is no file, no stamp, or the stamp is equal or older —\n * every one of those is somebody else's finding.\n */\nexport function binaryBehindFinding(text: string | null, binary: string): Finding | null {\n  if (text === null) return null;\n  const stamp = agentsStampVersion(text);\n  if (stamp === null || !versionAhead(stamp, binary)) return null;\n  return {\n    severity: \"warn\",\n    code: \"docs.binary-behind\",\n    message:\n      `This docs repo was written by loam v${stamp}; this binary is v${binary}. A newer loam may check ` +\n      \"joins this one cannot parse — an unrecognised directive is read as prose, so it produces no \" +\n      \"join to fail and this run reports green without having graded it. Treat a pass from this \" +\n      `binary as incomplete rather than clean, and upgrade to v${stamp} or later (\\`npm i -g @ybotok/loam\\`). ` +\n      \"Nothing here is wrong with the documents; the reader is behind them.\",\n  };\n}\n\n/**\n * The one finding `loam validate --all` owes the agent contract. `text` is the\n * docs repo's AGENTS.md, or null when there is none — no file means no contract\n * to have drifted, and this check stays silent rather than inventing a second\n * meaning for its code. Returns null when the stamp is current (or newer).\n */\nexport function agentsStaleFinding(text: string | null, binary: string): Finding | null {\n  if (text === null) return null;\n  const stamp = agentsStampVersion(text);\n  if (stamp === null) {\n    return {\n      severity: \"warn\",\n      code: \"agents.stale\",\n      message:\n        \"AGENTS.md has no version stamp — it predates stamping or was hand-created, so nothing says \" +\n        \"which loam its flag and code tables describe. Review it against the current `loam --help`, \" +\n        `then add \\`${agentsStampLine(binary)}\\` near the top; a hand-curated file keeps the warning ` +\n        \"off the same way, by keeping the stamp current.\",\n    };\n  }\n  if (!versionTrails(stamp, binary)) return null;\n  return {\n    severity: \"warn\",\n    code: \"agents.stale\",\n    message:\n      `AGENTS.md was written by loam v${stamp}; this binary is v${binary} — the flag and code tables ` +\n      \"agents branch on may have moved. Review the file against the current `loam --help`, then \" +\n      `update the stamp line to v${binary} (a hand-curated file silences this by bumping the stamp itself).`,\n  };\n}\n"]}

package/dist/core/agent/protocol.js

@@ -39,7 +39,7 @@ export const SUPPORT = [LOAM_REPORT];
 export const AGENT_COMMANDS = [...COMMANDS, ...SUPPORT];
 /**
  * Everything `loam instructions <name>` can print: the six workflows, support
- * protocol and four reference pages, in that order.
+ * protocol and five reference pages, in that order.
  *
  * The pages join the generated protocols HERE and nowhere else — not in
  * {@link AGENT_COMMANDS}, which is what scaffold.ts derives `SLASH_COMMANDS`

package/dist/core/agent/protocol.js.map

@@ -1 +1 @@
-{"version":3,"file":"protocol.js","sourceRoot":"","sources":["../../../src/core/agent/protocol.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,OAAO,EAAE,gBAAgB,EAAE,MAAM,0BAA0B,CAAC;AAC5D,OAAO,EAAE,gBAAgB,EAAE,MAAM,0BAA0B,CAAC;AAE5D,OAAO,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AAClD,OAAO,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AAClD,OAAO,EAAE,WAAW,EAAE,SAAS,EAAE,MAAM,wBAAwB,CAAC;AAChE,OAAO,EAAE,YAAY,EAAE,MAAM,wBAAwB,CAAC;AACtD,OAAO,EAAE,cAAc,EAAE,MAAM,0BAA0B,CAAC;AAC1D,OAAO,EAAE,UAAU,EAAE,MAAM,oCAAoC,CAAC;AAChE,OAAO,EAAE,WAAW,EAAE,MAAM,qBAAqB,CAAC;AAElD;;;;;GAKG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAqB;IACxC,UAAU;IACV,YAAY;IACZ,cAAc;IACd,UAAU;IACV,WAAW;IACX,SAAS;CACV,CAAC;AAEF;;;;;GAKG;AACH,MAAM,CAAC,MAAM,OAAO,GAAqB,CAAC,WAAW,CAAC,CAAC;AAEvD,uEAAuE;AACvE,MAAM,CAAC,MAAM,cAAc,GAAqB,CAAC,GAAG,QAAQ,EAAE,GAAG,OAAO,CAAC,CAAC;AAE1E;;;;;;;;;;;;;;GAcG;AACH,MAAM,SAAS,GAAqB,CAAC,GAAG,cAAc,EAAE,GAAG,UAAU,CAAC,CAAC;AAEvE;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,SAAS,GAA2B,MAAM,CAAC,WAAW,CACjE,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,CACvC,CAAC;AAEF;;;;;GAKG;AACH,MAAM,CAAC,MAAM,YAAY,GAA+C,MAAM,CAAC,WAAW,CACxF,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,YAAY,CAAC,CAAC,CAC/C,CAAC;AAEF;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,MAAM,UAAU,GAAG,CAAC,GAAuB,EAAW,EAAE,CACtD,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,EAAE,IAAI,WAAW,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAE3D;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,mBAAmB,CAAC,IAAY,EAAE,IAAuB;IACvE,MAAM,KAAK,GAAG,YAAY,CAAC,IAAI,CAAC,CAAC;IACjC,IAAI,KAAK,KAAK,SAAS;QAAE,OAAO,IAAI,CAAC;IACrC,MAAM,QAAQ,GAAG,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,CAAC,EAAE,EAAE;QACzC,MAAM,GAAG,GAAG,IAAI,CAAC,CAAC,CAAC,CAAC;QACpB,yEAAyE;QACzE,oEAAoE;QACpE,IAAI,GAAG,KAAK,SAAS,IAAI,UAAU,CAAC,GAAG,CAAC,IAAI,IAAI,KAAK,MAAM;YAAE,OAAO,EAAE,CAAC;QACvE,MAAM,OAAO,GAAG,IAAI,KAAK,SAAS;YAChC,CAAC,CAAC,gBAAgB,CAAC,GAAG,EAAE,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC;YACpC,CAAC,CAAC,gBAAgB,CAAC,GAAG,EAAE,gBAAgB,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;QACpD,OAAO,OAAO,KAAK,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC;IAC3C,CAAC,CAAC,CAAC;IACH,OAAO,QAAQ,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,QAAQ,CAAC;AACjD,CAAC;AAKD,MAAM,GAAG,GAAG,CAAC,EAAE,IAAI,EAAE,WAAW,EAAE,YAAY,EAAkB,EAAW,EAAE,CAC3E,CAAC,EAAE,IAAI,EAAE,WAAW,EAAE,YAAY,EAAE,CAAC,CAAC;AAExC,6FAA6F;AAC7F,MAAM,CAAC,MAAM,SAAS,GAAuB,QAAQ,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;AAE/D,2FAA2F;AAC3F,MAAM,CAAC,MAAM,aAAa,GAAuB,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;AAElE;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,eAAe,GAAuB,UAAU,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;AAEvE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,MAAM,UAAU,WAAW,CAAC,IAAY,EAAE,IAAI,GAAsB,EAAE;IACpE,MAAM,IAAI,GAAG,SAAS,CAAC,IAAI,CAAC,CAAC;IAC7B,IAAI,IAAI,KAAK,SAAS;QAAE,OAAO,IAAI,CAAC;IACpC,OAAO,IAAI,CAAC,OAAO,CAAC,YAAY,EAAE,CAAC,KAAK,EAAE,KAAa,EAAE,EAAE;QACzD,MAAM,GAAG,GAAG,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC;QACpC,OAAO,GAAG,KAAK,SAAS,IAAI,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,GAAG,CAAC;IAC5D,CAAC,CAAC,CAAC;AACL,CAAC","sourcesContent":["/**\n * The protocol surface: six lifecycle workflows, the support protocol and the\n * reference pages — what `loam instructions` prints (commands/instructions.ts)\n * and the corpus every check over loam's agent-facing prose reads\n * (test/codes-drift.test.ts, test/agent-contract.test.ts,\n * test/agent-commands-runnable.test.ts).\n */\nimport { featureIdProblem } from \"../kernel/ids/feature.js\";\nimport { serviceIdProblem } from \"../kernel/ids/service.js\";\nimport type { CommandContent, PlaceholderKind } from \"./contract.js\";\nimport { LOAM_ADOPT } from \"./workflows/adopt.js\";\nimport { LOAM_CHECK } from \"./workflows/check.js\";\nimport { LOAM_VERIFY, LOAM_SHIP } from \"./workflows/closing.js\";\nimport { LOAM_FEATURE } from \"./workflows/feature.js\";\nimport { LOAM_IMPLEMENT } from \"./workflows/implement.js\";\nimport { REFERENCES } from \"./workflows/reference/reference.js\";\nimport { LOAM_REPORT } from \"./support/report.js\";\n\n/**\n * The six protocols, in cycle order. One assembly, exported: scaffold.ts\n * derives the generated files through this same list, so what\n * `loam instructions` prints and what a fresh scaffold writes cannot drift\n * apart.\n */\nexport const COMMANDS: CommandContent[] = [\n  LOAM_ADOPT,\n  LOAM_FEATURE,\n  LOAM_IMPLEMENT,\n  LOAM_CHECK,\n  LOAM_VERIFY,\n  LOAM_SHIP,\n];\n\n/**\n * Support entry points generated beside the lifecycle, but not counted as\n * lifecycle steps. Reporting a bad run must be discoverable in every profile;\n * placing it in COMMANDS would make a consumer iterating that list try to run\n * incident collection after every feature.\n */\nexport const SUPPORT: CommandContent[] = [LOAM_REPORT];\n\n/** Every command/skill file init generates, regardless of category. */\nexport const AGENT_COMMANDS: CommandContent[] = [...COMMANDS, ...SUPPORT];\n\n/**\n * Everything `loam instructions <name>` can print: the six workflows, support\n * protocol and four reference pages, in that order.\n *\n * The pages join the generated protocols HERE and nowhere else — not in\n * {@link AGENT_COMMANDS}, which is what scaffold.ts derives `SLASH_COMMANDS`\n * and `plannedCommandFiles` from. That is the whole mechanism, and the\n * asymmetry is the point: a page is printable by name but `loam init` writes no\n * file for it, so moving 44 KB out of AGENTS.md did not put 44 KB back as four\n * new artifacts in every repository loam touches. The support protocol does\n * belong in AGENT_COMMANDS because discovery is its purpose, while its separate\n * menu category keeps it out of the lifecycle. test/agents.test.ts asserts the\n * reference-page halves separately, because a future edit can break either\n * alone.\n */\nconst PRINTABLE: CommandContent[] = [...AGENT_COMMANDS, ...REFERENCES];\n\n/**\n * The printable bodies, keyed by name — what `loam instructions <name>` prints,\n * and the corpus every check over loam's agent-facing prose reads.\n *\n * Separate from SLASH_COMMANDS since the file became a pointer: the protocol is\n * still the thing that must document every stable code (`codes-drift`) and\n * every `loam …` line it teaches must still parse against the real CLI\n * (`agent-commands-runnable`). Those two properties are about the INSTRUCTIONS,\n * and they did not move just because the delivery did.\n *\n * The reference pages belong in this record for exactly that reason. Every code\n * they carry LEFT AGENTS.md to get here, and `codes-drift` reads\n * `AGENTS_MD + PROTOCOLS` — so the guard stays green by construction, because\n * the codes moved from one half of that corpus into the other. If it goes red\n * after a change here, something was deleted rather than moved.\n */\nexport const PROTOCOLS: Record<string, string> = Object.fromEntries(\n  PRINTABLE.map((c) => [c.name, c.body]),\n);\n\n/**\n * What each page's `$1`, `$2`, … denote — see {@link CommandContent.placeholders}.\n * A reference page declares `[]`, which is not a formality: `placeholderProblems`\n * keys off this record, and a name absent from it is treated as unknown rather\n * than as taking no arguments.\n */\nexport const PLACEHOLDERS: Record<string, readonly PlaceholderKind[]> = Object.fromEntries(\n  PRINTABLE.map((c) => [c.name, c.placeholders]),\n);\n\n/**\n * Whether nothing was supplied for this position — the two shapes an absent\n * argument actually arrives in, in one place because both call sites below owe\n * the same answer.\n *\n * The first is empty; {@link protocolFor} says which dialects send that. The\n * second is the placeholder ITSELF, arriving as data. One body serves twenty\n * tool dialects (tools/registry.ts) and keeps Claude's positional `$1`/`$2`\n * convention in all of them (see {@link CommandContent}), so every generated\n * stub carries the spelling verbatim: `.gemini/commands/loam/adopt.toml`\n * contains the literal line `loam instructions loam-adopt $1`. Gemini's own\n * convention is `{{args}}` and Copilot's is `${input:…}`, and Cline, Kilo Code\n * and Roo Code substitute nothing whatever — so on those three the `$1` reaches\n * this command exactly as written, and loam refused the literal first\n * instruction of its own workflow with `invalid-option`. (Unquoted in a POSIX\n * shell the same line degrades the other way: `$1` expands to empty, and the\n * agent receives a protocol addressed to nobody.) The same class already cost\n * `loam-check` its placeholder — see the comment in workflows/check.ts; this is\n * the general fix, made once in the RECEIVING command rather than per dialect.\n *\n * Scoped to `^\\$[1-9]$` and no wider. `{{args}}` and `${input:…}` are\n * deliberately NOT matched: the tools that spell placeholders that way\n * substitute them before an agent ever reads the file, so they cannot arrive\n * here, and loam emits neither. A value that merely CONTAINS a placeholder\n * (`FEAT-$1`) is a real argument and is still checked as one.\n */\nconst unsupplied = (arg: string | undefined): boolean =>\n  arg === undefined || arg === \"\" || /^\\$[1-9]$/.test(arg);\n\n/**\n * Why the arguments given to `name` cannot be substituted into its protocol, or\n * null when they can. One sentence per bad argument, already naming the\n * placeholder it was meant to fill.\n *\n * The grammars are `core/kernel/ids/`'s, never a second copy: a value this accepts\n * and `loam adopt` refuses would be worse than no check, because the protocol\n * would still be wrong and now something had approved it. An argument nobody\n * supplied is not an error — `protocolFor` leaves that placeholder standing on\n * purpose, so the page reads as \"the service id goes here\" — and by\n * {@link unsupplied} that covers the placeholder text arriving as the argument,\n * which is what an untouched generated stub sends.\n */\nexport function placeholderProblems(name: string, args: readonly string[]): string[] | null {\n  const kinds = PLACEHOLDERS[name];\n  if (kinds === undefined) return null;\n  const problems = kinds.flatMap((kind, i) => {\n    const arg = args[i];\n    // The `undefined` arm is `unsupplied`'s own; it is repeated here because\n    // that is what narrows `arg` to a string for the id grammars below.\n    if (arg === undefined || unsupplied(arg) || kind === \"free\") return [];\n    const problem = kind === \"service\"\n      ? serviceIdProblem(arg, `$${i + 1}`)\n      : featureIdProblem(arg, `feature id ($${i + 1})`);\n    return problem === null ? [] : [problem];\n  });\n  return problems.length === 0 ? null : problems;\n}\n\n/** One row of the `loam instructions` menu: enough to choose, and nothing more. */\ntype MenuRow = Pick<CommandContent, \"name\" | \"description\" | \"argumentHint\">;\n\nconst row = ({ name, description, argumentHint }: CommandContent): MenuRow =>\n  ({ name, description, argumentHint });\n\n/** The workflow names, in cycle order — `loam instructions` with no argument lists these. */\nexport const WORKFLOWS: readonly MenuRow[] = COMMANDS.map(row);\n\n/** Support protocols, listed separately so no caller mistakes one for a lifecycle step. */\nexport const SUPPORT_PAGES: readonly MenuRow[] = SUPPORT.map(row);\n\n/**\n * The reference-page names, listed by the same bare `loam instructions` and\n * kept a SEPARATE list rather than appended to {@link WORKFLOWS}.\n *\n * A page is not a workflow: it has no steps, it is not part of the cycle, and\n * running one is not doing anything. A menu that ran the ten together would\n * read as a ten-step process, which is the one thing the six-step cycle must\n * not be confused with — so the command prints them under their own heading\n * (commands/instructions.ts) and test/instructions.test.ts pins that they stay\n * apart.\n */\nexport const REFERENCE_PAGES: readonly MenuRow[] = REFERENCES.map(row);\n\n/**\n * One workflow's protocol with `$1`, `$2`, … replaced by the arguments given.\n *\n * An unsupplied placeholder is LEFT STANDING rather than blanked: the bodies\n * are written so `$1` reads as \"the feature id goes here\", and a protocol that\n * silently dropped it would hand an agent `loam validate --feature --json` — a\n * command that parses, runs, and answers a different question. Extra arguments\n * are ignored for the same reason: this substitutes, it does not validate.\n *\n * \"Unsupplied\" is {@link unsupplied}'s two shapes, not merely a missing\n * element, and neither is pedantry — they are the two things a tool actually\n * sends. An EMPTY argument is the first: several dialects expand an absent\n * positional to the empty string, and `loam-feature`'s own invocation quotes\n * its second one (`--title \"$2\"`), so `/loam-feature FEAT-101` with no title\n * arrives here as `[\"FEAT-101\", \"\"]`. Blanking it produced\n * `loam new FEAT-101 --title \"\"` — which is exactly the failure the paragraph\n * above describes, reached by the one path that paragraph did not cover: the\n * command succeeds, and writes a feature whose title is the empty string and\n * whose intent.md opens with a bare `#`.\n *\n * The LITERAL PLACEHOLDER is the second: the dialects that substitute nothing\n * hand this command the `$1` their generated stub was written with, so\n * `loam instructions loam-adopt $1` renders the same page as\n * `loam instructions loam-adopt` — the placeholder standing, the protocol\n * printed. Here the shape mostly falls out anyway (planting `$1` where `$1`\n * stood is a no-op); it is spelled all the same, because a MISNUMBERED one\n * would not be — `$3` given for `$1` would renumber the placeholder in the\n * printed page — and because the check above and this render have to agree on\n * one definition or a value can pass one and be rewritten by the other.\n */\nexport function protocolFor(name: string, args: readonly string[] = []): string | null {\n  const body = PROTOCOLS[name];\n  if (body === undefined) return null;\n  return body.replace(/\\$([1-9])/g, (whole, digit: string) => {\n    const arg = args[Number(digit) - 1];\n    return arg === undefined || unsupplied(arg) ? whole : arg;\n  });\n}\n"]}
+{"version":3,"file":"protocol.js","sourceRoot":"","sources":["../../../src/core/agent/protocol.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,OAAO,EAAE,gBAAgB,EAAE,MAAM,0BAA0B,CAAC;AAC5D,OAAO,EAAE,gBAAgB,EAAE,MAAM,0BAA0B,CAAC;AAE5D,OAAO,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AAClD,OAAO,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AAClD,OAAO,EAAE,WAAW,EAAE,SAAS,EAAE,MAAM,wBAAwB,CAAC;AAChE,OAAO,EAAE,YAAY,EAAE,MAAM,wBAAwB,CAAC;AACtD,OAAO,EAAE,cAAc,EAAE,MAAM,0BAA0B,CAAC;AAC1D,OAAO,EAAE,UAAU,EAAE,MAAM,oCAAoC,CAAC;AAChE,OAAO,EAAE,WAAW,EAAE,MAAM,qBAAqB,CAAC;AAElD;;;;;GAKG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAqB;IACxC,UAAU;IACV,YAAY;IACZ,cAAc;IACd,UAAU;IACV,WAAW;IACX,SAAS;CACV,CAAC;AAEF;;;;;GAKG;AACH,MAAM,CAAC,MAAM,OAAO,GAAqB,CAAC,WAAW,CAAC,CAAC;AAEvD,uEAAuE;AACvE,MAAM,CAAC,MAAM,cAAc,GAAqB,CAAC,GAAG,QAAQ,EAAE,GAAG,OAAO,CAAC,CAAC;AAE1E;;;;;;;;;;;;;;GAcG;AACH,MAAM,SAAS,GAAqB,CAAC,GAAG,cAAc,EAAE,GAAG,UAAU,CAAC,CAAC;AAEvE;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,SAAS,GAA2B,MAAM,CAAC,WAAW,CACjE,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,CACvC,CAAC;AAEF;;;;;GAKG;AACH,MAAM,CAAC,MAAM,YAAY,GAA+C,MAAM,CAAC,WAAW,CACxF,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,YAAY,CAAC,CAAC,CAC/C,CAAC;AAEF;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,MAAM,UAAU,GAAG,CAAC,GAAuB,EAAW,EAAE,CACtD,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,EAAE,IAAI,WAAW,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAE3D;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,mBAAmB,CAAC,IAAY,EAAE,IAAuB;IACvE,MAAM,KAAK,GAAG,YAAY,CAAC,IAAI,CAAC,CAAC;IACjC,IAAI,KAAK,KAAK,SAAS;QAAE,OAAO,IAAI,CAAC;IACrC,MAAM,QAAQ,GAAG,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,CAAC,EAAE,EAAE;QACzC,MAAM,GAAG,GAAG,IAAI,CAAC,CAAC,CAAC,CAAC;QACpB,yEAAyE;QACzE,oEAAoE;QACpE,IAAI,GAAG,KAAK,SAAS,IAAI,UAAU,CAAC,GAAG,CAAC,IAAI,IAAI,KAAK,MAAM;YAAE,OAAO,EAAE,CAAC;QACvE,MAAM,OAAO,GAAG,IAAI,KAAK,SAAS;YAChC,CAAC,CAAC,gBAAgB,CAAC,GAAG,EAAE,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC;YACpC,CAAC,CAAC,gBAAgB,CAAC,GAAG,EAAE,gBAAgB,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;QACpD,OAAO,OAAO,KAAK,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC;IAC3C,CAAC,CAAC,CAAC;IACH,OAAO,QAAQ,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,QAAQ,CAAC;AACjD,CAAC;AAKD,MAAM,GAAG,GAAG,CAAC,EAAE,IAAI,EAAE,WAAW,EAAE,YAAY,EAAkB,EAAW,EAAE,CAC3E,CAAC,EAAE,IAAI,EAAE,WAAW,EAAE,YAAY,EAAE,CAAC,CAAC;AAExC,6FAA6F;AAC7F,MAAM,CAAC,MAAM,SAAS,GAAuB,QAAQ,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;AAE/D,2FAA2F;AAC3F,MAAM,CAAC,MAAM,aAAa,GAAuB,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;AAElE;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,eAAe,GAAuB,UAAU,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;AAEvE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,MAAM,UAAU,WAAW,CAAC,IAAY,EAAE,IAAI,GAAsB,EAAE;IACpE,MAAM,IAAI,GAAG,SAAS,CAAC,IAAI,CAAC,CAAC;IAC7B,IAAI,IAAI,KAAK,SAAS;QAAE,OAAO,IAAI,CAAC;IACpC,OAAO,IAAI,CAAC,OAAO,CAAC,YAAY,EAAE,CAAC,KAAK,EAAE,KAAa,EAAE,EAAE;QACzD,MAAM,GAAG,GAAG,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC;QACpC,OAAO,GAAG,KAAK,SAAS,IAAI,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,GAAG,CAAC;IAC5D,CAAC,CAAC,CAAC;AACL,CAAC","sourcesContent":["/**\n * The protocol surface: six lifecycle workflows, the support protocol and the\n * reference pages — what `loam instructions` prints (commands/instructions.ts)\n * and the corpus every check over loam's agent-facing prose reads\n * (test/codes-drift.test.ts, test/agent-contract.test.ts,\n * test/agent-commands-runnable.test.ts).\n */\nimport { featureIdProblem } from \"../kernel/ids/feature.js\";\nimport { serviceIdProblem } from \"../kernel/ids/service.js\";\nimport type { CommandContent, PlaceholderKind } from \"./contract.js\";\nimport { LOAM_ADOPT } from \"./workflows/adopt.js\";\nimport { LOAM_CHECK } from \"./workflows/check.js\";\nimport { LOAM_VERIFY, LOAM_SHIP } from \"./workflows/closing.js\";\nimport { LOAM_FEATURE } from \"./workflows/feature.js\";\nimport { LOAM_IMPLEMENT } from \"./workflows/implement.js\";\nimport { REFERENCES } from \"./workflows/reference/reference.js\";\nimport { LOAM_REPORT } from \"./support/report.js\";\n\n/**\n * The six protocols, in cycle order. One assembly, exported: scaffold.ts\n * derives the generated files through this same list, so what\n * `loam instructions` prints and what a fresh scaffold writes cannot drift\n * apart.\n */\nexport const COMMANDS: CommandContent[] = [\n  LOAM_ADOPT,\n  LOAM_FEATURE,\n  LOAM_IMPLEMENT,\n  LOAM_CHECK,\n  LOAM_VERIFY,\n  LOAM_SHIP,\n];\n\n/**\n * Support entry points generated beside the lifecycle, but not counted as\n * lifecycle steps. Reporting a bad run must be discoverable in every profile;\n * placing it in COMMANDS would make a consumer iterating that list try to run\n * incident collection after every feature.\n */\nexport const SUPPORT: CommandContent[] = [LOAM_REPORT];\n\n/** Every command/skill file init generates, regardless of category. */\nexport const AGENT_COMMANDS: CommandContent[] = [...COMMANDS, ...SUPPORT];\n\n/**\n * Everything `loam instructions <name>` can print: the six workflows, support\n * protocol and five reference pages, in that order.\n *\n * The pages join the generated protocols HERE and nowhere else — not in\n * {@link AGENT_COMMANDS}, which is what scaffold.ts derives `SLASH_COMMANDS`\n * and `plannedCommandFiles` from. That is the whole mechanism, and the\n * asymmetry is the point: a page is printable by name but `loam init` writes no\n * file for it, so moving 44 KB out of AGENTS.md did not put 44 KB back as four\n * new artifacts in every repository loam touches. The support protocol does\n * belong in AGENT_COMMANDS because discovery is its purpose, while its separate\n * menu category keeps it out of the lifecycle. test/agents.test.ts asserts the\n * reference-page halves separately, because a future edit can break either\n * alone.\n */\nconst PRINTABLE: CommandContent[] = [...AGENT_COMMANDS, ...REFERENCES];\n\n/**\n * The printable bodies, keyed by name — what `loam instructions <name>` prints,\n * and the corpus every check over loam's agent-facing prose reads.\n *\n * Separate from SLASH_COMMANDS since the file became a pointer: the protocol is\n * still the thing that must document every stable code (`codes-drift`) and\n * every `loam …` line it teaches must still parse against the real CLI\n * (`agent-commands-runnable`). Those two properties are about the INSTRUCTIONS,\n * and they did not move just because the delivery did.\n *\n * The reference pages belong in this record for exactly that reason. Every code\n * they carry LEFT AGENTS.md to get here, and `codes-drift` reads\n * `AGENTS_MD + PROTOCOLS` — so the guard stays green by construction, because\n * the codes moved from one half of that corpus into the other. If it goes red\n * after a change here, something was deleted rather than moved.\n */\nexport const PROTOCOLS: Record<string, string> = Object.fromEntries(\n  PRINTABLE.map((c) => [c.name, c.body]),\n);\n\n/**\n * What each page's `$1`, `$2`, … denote — see {@link CommandContent.placeholders}.\n * A reference page declares `[]`, which is not a formality: `placeholderProblems`\n * keys off this record, and a name absent from it is treated as unknown rather\n * than as taking no arguments.\n */\nexport const PLACEHOLDERS: Record<string, readonly PlaceholderKind[]> = Object.fromEntries(\n  PRINTABLE.map((c) => [c.name, c.placeholders]),\n);\n\n/**\n * Whether nothing was supplied for this position — the two shapes an absent\n * argument actually arrives in, in one place because both call sites below owe\n * the same answer.\n *\n * The first is empty; {@link protocolFor} says which dialects send that. The\n * second is the placeholder ITSELF, arriving as data. One body serves twenty\n * tool dialects (tools/registry.ts) and keeps Claude's positional `$1`/`$2`\n * convention in all of them (see {@link CommandContent}), so every generated\n * stub carries the spelling verbatim: `.gemini/commands/loam/adopt.toml`\n * contains the literal line `loam instructions loam-adopt $1`. Gemini's own\n * convention is `{{args}}` and Copilot's is `${input:…}`, and Cline, Kilo Code\n * and Roo Code substitute nothing whatever — so on those three the `$1` reaches\n * this command exactly as written, and loam refused the literal first\n * instruction of its own workflow with `invalid-option`. (Unquoted in a POSIX\n * shell the same line degrades the other way: `$1` expands to empty, and the\n * agent receives a protocol addressed to nobody.) The same class already cost\n * `loam-check` its placeholder — see the comment in workflows/check.ts; this is\n * the general fix, made once in the RECEIVING command rather than per dialect.\n *\n * Scoped to `^\\$[1-9]$` and no wider. `{{args}}` and `${input:…}` are\n * deliberately NOT matched: the tools that spell placeholders that way\n * substitute them before an agent ever reads the file, so they cannot arrive\n * here, and loam emits neither. A value that merely CONTAINS a placeholder\n * (`FEAT-$1`) is a real argument and is still checked as one.\n */\nconst unsupplied = (arg: string | undefined): boolean =>\n  arg === undefined || arg === \"\" || /^\\$[1-9]$/.test(arg);\n\n/**\n * Why the arguments given to `name` cannot be substituted into its protocol, or\n * null when they can. One sentence per bad argument, already naming the\n * placeholder it was meant to fill.\n *\n * The grammars are `core/kernel/ids/`'s, never a second copy: a value this accepts\n * and `loam adopt` refuses would be worse than no check, because the protocol\n * would still be wrong and now something had approved it. An argument nobody\n * supplied is not an error — `protocolFor` leaves that placeholder standing on\n * purpose, so the page reads as \"the service id goes here\" — and by\n * {@link unsupplied} that covers the placeholder text arriving as the argument,\n * which is what an untouched generated stub sends.\n */\nexport function placeholderProblems(name: string, args: readonly string[]): string[] | null {\n  const kinds = PLACEHOLDERS[name];\n  if (kinds === undefined) return null;\n  const problems = kinds.flatMap((kind, i) => {\n    const arg = args[i];\n    // The `undefined` arm is `unsupplied`'s own; it is repeated here because\n    // that is what narrows `arg` to a string for the id grammars below.\n    if (arg === undefined || unsupplied(arg) || kind === \"free\") return [];\n    const problem = kind === \"service\"\n      ? serviceIdProblem(arg, `$${i + 1}`)\n      : featureIdProblem(arg, `feature id ($${i + 1})`);\n    return problem === null ? [] : [problem];\n  });\n  return problems.length === 0 ? null : problems;\n}\n\n/** One row of the `loam instructions` menu: enough to choose, and nothing more. */\ntype MenuRow = Pick<CommandContent, \"name\" | \"description\" | \"argumentHint\">;\n\nconst row = ({ name, description, argumentHint }: CommandContent): MenuRow =>\n  ({ name, description, argumentHint });\n\n/** The workflow names, in cycle order — `loam instructions` with no argument lists these. */\nexport const WORKFLOWS: readonly MenuRow[] = COMMANDS.map(row);\n\n/** Support protocols, listed separately so no caller mistakes one for a lifecycle step. */\nexport const SUPPORT_PAGES: readonly MenuRow[] = SUPPORT.map(row);\n\n/**\n * The reference-page names, listed by the same bare `loam instructions` and\n * kept a SEPARATE list rather than appended to {@link WORKFLOWS}.\n *\n * A page is not a workflow: it has no steps, it is not part of the cycle, and\n * running one is not doing anything. A menu that ran the ten together would\n * read as a ten-step process, which is the one thing the six-step cycle must\n * not be confused with — so the command prints them under their own heading\n * (commands/instructions.ts) and test/instructions.test.ts pins that they stay\n * apart.\n */\nexport const REFERENCE_PAGES: readonly MenuRow[] = REFERENCES.map(row);\n\n/**\n * One workflow's protocol with `$1`, `$2`, … replaced by the arguments given.\n *\n * An unsupplied placeholder is LEFT STANDING rather than blanked: the bodies\n * are written so `$1` reads as \"the feature id goes here\", and a protocol that\n * silently dropped it would hand an agent `loam validate --feature --json` — a\n * command that parses, runs, and answers a different question. Extra arguments\n * are ignored for the same reason: this substitutes, it does not validate.\n *\n * \"Unsupplied\" is {@link unsupplied}'s two shapes, not merely a missing\n * element, and neither is pedantry — they are the two things a tool actually\n * sends. An EMPTY argument is the first: several dialects expand an absent\n * positional to the empty string, and `loam-feature`'s own invocation quotes\n * its second one (`--title \"$2\"`), so `/loam-feature FEAT-101` with no title\n * arrives here as `[\"FEAT-101\", \"\"]`. Blanking it produced\n * `loam new FEAT-101 --title \"\"` — which is exactly the failure the paragraph\n * above describes, reached by the one path that paragraph did not cover: the\n * command succeeds, and writes a feature whose title is the empty string and\n * whose intent.md opens with a bare `#`.\n *\n * The LITERAL PLACEHOLDER is the second: the dialects that substitute nothing\n * hand this command the `$1` their generated stub was written with, so\n * `loam instructions loam-adopt $1` renders the same page as\n * `loam instructions loam-adopt` — the placeholder standing, the protocol\n * printed. Here the shape mostly falls out anyway (planting `$1` where `$1`\n * stood is a no-op); it is spelled all the same, because a MISNUMBERED one\n * would not be — `$3` given for `$1` would renumber the placeholder in the\n * printed page — and because the check above and this render have to agree on\n * one definition or a value can pass one and be rewritten by the other.\n */\nexport function protocolFor(name: string, args: readonly string[] = []): string | null {\n  const body = PROTOCOLS[name];\n  if (body === undefined) return null;\n  return body.replace(/\\$([1-9])/g, (whole, digit: string) => {\n    const arg = args[Number(digit) - 1];\n    return arg === undefined || unsupplied(arg) ? whole : arg;\n  });\n}\n"]}

package/dist/core/agent/scaffold.js

@@ -53,8 +53,9 @@ import { AGENT_TOOLS, CLAUDE } from "./tools/registry.js";
  * Thinning the file is the third option. What remains is what does not move
  * between releases: what this workflow is for, and the verbs in order. What
  * leaves is everything version-shaped. `doctor.agent-files-stale` still reports
- * a file whose stamp has fallen behind, and now has almost nothing to be right
- * about — which is the point.
+ * a file whose stamp has fallen behind — once its body, stamp aside, is no
+ * longer the one this binary writes — and now has almost nothing to be right
+ * about, which is the point.
  *
  * The trade is real and worth stating: an agent that cannot execute `loam` now
  * has a spine instead of a protocol. That is the correct failure. The exact
@@ -64,12 +65,13 @@ import { AGENT_TOOLS, CLAUDE } from "./tools/registry.js";
  *
  * The last clause of the pointer is the one sentence here that changes what an
  * agent DOES rather than what it knows. `loam instructions loam-check` prints
- * 84 KB — about a fifth of a 100k-token window, 223 fix-table rows of which a
- * run needs two or three — and every file written from this stub opens by
- * telling the agent to run it. `--no-fix-tables` (commands/instructions.ts)
- * drops the rows, and `loam explain <code>` answers the one row the run turned
- * out to need in under 500 bytes. The flag is what makes the lazy path payable;
- * this sentence is what makes an agent take it.
+ * the largest page loam has — 109 KB measured 2026-10-10 (84 KB when this was
+ * first written), about a quarter of a 100k-token window, and hundreds of
+ * fix-table rows of which a run needs two or three — and every file written
+ * from this stub opens by telling the agent to run it. `--no-fix-tables`
+ * (commands/instructions.ts) drops the rows, and `loam explain <code>` answers
+ * the one row the run turned out to need on its own. The flag is what makes
+ * the lazy path payable; this sentence is what makes an agent take it.
  */
 function stubBody(c) {
     const steps = c.spine.map((s, i) => `  ${i + 1}. ${s}`).join("\n");
@@ -234,13 +236,6 @@ export async function syncAgentCommands(req) {
     }
     return out;
 }
-/**
- * Backward-compatible create-only wrapper. Callers that own no digest manifest
- * leave every existing file alone and receive only the paths created.
- */
-export async function scaffoldAgentCommands(cwd, toolIds = ["claude"], delivery = DELIVERIES) {
-    return (await syncAgentCommands({ cwd, toolIds, delivery })).created;
-}
 /**
  * The registry ids whose marker paths are present in `cwd` — what `loam init`
  * writes for when nobody passed `--tools`.

package/dist/core/agent/scaffold.js.map

@@ -1 +1 @@
-{"version":3,"file":"scaffold.js","sourceRoot":"","sources":["../../../src/core/agent/scaffold.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,aAAa,CAAC;AACzC,OAAO,EAAE,UAAU,EAAE,MAAM,SAAS,CAAC;AACrC,OAAO,EAAE,KAAK,EAAE,QAAQ,EAAE,SAAS,EAAE,MAAM,kBAAkB,CAAC;AAC9D,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,WAAW,CAAC;AACpD,OAAO,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AACpD,OAAO,EAAE,YAAY,EAAE,MAAM,wBAAwB,CAAC;AAEtD,OAAO,EAAE,cAAc,EAAE,MAAM,eAAe,CAAC;AAC/C,OAAO,EAAE,WAAW,EAAE,MAAM,EAAE,MAAM,qBAAqB,CAAC;AAE1D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsCG;AACH,SAAS,QAAQ,CAAC,CAAiB;IACjC,MAAM,KAAK,GAAG,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,KAAK,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IACnE,MAAM,KAAK,GAAG,CAAC,CAAC,IAAI,KAAK,aAAa;QACpC,CAAC,CAAC;;uEAEiE;QACnE,CAAC,CAAC;;;iDAG2C,CAAC;IAChD,MAAM,MAAM,GAAG,CAAC,CAAC,IAAI,KAAK,aAAa;QACrC,CAAC,CAAC;;uEAEiE;QACnE,CAAC,CAAC;;;;;kFAK4E,CAAC;IACjF,OAAO,GAAG,CAAC,CAAC,OAAO;;EAEnB,KAAK;;;;;;MAMD,CAAC,CAAC,UAAU;;;;EAIhB,KAAK;;EAEL,MAAM;;;;;;CAMP,CAAC;AACF,CAAC;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,OAAO,GAAG,CAAC,CAAiB,EAAkB,EAAE,CAAC,CAAC;IACtD,GAAG,CAAC;IACJ,IAAI,EAAE,GAAG,eAAe,CAAC,YAAY,CAAC,OAAO,QAAQ,CAAC,CAAC,CAAC,EAAE;CAC3D,CAAC,CAAC;AAEH;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,cAAc,GAA2B,MAAM,CAAC,WAAW,CACtE,cAAc,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,MAAM,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAC/D,CAAC;AAEF,4EAA4E;AAC5E,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,UAAU,EAAE,QAAQ,CAAU,CAAC;AAG1D,MAAM,CAAC,MAAM,cAAc,GAAG,CAAC,MAAM,EAAE,SAAS,EAAE,MAAM,CAAU,CAAC;AAGnE,MAAM,gBAAgB,GAA8C;IAClE,IAAI,EAAE,IAAI,GAAG,CAAC,cAAc,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;IAC5D,OAAO,EAAE,IAAI,GAAG,CAAC,CAAC,YAAY,EAAE,gBAAgB,EAAE,YAAY,EAAE,aAAa,EAAE,aAAa,CAAC,CAAC;IAC9F,IAAI,EAAE,IAAI,GAAG,CAAC,CAAC,cAAc,EAAE,YAAY,EAAE,WAAW,EAAE,aAAa,CAAC,CAAC;CAC1E,CAAC;AAEF;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,mBAAmB,CACjC,GAAW,EACX,OAAiB,EACjB,QAAQ,GAAwB,UAAU,EAC1C,OAAO,GAAiB,MAAM;IAE9B,OAAO,OAAO,CAAC,OAAO,CAAC,CAAC,EAAE,EAAE,EAAE;QAC5B,MAAM,IAAI,GAAG,WAAW,CAAC,EAAE,CAAC,CAAC;QAC7B,IAAI,IAAI,KAAK,SAAS;YAAE,MAAM,IAAI,KAAK,CAAC,uBAAuB,EAAE,EAAE,CAAC,CAAC;QACrE,MAAM,QAAQ,GAAuB,EAAE,CAAC;QACxC,sEAAsE;QACtE,wEAAwE;QACxE,2BAA2B;QAC3B,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,GAAG,IAAI,CAAC;QACrC,IAAI,QAAQ,CAAC,QAAQ,CAAC,UAAU,CAAC,IAAI,IAAI,KAAK,SAAS,IAAI,MAAM,KAAK,SAAS,EAAE,CAAC;YAChF,QAAQ,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,CAAC,CAAC;QAClC,CAAC;QACD,IAAI,QAAQ,CAAC,QAAQ,CAAC,QAAQ,CAAC,IAAI,KAAK,KAAK,SAAS;YAAE,QAAQ,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QAC7E,OAAO,QAAQ,CAAC,OAAO,CAAC,CAAC,CAAC,EAAE,EAAE,CAC5B,cAAc,CAAC,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,gBAAgB,CAAC,OAAO,CAAC,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;YAC1F,IAAI,EAAE,IAAI,CAAC,GAAG,EAAE,GAAG,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;YAClC,OAAO,EAAE,CAAC,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC;SAC9B,CAAC,CAAC,CACJ,CAAC;IACJ,CAAC,CAAC,CAAC;AACL,CAAC;AAED,SAAS,aAAa,CAAC,OAAwB;IAC7C,OAAO,UAAU,CAAC,QAAQ,CAAC,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;AAC5D,CAAC;AAED,SAAS,YAAY,CAAC,GAAW,EAAE,IAAY;IAC7C,OAAO,QAAQ,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC,UAAU,CAAC,IAAI,EAAE,GAAG,CAAC,CAAC;AACnD,CAAC;AAED,MAAM,UAAU,wBAAwB,CACtC,GAAW,EACX,OAAgC,EAChC,QAAsD,EACtD,OAAyC;IAEzC,MAAM,GAAG,GAAG,EAAE,GAAG,QAAQ,EAAE,CAAC;IAC5B,KAAK,MAAM,IAAI,IAAI,OAAO;QAAE,OAAO,GAAG,CAAC,YAAY,CAAC,GAAG,EAAE,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC;IACrE,OAAO,MAAM,CAAC,MAAM,CAAC,GAAG,EAAE,OAAO,CAAC,CAAC;AACrC,CAAC;AASD;;;;;GAKG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB,CAAC,GAMvC;IACC,MAAM,EAAE,GAAG,EAAE,OAAO,GAAG,CAAC,QAAQ,CAAC,EAAE,QAAQ,GAAG,UAAU,EAAE,OAAO,GAAG,MAAM,EAAE,KAAK,GAAG,EAAE,EAAE,GAAG,GAAG,CAAC;IAC/F,MAAM,GAAG,GAAkB,EAAE,OAAO,EAAE,EAAE,EAAE,SAAS,EAAE,EAAE,EAAE,OAAO,EAAE,EAAE,EAAE,CAAC;IACvE,KAAK,MAAM,EAAE,IAAI,EAAE,OAAO,EAAE,IAAI,mBAAmB,CAAC,GAAG,EAAE,OAAO,EAAE,QAAQ,EAAE,OAAO,CAAC,EAAE,CAAC;QACrF,MAAM,GAAG,GAAG,YAAY,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC;QACpC,MAAM,OAAO,GAAG,aAAa,CAAC,OAAO,CAAC,CAAC;QACvC,IAAI,CAAC,UAAU,CAAC,IAAI,CAAC,EAAE,CAAC;YACtB,MAAM,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;YAChD,MAAM,SAAS,CAAC,IAAI,EAAE,OAAO,EAAE,MAAM,CAAC,CAAC;YACvC,GAAG,CAAC,OAAO,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;YACvB,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,GAAG,OAAO,CAAC;YAC3B,SAAS;QACX,CAAC;QACD,MAAM,OAAO,GAAG,aAAa,CAAC,MAAM,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC;QACpD,IAAI,OAAO,KAAK,OAAO,EAAE,CAAC;YACxB,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,GAAG,OAAO,CAAC;YAC3B,SAAS;QACX,CAAC;QACD,IAAI,KAAK,CAAC,GAAG,CAAC,KAAK,OAAO;YAAE,SAAS;QACrC,MAAM,SAAS,CAAC,IAAI,EAAE,OAAO,EAAE,MAAM,CAAC,CAAC;QACvC,GAAG,CAAC,SAAS,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QACzB,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,GAAG,OAAO,CAAC;IAC7B,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC;AAED;;;GAGG;AACH,MAAM,CAAC,KAAK,UAAU,qBAAqB,CACzC,GAAW,EACX,OAAO,GAAa,CAAC,QAAQ,CAAC,EAC9B,QAAQ,GAAwB,UAAU;IAE1C,OAAO,CAAC,MAAM,iBAAiB,CAAC,EAAE,GAAG,EAAE,OAAO,EAAE,QAAQ,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC;AACvE,CAAC;AAED;;;;;;;;;GASG;AACH,MAAM,UAAU,gBAAgB,CAAC,GAAW;IAC1C,OAAO,MAAM,CAAC,OAAO,CAAC,WAAW,CAAC;SAC/B,MAAM,CAAC,CAAC,CAAC,EAAE,IAAI,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,UAAU,CAAC,IAAI,CAAC,GAAG,EAAE,MAAM,CAAC,CAAC,CAAC,CAAC;SACjF,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,EAAE,CAAC,CAAC;AACvB,CAAC","sourcesContent":["/**\n * The generated FILES: what a pointer file contains (the stub), what this\n * binary would write (SLASH_COMMANDS, plannedCommandFiles), and how the files\n * land and are detected on disk.\n *\n * The command and skill files go into the repo `init` runs in, because that is\n * where the agent is invoked — for whichever tools the repo shows signs of, via\n * the AGENT_TOOLS registry (tools/registry.ts): one shared body, a per-tool\n * path and wrapper. A delivery is refreshed only while its bytes still match\n * the digest loam recorded when it wrote them; a team's edits revoke that\n * authority and outrank ours.\n *\n * Two deliveries, one body. A slash command has to be TYPED, so it only ever\n * reaches an agent whose operator already knows loam exists. A skill is loaded\n * by the model itself when the task matches its `description`, which is how the\n * protocol reaches an agent that was never told about it. That difference is\n * the whole reason both are written by default.\n *\n * The per-tool command and skill files carry the same version stamp AGENTS.md\n * does (agents-md.ts), for the same reason and with the same answer:\n * `loam doctor` reports `doctor.agent-files-stale` without writing. A later\n * `loam init` can refresh only a digest-matched pointer. Without the stamp,\n * absence was the only drift doctor could see — a command file mangled to one\n * line left it saying `healthy: true`, which across a hundred repositories is\n * invisible rot with no repair path.\n */\nimport { createHash } from \"node:crypto\";\nimport { existsSync } from \"node:fs\";\nimport { mkdir, readFile, writeFile } from \"node:fs/promises\";\nimport { dirname, join, relative } from \"node:path\";\nimport { agentsStampLine } from \"./agents-stamp.js\";\nimport { LOAM_VERSION } from \"../envelope/version.js\";\nimport type { AgentFileEmitter, CommandContent } from \"./contract.js\";\nimport { AGENT_COMMANDS } from \"./protocol.js\";\nimport { AGENT_TOOLS, CLAUDE } from \"./tools/registry.js\";\n\n/**\n * What a generated file actually contains: the purpose, the spine, and the\n * command that prints the rest.\n *\n * The protocol itself stays in `body` and ships inside the binary, reachable as\n * `loam instructions <name>`. The file on disk gets a pointer to it, because\n * these two things go stale in opposite directions and only one of them can be\n * fixed. A generated file is refreshed only while its bytes still match the\n * digest loam recorded; any edit revokes that authority because your edits\n * outrank the template. Without that distinction a repo scaffolded a year ago\n * holds a year-old protocol: exact\n * flags, exact finding codes, exact step order, all of it asserted with total\n * confidence by a file whose reader has no way to know it is describing a\n * different release. That is not a hypothetical failure mode. It is the one\n * every project shipping generated agent instructions has had, and the fix\n * everybody reaches for — regenerate on upgrade — trades it for silently\n * overwriting what a human wrote.\n *\n * Thinning the file is the third option. What remains is what does not move\n * between releases: what this workflow is for, and the verbs in order. What\n * leaves is everything version-shaped. `doctor.agent-files-stale` still reports\n * a file whose stamp has fallen behind, and now has almost nothing to be right\n * about — which is the point.\n *\n * The trade is real and worth stating: an agent that cannot execute `loam` now\n * has a spine instead of a protocol. That is the correct failure. The exact\n * diagnostic and lifecycle invocations belong to the binary-owned page; an\n * agent that cannot run loam cannot finish either kind from an embedded copy —\n * it can only try using a year-old flag.\n *\n * The last clause of the pointer is the one sentence here that changes what an\n * agent DOES rather than what it knows. `loam instructions loam-check` prints\n * 84 KB — about a fifth of a 100k-token window, 223 fix-table rows of which a\n * run needs two or three — and every file written from this stub opens by\n * telling the agent to run it. `--no-fix-tables` (commands/instructions.ts)\n * drops the rows, and `loam explain <code>` answers the one row the run turned\n * out to need in under 500 bytes. The flag is what makes the lazy path payable;\n * this sentence is what makes an agent take it.\n */\nfunction stubBody(c: CommandContent): string {\n  const steps = c.spine.map((s, i) => `  ${i + 1}. ${s}`).join(\"\\n\");\n  const entry = c.name === \"loam-report\"\n    ? `This support protocol has two equivalent chat entry points: the explicit command a\nuser chooses, and the Agent Skill an unexpected-run request may load. Both reach\nthe same local, sanitized report; the agent owns the diagnostic steps.`\n    : `This workflow has two equivalent chat entry points: the explicit command a user\nchooses, and the Agent Skill a natural-language request may load. Both reach this\nsame body and must produce the same status/edit/validate loop; do not make the\nuser type the internal loam commands one by one.`;\n  const output = c.name === \"loam-report\"\n    ? `The runtime protocol decides which diagnostics are safe to run and what may enter the\nreport. Do not infer permission to retry a writer, repair files or send the result\nfrom the broader lifecycle commands another generated skill may allow.`\n    : `Every step above is a \\`loam\\` invocation, and each command's own \\`--json\\` output\ncarries what to do next: findings have stable codes, and \\`loam status --json\\` puts\nthe ordered \\`next[]\\` — each entry a code and the literal command — in one place.\nBranch on the codes, never on the prose. The check workflow starts with\n\\`--no-fix-tables\\`; use \\`loam explain <code>\\` for each code the run actually\nreports, and remove that flag only when you deliberately need the complete table.`;\n  return `${c.purpose}\n\n${entry}\n\n**Run this first.** It is the protocol, and it ships with the binary you are about\nto call — so it names this loam's flags, its finding codes and its fix tables,\nnot the ones that were current when this repository was scaffolded:\n\n    ${c.invocation}\n\nThe spine it fills in, so you can tell a run that went sideways from one that did not:\n\n${steps}\n\n${output}\n\nThis file is a pointer, not the protocol. loam may refresh it while its bytes still\nmatch the digest recorded in loam.json. Editing it revokes that authority: your\nchanges outrank the template and stay untouched. Where this file and\n\\`loam instructions\\` disagree, the command is right.\n`;\n}\n\n/**\n * The command body a file actually gets: the pointer, under the same version\n * stamp AGENTS.md carries.\n *\n * The stamp is applied once, here, rather than in twenty wrappers — it is a\n * fact about loam, not about a tool's dialect, and a per-wrapper copy is twenty\n * chances to forget it. It rides at the top of the BODY (not the file) because\n * every dialect puts something of its own first: YAML frontmatter, a TOML key,\n * a title line. An HTML comment is invisible in all of them, and\n * `agentsStampVersion` matches it wherever in the file it lands.\n *\n * A repo initialized before stamping existed has unstamped files, which is\n * exactly what `doctor.agent-files-stale` is for: nobody has confirmed that\n * those instructions still describe this binary.\n */\nconst stubbed = (c: CommandContent): CommandContent => ({\n  ...c,\n  body: `${agentsStampLine(LOAM_VERSION)}\\n\\n${stubBody(c)}`,\n});\n\n/**\n * The Claude-format files, keyed by command name: exactly what **this** binary\n * would write, derived through the same adapter that writes them, so the export\n * and a freshly scaffolded repo can never disagree.\n *\n * Read that scope literally. It used to be described as the on-disk contract of\n * every repo initialized before `--tools` existed, and that is no longer true\n * of anything but a fresh scaffold: a file holds the STUB now, every repo\n * scaffolded before that holds the full protocol. A recorded, byte-identical\n * pointer can refresh; an older unrecorded file or any customized file cannot,\n * so an export cannot describe files this binary did not write.\n *\n * The protocol those older files carry is `PROTOCOLS`. Anything asserting on\n * protocol content wants that one — this answers \"what would loam write here\",\n * not \"what does loam instruct\".\n */\nexport const SLASH_COMMANDS: Record<string, string> = Object.fromEntries(\n  AGENT_COMMANDS.map((c) => [c.name, CLAUDE.format(stubbed(c))]),\n);\n\n/** The two ways a command body reaches an agent. Both are on by default. */\nexport const DELIVERIES = [\"commands\", \"skills\"] as const;\nexport type Delivery = (typeof DELIVERIES)[number];\n\nexport const AGENT_PROFILES = [\"full\", \"service\", \"docs\"] as const;\nexport type AgentProfile = (typeof AGENT_PROFILES)[number];\n\nconst PROFILE_COMMANDS: Record<AgentProfile, ReadonlySet<string>> = {\n  full: new Set(AGENT_COMMANDS.map((command) => command.name)),\n  service: new Set([\"loam-adopt\", \"loam-implement\", \"loam-check\", \"loam-verify\", \"loam-report\"]),\n  docs: new Set([\"loam-feature\", \"loam-check\", \"loam-ship\", \"loam-report\"]),\n};\n\n/**\n * Every file the selected tools would lay down, in creation order — the same\n * list `init` probes for `skipped` BEFORE the scaffold runs, so created +\n * skipped is the same list on every repo.\n *\n * Called with two arguments it returns EVERYTHING the binary would write under\n * default delivery: commands and skills both. That is the contract callers\n * outside this module depend on — `loam doctor` asks \"what should be here?\"\n * and a half-answer would report a fully-scaffolded repo as fully scaffolded\n * while ignoring every skill file. The name predates the second delivery and is\n * kept because it is imported elsewhere; `delivery` narrows it.\n */\nexport function plannedCommandFiles(\n  cwd: string,\n  toolIds: string[],\n  delivery: readonly Delivery[] = DELIVERIES,\n  profile: AgentProfile = \"full\",\n): Array<{ path: string; content: string }> {\n  return toolIds.flatMap((id) => {\n    const tool = AGENT_TOOLS[id];\n    if (tool === undefined) throw new Error(`unknown agent tool: ${id}`);\n    const emitters: AgentFileEmitter[] = [];\n    // A tool declares only the deliveries it actually reads, so an absent\n    // emitter is a fact about the tool, never a reason to fall back to some\n    // other tool's convention.\n    const { path, format, skill } = tool;\n    if (delivery.includes(\"commands\") && path !== undefined && format !== undefined) {\n      emitters.push({ path, format });\n    }\n    if (delivery.includes(\"skills\") && skill !== undefined) emitters.push(skill);\n    return emitters.flatMap((e) =>\n      AGENT_COMMANDS.filter((command) => PROFILE_COMMANDS[profile].has(command.name)).map((c) => ({\n        path: join(cwd, ...e.path(c.name)),\n        content: e.format(stubbed(c)),\n      })),\n    );\n  });\n}\n\nfunction contentDigest(content: string | Buffer): string {\n  return createHash(\"sha256\").update(content).digest(\"hex\");\n}\n\nfunction manifestPath(cwd: string, path: string): string {\n  return relative(cwd, path).replaceAll(\"\\\\\", \"/\");\n}\n\nexport function updatedAgentFileManifest(\n  cwd: string,\n  planned: Array<{ path: string }>,\n  existing: Readonly<Record<string, string>> | undefined,\n  managed: Readonly<Record<string, string>>,\n): Record<string, string> {\n  const out = { ...existing };\n  for (const file of planned) delete out[manifestPath(cwd, file.path)];\n  return Object.assign(out, managed);\n}\n\nexport interface AgentFileSync {\n  created: string[];\n  refreshed: string[];\n  /** Repo-relative path -> digest of the bytes loam is allowed to refresh. */\n  managed: Record<string, string>;\n}\n\n/**\n * Create missing files and refresh only files still byte-identical to the\n * digest recorded when loam last wrote them. A human edit breaks that equality\n * and therefore revokes loam's authority over the file without a marker block\n * or a prompt.\n */\nexport async function syncAgentCommands(req: {\n  cwd: string;\n  toolIds?: string[];\n  delivery?: readonly Delivery[];\n  profile?: AgentProfile;\n  known?: Readonly<Record<string, string>>;\n}): Promise<AgentFileSync> {\n  const { cwd, toolIds = [\"claude\"], delivery = DELIVERIES, profile = \"full\", known = {} } = req;\n  const out: AgentFileSync = { created: [], refreshed: [], managed: {} };\n  for (const { path, content } of plannedCommandFiles(cwd, toolIds, delivery, profile)) {\n    const key = manifestPath(cwd, path);\n    const desired = contentDigest(content);\n    if (!existsSync(path)) {\n      await mkdir(dirname(path), { recursive: true });\n      await writeFile(path, content, \"utf8\");\n      out.created.push(path);\n      out.managed[key] = desired;\n      continue;\n    }\n    const current = contentDigest(await readFile(path));\n    if (current === desired) {\n      out.managed[key] = desired;\n      continue;\n    }\n    if (known[key] !== current) continue;\n    await writeFile(path, content, \"utf8\");\n    out.refreshed.push(path);\n    out.managed[key] = desired;\n  }\n  return out;\n}\n\n/**\n * Backward-compatible create-only wrapper. Callers that own no digest manifest\n * leave every existing file alone and receive only the paths created.\n */\nexport async function scaffoldAgentCommands(\n  cwd: string,\n  toolIds: string[] = [\"claude\"],\n  delivery: readonly Delivery[] = DELIVERIES,\n): Promise<string[]> {\n  return (await syncAgentCommands({ cwd, toolIds, delivery })).created;\n}\n\n/**\n * The registry ids whose marker paths are present in `cwd` — what `loam init`\n * writes for when nobody passed `--tools`.\n *\n * A repo with `.cursor/` and no Claude Code used to get `.claude/commands/`\n * and nothing it could actually run. Presence is the whole test, and existence\n * (not directory-ness) is what is asked, because a marker is as often a file as\n * a directory — `.github/copilot-instructions.md` is the honest signal for\n * Copilot where `.github/` itself is noise.\n */\nexport function detectAgentTools(cwd: string): string[] {\n  return Object.entries(AGENT_TOOLS)\n    .filter(([, tool]) => tool.detect.some((marker) => existsSync(join(cwd, marker))))\n    .map(([id]) => id);\n}\n"]}
+{"version":3,"file":"scaffold.js","sourceRoot":"","sources":["../../../src/core/agent/scaffold.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,aAAa,CAAC;AACzC,OAAO,EAAE,UAAU,EAAE,MAAM,SAAS,CAAC;AACrC,OAAO,EAAE,KAAK,EAAE,QAAQ,EAAE,SAAS,EAAE,MAAM,kBAAkB,CAAC;AAC9D,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,WAAW,CAAC;AACpD,OAAO,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AACpD,OAAO,EAAE,YAAY,EAAE,MAAM,wBAAwB,CAAC;AAEtD,OAAO,EAAE,cAAc,EAAE,MAAM,eAAe,CAAC;AAC/C,OAAO,EAAE,WAAW,EAAE,MAAM,EAAE,MAAM,qBAAqB,CAAC;AAE1D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwCG;AACH,SAAS,QAAQ,CAAC,CAAiB;IACjC,MAAM,KAAK,GAAG,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,KAAK,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IACnE,MAAM,KAAK,GAAG,CAAC,CAAC,IAAI,KAAK,aAAa;QACpC,CAAC,CAAC;;uEAEiE;QACnE,CAAC,CAAC;;;iDAG2C,CAAC;IAChD,MAAM,MAAM,GAAG,CAAC,CAAC,IAAI,KAAK,aAAa;QACrC,CAAC,CAAC;;uEAEiE;QACnE,CAAC,CAAC;;;;;kFAK4E,CAAC;IACjF,OAAO,GAAG,CAAC,CAAC,OAAO;;EAEnB,KAAK;;;;;;MAMD,CAAC,CAAC,UAAU;;;;EAIhB,KAAK;;EAEL,MAAM;;;;;;CAMP,CAAC;AACF,CAAC;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,OAAO,GAAG,CAAC,CAAiB,EAAkB,EAAE,CAAC,CAAC;IACtD,GAAG,CAAC;IACJ,IAAI,EAAE,GAAG,eAAe,CAAC,YAAY,CAAC,OAAO,QAAQ,CAAC,CAAC,CAAC,EAAE;CAC3D,CAAC,CAAC;AAEH;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,cAAc,GAA2B,MAAM,CAAC,WAAW,CACtE,cAAc,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,MAAM,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAC/D,CAAC;AAEF,4EAA4E;AAC5E,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,UAAU,EAAE,QAAQ,CAAU,CAAC;AAG1D,MAAM,CAAC,MAAM,cAAc,GAAG,CAAC,MAAM,EAAE,SAAS,EAAE,MAAM,CAAU,CAAC;AAGnE,MAAM,gBAAgB,GAA8C;IAClE,IAAI,EAAE,IAAI,GAAG,CAAC,cAAc,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;IAC5D,OAAO,EAAE,IAAI,GAAG,CAAC,CAAC,YAAY,EAAE,gBAAgB,EAAE,YAAY,EAAE,aAAa,EAAE,aAAa,CAAC,CAAC;IAC9F,IAAI,EAAE,IAAI,GAAG,CAAC,CAAC,cAAc,EAAE,YAAY,EAAE,WAAW,EAAE,aAAa,CAAC,CAAC;CAC1E,CAAC;AAEF;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,mBAAmB,CACjC,GAAW,EACX,OAAiB,EACjB,QAAQ,GAAwB,UAAU,EAC1C,OAAO,GAAiB,MAAM;IAE9B,OAAO,OAAO,CAAC,OAAO,CAAC,CAAC,EAAE,EAAE,EAAE;QAC5B,MAAM,IAAI,GAAG,WAAW,CAAC,EAAE,CAAC,CAAC;QAC7B,IAAI,IAAI,KAAK,SAAS;YAAE,MAAM,IAAI,KAAK,CAAC,uBAAuB,EAAE,EAAE,CAAC,CAAC;QACrE,MAAM,QAAQ,GAAuB,EAAE,CAAC;QACxC,sEAAsE;QACtE,wEAAwE;QACxE,2BAA2B;QAC3B,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,GAAG,IAAI,CAAC;QACrC,IAAI,QAAQ,CAAC,QAAQ,CAAC,UAAU,CAAC,IAAI,IAAI,KAAK,SAAS,IAAI,MAAM,KAAK,SAAS,EAAE,CAAC;YAChF,QAAQ,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,CAAC,CAAC;QAClC,CAAC;QACD,IAAI,QAAQ,CAAC,QAAQ,CAAC,QAAQ,CAAC,IAAI,KAAK,KAAK,SAAS;YAAE,QAAQ,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QAC7E,OAAO,QAAQ,CAAC,OAAO,CAAC,CAAC,CAAC,EAAE,EAAE,CAC5B,cAAc,CAAC,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,gBAAgB,CAAC,OAAO,CAAC,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;YAC1F,IAAI,EAAE,IAAI,CAAC,GAAG,EAAE,GAAG,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;YAClC,OAAO,EAAE,CAAC,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC;SAC9B,CAAC,CAAC,CACJ,CAAC;IACJ,CAAC,CAAC,CAAC;AACL,CAAC;AAED,SAAS,aAAa,CAAC,OAAwB;IAC7C,OAAO,UAAU,CAAC,QAAQ,CAAC,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;AAC5D,CAAC;AAED,SAAS,YAAY,CAAC,GAAW,EAAE,IAAY;IAC7C,OAAO,QAAQ,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC,UAAU,CAAC,IAAI,EAAE,GAAG,CAAC,CAAC;AACnD,CAAC;AAED,MAAM,UAAU,wBAAwB,CACtC,GAAW,EACX,OAAgC,EAChC,QAAsD,EACtD,OAAyC;IAEzC,MAAM,GAAG,GAAG,EAAE,GAAG,QAAQ,EAAE,CAAC;IAC5B,KAAK,MAAM,IAAI,IAAI,OAAO;QAAE,OAAO,GAAG,CAAC,YAAY,CAAC,GAAG,EAAE,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC;IACrE,OAAO,MAAM,CAAC,MAAM,CAAC,GAAG,EAAE,OAAO,CAAC,CAAC;AACrC,CAAC;AASD;;;;;GAKG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB,CAAC,GAMvC;IACC,MAAM,EAAE,GAAG,EAAE,OAAO,GAAG,CAAC,QAAQ,CAAC,EAAE,QAAQ,GAAG,UAAU,EAAE,OAAO,GAAG,MAAM,EAAE,KAAK,GAAG,EAAE,EAAE,GAAG,GAAG,CAAC;IAC/F,MAAM,GAAG,GAAkB,EAAE,OAAO,EAAE,EAAE,EAAE,SAAS,EAAE,EAAE,EAAE,OAAO,EAAE,EAAE,EAAE,CAAC;IACvE,KAAK,MAAM,EAAE,IAAI,EAAE,OAAO,EAAE,IAAI,mBAAmB,CAAC,GAAG,EAAE,OAAO,EAAE,QAAQ,EAAE,OAAO,CAAC,EAAE,CAAC;QACrF,MAAM,GAAG,GAAG,YAAY,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC;QACpC,MAAM,OAAO,GAAG,aAAa,CAAC,OAAO,CAAC,CAAC;QACvC,IAAI,CAAC,UAAU,CAAC,IAAI,CAAC,EAAE,CAAC;YACtB,MAAM,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;YAChD,MAAM,SAAS,CAAC,IAAI,EAAE,OAAO,EAAE,MAAM,CAAC,CAAC;YACvC,GAAG,CAAC,OAAO,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;YACvB,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,GAAG,OAAO,CAAC;YAC3B,SAAS;QACX,CAAC;QACD,MAAM,OAAO,GAAG,aAAa,CAAC,MAAM,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC;QACpD,IAAI,OAAO,KAAK,OAAO,EAAE,CAAC;YACxB,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,GAAG,OAAO,CAAC;YAC3B,SAAS;QACX,CAAC;QACD,IAAI,KAAK,CAAC,GAAG,CAAC,KAAK,OAAO;YAAE,SAAS;QACrC,MAAM,SAAS,CAAC,IAAI,EAAE,OAAO,EAAE,MAAM,CAAC,CAAC;QACvC,GAAG,CAAC,SAAS,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QACzB,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,GAAG,OAAO,CAAC;IAC7B,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC;AAED;;;;;;;;;GASG;AACH,MAAM,UAAU,gBAAgB,CAAC,GAAW;IAC1C,OAAO,MAAM,CAAC,OAAO,CAAC,WAAW,CAAC;SAC/B,MAAM,CAAC,CAAC,CAAC,EAAE,IAAI,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,UAAU,CAAC,IAAI,CAAC,GAAG,EAAE,MAAM,CAAC,CAAC,CAAC,CAAC;SACjF,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,EAAE,CAAC,CAAC;AACvB,CAAC","sourcesContent":["/**\n * The generated FILES: what a pointer file contains (the stub), what this\n * binary would write (SLASH_COMMANDS, plannedCommandFiles), and how the files\n * land and are detected on disk.\n *\n * The command and skill files go into the repo `init` runs in, because that is\n * where the agent is invoked — for whichever tools the repo shows signs of, via\n * the AGENT_TOOLS registry (tools/registry.ts): one shared body, a per-tool\n * path and wrapper. A delivery is refreshed only while its bytes still match\n * the digest loam recorded when it wrote them; a team's edits revoke that\n * authority and outrank ours.\n *\n * Two deliveries, one body. A slash command has to be TYPED, so it only ever\n * reaches an agent whose operator already knows loam exists. A skill is loaded\n * by the model itself when the task matches its `description`, which is how the\n * protocol reaches an agent that was never told about it. That difference is\n * the whole reason both are written by default.\n *\n * The per-tool command and skill files carry the same version stamp AGENTS.md\n * does (agents-md.ts), for the same reason and with the same answer:\n * `loam doctor` reports `doctor.agent-files-stale` without writing. A later\n * `loam init` can refresh only a digest-matched pointer. Without the stamp,\n * absence was the only drift doctor could see — a command file mangled to one\n * line left it saying `healthy: true`, which across a hundred repositories is\n * invisible rot with no repair path.\n */\nimport { createHash } from \"node:crypto\";\nimport { existsSync } from \"node:fs\";\nimport { mkdir, readFile, writeFile } from \"node:fs/promises\";\nimport { dirname, join, relative } from \"node:path\";\nimport { agentsStampLine } from \"./agents-stamp.js\";\nimport { LOAM_VERSION } from \"../envelope/version.js\";\nimport type { AgentFileEmitter, CommandContent } from \"./contract.js\";\nimport { AGENT_COMMANDS } from \"./protocol.js\";\nimport { AGENT_TOOLS, CLAUDE } from \"./tools/registry.js\";\n\n/**\n * What a generated file actually contains: the purpose, the spine, and the\n * command that prints the rest.\n *\n * The protocol itself stays in `body` and ships inside the binary, reachable as\n * `loam instructions <name>`. The file on disk gets a pointer to it, because\n * these two things go stale in opposite directions and only one of them can be\n * fixed. A generated file is refreshed only while its bytes still match the\n * digest loam recorded; any edit revokes that authority because your edits\n * outrank the template. Without that distinction a repo scaffolded a year ago\n * holds a year-old protocol: exact\n * flags, exact finding codes, exact step order, all of it asserted with total\n * confidence by a file whose reader has no way to know it is describing a\n * different release. That is not a hypothetical failure mode. It is the one\n * every project shipping generated agent instructions has had, and the fix\n * everybody reaches for — regenerate on upgrade — trades it for silently\n * overwriting what a human wrote.\n *\n * Thinning the file is the third option. What remains is what does not move\n * between releases: what this workflow is for, and the verbs in order. What\n * leaves is everything version-shaped. `doctor.agent-files-stale` still reports\n * a file whose stamp has fallen behind — once its body, stamp aside, is no\n * longer the one this binary writes — and now has almost nothing to be right\n * about, which is the point.\n *\n * The trade is real and worth stating: an agent that cannot execute `loam` now\n * has a spine instead of a protocol. That is the correct failure. The exact\n * diagnostic and lifecycle invocations belong to the binary-owned page; an\n * agent that cannot run loam cannot finish either kind from an embedded copy —\n * it can only try using a year-old flag.\n *\n * The last clause of the pointer is the one sentence here that changes what an\n * agent DOES rather than what it knows. `loam instructions loam-check` prints\n * the largest page loam has — 109 KB measured 2026-10-10 (84 KB when this was\n * first written), about a quarter of a 100k-token window, and hundreds of\n * fix-table rows of which a run needs two or three — and every file written\n * from this stub opens by telling the agent to run it. `--no-fix-tables`\n * (commands/instructions.ts) drops the rows, and `loam explain <code>` answers\n * the one row the run turned out to need on its own. The flag is what makes\n * the lazy path payable; this sentence is what makes an agent take it.\n */\nfunction stubBody(c: CommandContent): string {\n  const steps = c.spine.map((s, i) => `  ${i + 1}. ${s}`).join(\"\\n\");\n  const entry = c.name === \"loam-report\"\n    ? `This support protocol has two equivalent chat entry points: the explicit command a\nuser chooses, and the Agent Skill an unexpected-run request may load. Both reach\nthe same local, sanitized report; the agent owns the diagnostic steps.`\n    : `This workflow has two equivalent chat entry points: the explicit command a user\nchooses, and the Agent Skill a natural-language request may load. Both reach this\nsame body and must produce the same status/edit/validate loop; do not make the\nuser type the internal loam commands one by one.`;\n  const output = c.name === \"loam-report\"\n    ? `The runtime protocol decides which diagnostics are safe to run and what may enter the\nreport. Do not infer permission to retry a writer, repair files or send the result\nfrom the broader lifecycle commands another generated skill may allow.`\n    : `Every step above is a \\`loam\\` invocation, and each command's own \\`--json\\` output\ncarries what to do next: findings have stable codes, and \\`loam status --json\\` puts\nthe ordered \\`next[]\\` — each entry a code and the literal command — in one place.\nBranch on the codes, never on the prose. The check workflow starts with\n\\`--no-fix-tables\\`; use \\`loam explain <code>\\` for each code the run actually\nreports, and remove that flag only when you deliberately need the complete table.`;\n  return `${c.purpose}\n\n${entry}\n\n**Run this first.** It is the protocol, and it ships with the binary you are about\nto call — so it names this loam's flags, its finding codes and its fix tables,\nnot the ones that were current when this repository was scaffolded:\n\n    ${c.invocation}\n\nThe spine it fills in, so you can tell a run that went sideways from one that did not:\n\n${steps}\n\n${output}\n\nThis file is a pointer, not the protocol. loam may refresh it while its bytes still\nmatch the digest recorded in loam.json. Editing it revokes that authority: your\nchanges outrank the template and stay untouched. Where this file and\n\\`loam instructions\\` disagree, the command is right.\n`;\n}\n\n/**\n * The command body a file actually gets: the pointer, under the same version\n * stamp AGENTS.md carries.\n *\n * The stamp is applied once, here, rather than in twenty wrappers — it is a\n * fact about loam, not about a tool's dialect, and a per-wrapper copy is twenty\n * chances to forget it. It rides at the top of the BODY (not the file) because\n * every dialect puts something of its own first: YAML frontmatter, a TOML key,\n * a title line. An HTML comment is invisible in all of them, and\n * `agentsStampVersion` matches it wherever in the file it lands.\n *\n * A repo initialized before stamping existed has unstamped files, which is\n * exactly what `doctor.agent-files-stale` is for: nobody has confirmed that\n * those instructions still describe this binary.\n */\nconst stubbed = (c: CommandContent): CommandContent => ({\n  ...c,\n  body: `${agentsStampLine(LOAM_VERSION)}\\n\\n${stubBody(c)}`,\n});\n\n/**\n * The Claude-format files, keyed by command name: exactly what **this** binary\n * would write, derived through the same adapter that writes them, so the export\n * and a freshly scaffolded repo can never disagree.\n *\n * Read that scope literally. It used to be described as the on-disk contract of\n * every repo initialized before `--tools` existed, and that is no longer true\n * of anything but a fresh scaffold: a file holds the STUB now, every repo\n * scaffolded before that holds the full protocol. A recorded, byte-identical\n * pointer can refresh; an older unrecorded file or any customized file cannot,\n * so an export cannot describe files this binary did not write.\n *\n * The protocol those older files carry is `PROTOCOLS`. Anything asserting on\n * protocol content wants that one — this answers \"what would loam write here\",\n * not \"what does loam instruct\".\n */\nexport const SLASH_COMMANDS: Record<string, string> = Object.fromEntries(\n  AGENT_COMMANDS.map((c) => [c.name, CLAUDE.format(stubbed(c))]),\n);\n\n/** The two ways a command body reaches an agent. Both are on by default. */\nexport const DELIVERIES = [\"commands\", \"skills\"] as const;\nexport type Delivery = (typeof DELIVERIES)[number];\n\nexport const AGENT_PROFILES = [\"full\", \"service\", \"docs\"] as const;\nexport type AgentProfile = (typeof AGENT_PROFILES)[number];\n\nconst PROFILE_COMMANDS: Record<AgentProfile, ReadonlySet<string>> = {\n  full: new Set(AGENT_COMMANDS.map((command) => command.name)),\n  service: new Set([\"loam-adopt\", \"loam-implement\", \"loam-check\", \"loam-verify\", \"loam-report\"]),\n  docs: new Set([\"loam-feature\", \"loam-check\", \"loam-ship\", \"loam-report\"]),\n};\n\n/**\n * Every file the selected tools would lay down, in creation order — the same\n * list `init` probes for `skipped` BEFORE the scaffold runs, so created +\n * skipped is the same list on every repo.\n *\n * Called with two arguments it returns EVERYTHING the binary would write under\n * default delivery: commands and skills both. That is the contract callers\n * outside this module depend on — `loam doctor` asks \"what should be here?\"\n * and a half-answer would report a fully-scaffolded repo as fully scaffolded\n * while ignoring every skill file. The name predates the second delivery and is\n * kept because it is imported elsewhere; `delivery` narrows it.\n */\nexport function plannedCommandFiles(\n  cwd: string,\n  toolIds: string[],\n  delivery: readonly Delivery[] = DELIVERIES,\n  profile: AgentProfile = \"full\",\n): Array<{ path: string; content: string }> {\n  return toolIds.flatMap((id) => {\n    const tool = AGENT_TOOLS[id];\n    if (tool === undefined) throw new Error(`unknown agent tool: ${id}`);\n    const emitters: AgentFileEmitter[] = [];\n    // A tool declares only the deliveries it actually reads, so an absent\n    // emitter is a fact about the tool, never a reason to fall back to some\n    // other tool's convention.\n    const { path, format, skill } = tool;\n    if (delivery.includes(\"commands\") && path !== undefined && format !== undefined) {\n      emitters.push({ path, format });\n    }\n    if (delivery.includes(\"skills\") && skill !== undefined) emitters.push(skill);\n    return emitters.flatMap((e) =>\n      AGENT_COMMANDS.filter((command) => PROFILE_COMMANDS[profile].has(command.name)).map((c) => ({\n        path: join(cwd, ...e.path(c.name)),\n        content: e.format(stubbed(c)),\n      })),\n    );\n  });\n}\n\nfunction contentDigest(content: string | Buffer): string {\n  return createHash(\"sha256\").update(content).digest(\"hex\");\n}\n\nfunction manifestPath(cwd: string, path: string): string {\n  return relative(cwd, path).replaceAll(\"\\\\\", \"/\");\n}\n\nexport function updatedAgentFileManifest(\n  cwd: string,\n  planned: Array<{ path: string }>,\n  existing: Readonly<Record<string, string>> | undefined,\n  managed: Readonly<Record<string, string>>,\n): Record<string, string> {\n  const out = { ...existing };\n  for (const file of planned) delete out[manifestPath(cwd, file.path)];\n  return Object.assign(out, managed);\n}\n\nexport interface AgentFileSync {\n  created: string[];\n  refreshed: string[];\n  /** Repo-relative path -> digest of the bytes loam is allowed to refresh. */\n  managed: Record<string, string>;\n}\n\n/**\n * Create missing files and refresh only files still byte-identical to the\n * digest recorded when loam last wrote them. A human edit breaks that equality\n * and therefore revokes loam's authority over the file without a marker block\n * or a prompt.\n */\nexport async function syncAgentCommands(req: {\n  cwd: string;\n  toolIds?: string[];\n  delivery?: readonly Delivery[];\n  profile?: AgentProfile;\n  known?: Readonly<Record<string, string>>;\n}): Promise<AgentFileSync> {\n  const { cwd, toolIds = [\"claude\"], delivery = DELIVERIES, profile = \"full\", known = {} } = req;\n  const out: AgentFileSync = { created: [], refreshed: [], managed: {} };\n  for (const { path, content } of plannedCommandFiles(cwd, toolIds, delivery, profile)) {\n    const key = manifestPath(cwd, path);\n    const desired = contentDigest(content);\n    if (!existsSync(path)) {\n      await mkdir(dirname(path), { recursive: true });\n      await writeFile(path, content, \"utf8\");\n      out.created.push(path);\n      out.managed[key] = desired;\n      continue;\n    }\n    const current = contentDigest(await readFile(path));\n    if (current === desired) {\n      out.managed[key] = desired;\n      continue;\n    }\n    if (known[key] !== current) continue;\n    await writeFile(path, content, \"utf8\");\n    out.refreshed.push(path);\n    out.managed[key] = desired;\n  }\n  return out;\n}\n\n/**\n * The registry ids whose marker paths are present in `cwd` — what `loam init`\n * writes for when nobody passed `--tools`.\n *\n * A repo with `.cursor/` and no Claude Code used to get `.claude/commands/`\n * and nothing it could actually run. Presence is the whole test, and existence\n * (not directory-ness) is what is asked, because a marker is as often a file as\n * a directory — `.github/copilot-instructions.md` is the honest signal for\n * Copilot where `.github/` itself is noise.\n */\nexport function detectAgentTools(cwd: string): string[] {\n  return Object.entries(AGENT_TOOLS)\n    .filter(([, tool]) => tool.detect.some((marker) => existsSync(join(cwd, marker))))\n    .map(([id]) => id);\n}\n"]}

package/dist/core/agent/support/report.js

@@ -61,13 +61,40 @@ prefer repository-relative paths. Do not copy source files, architecture/spec bo
 command output when a code and short excerpt prove the same fact. Review the finished report once
 more for secrets before handing it back.
 
+The fleet's own names are often confidential too: its services, topics, messages, operation ids and
+requirement ids. Write \`Minimal safe reproduction\` on neutral stand-ins — an order service, a
+payment service, a broker topic, a store — rebuilt until it shows the same finding or refusal, so the
+report can travel without the fleet. Where the excerpt under \`Actual\` must quote the fleet's own
+output, say in \`Sanitization\` that it does, so that whoever forwards the report knows that
+section stays behind.
+
 ## Write one separate report
 
-Create \`loam-reports/YYYY-MM-DD-<short-slug>.md\` at the current repository root. Use a short neutral
-slug based on the symptom, not a customer, person or secret. Never overwrite a different incident;
-add a numeric suffix when the path exists. Reports are ordinary project files so the team can
-review or commit them deliberately, but do not upload, submit an issue, send telemetry, or contact
-any service automatically.
+Create \`loam-reports/NNN-YYYY-MM-DD-<short-slug>.md\` in the directory holding the \`loam.json\` that
+resolved — or, when a \`loam.json\` was found but does not parse, beside that file, so a report about
+the broken config joins the corpus already there; only when there is no config file at or above you
+is it the directory you run in.
+\`loam doctor --json\` hands you that whole directory — that root WITH \`loam-reports/\`
+already on the end — as \`reports.dir\`: write inside the path it gives, never joined onto
+\`loam-reports/\` a second time. \`NNN\` is an ordinal of at least three digits, zero-padded, one more
+than the highest already in that directory — read \`reports.next\` from the same output, which says
+\`001\` when the directory is empty or absent, and widens past three digits rather than reusing a
+number once the corpus gets there. Use a short neutral slug based on the symptom, not a customer,
+person or secret. Never
+overwrite a different incident: a path that already exists means a concurrent report claimed that
+ordinal, so take the next one rather than adding a suffix. That check is on the PATH, and the
+promise is about the ordinal, so re-run \`loam doctor --json\` after writing: if two entries carry
+the same \`ordinal\`, the one with the later \`Recorded\` timestamp renames itself to the next free
+number. The ordinal is the report's handle —
+cite one by its number in a commit message, an issue, or another report's cross-references, and
+never by filename, which is free to be renamed. The ordinal is unique within that directory, not
+across a fleet: a service repository and the docs repository each number their own, so when two
+repositories are in play cite \`<repo>/loam-reports/NNN\`.
+
+Reports are ordinary project files so the team can review or commit them deliberately, but
+do not upload, submit an issue, send telemetry, or contact any service automatically.
+\`loam doctor\` reads the directory — how many reports it holds, how many are in each status, and
+which ordinal comes next — and that is a local read of local files: nothing is transmitted.
 
 Use this shape, omitting only fields that truly cannot be known and marking them \`not collected\`:
 
@@ -75,6 +102,7 @@ Use this shape, omitting only fields that truly cannot be known and marking them
 
     - Recorded: <ISO-8601 timestamp>
     - Classification: <one value above>
+    - Status: open
     - Repository role: <docs | service | combined | unresolved>
     - loam version: <version>
     - Entry point: <chat command, skill, or CLI command; sanitized>
@@ -91,6 +119,19 @@ Use this shape, omitting only fields that truly cannot be known and marking them
     ## Missing evidence
     ## Sanitization
 
+\`Status\` is written as \`open\` and stays the report's own record of where it got to. The vocabulary
+is \`open\`, \`sent\` (handed to loam's author — the person forwarding a report sets this, never the
+agent writing it), \`fixed in <version>\`, and \`superseded by <NNN>\` naming the report that
+replaced this one. Close a report by editing its own \`Status\` line: there is no index to keep in
+step, and \`loam doctor\` counts the directory by reading that line's first word, so
+\`fixed in 0.2.0-alpha.5\` counts as fixed. It reads that line from the HEADER FIELD BLOCK only —
+the lines above the first \`##\` heading, quoted code skipped in either markdown spelling: a fence
+(closed only by a run of the same character at least as long as the one that opened it, so a
+\`\`\` inside a \`\`\`\` block is content) and an indented block, which is the shape THIS template is
+printed in above. So a report that quotes this template, however it quotes it, still counts as
+whatever its own header says. A report written before this
+field existed has no \`Status\` line and counts as unstated.
+
 In \`Machine contract\`, include exit code plus the stable envelope fields and relevant finding
 codes/locations; do not paste an entire large JSON payload. In \`Sanitization\`, list the kinds of
 values removed without revealing them. If no workaround is known, say so rather than inventing one.

package/dist/core/agent/support/report.js.map

@@ -1 +1 @@
-{"version":3,"file":"report.js","sourceRoot":"","sources":["../../../../src/core/agent/support/report.ts"],"names":[],"mappings":"AAEA;;;;GAIG;AACH,MAAM,CAAC,MAAM,WAAW,GAAmB;IACzC,IAAI,EAAE,aAAa;IACnB,WAAW,EACT,uFAAuF;IACzF,YAAY,EAAE,EAAE;IAChB,OAAO,EACL,oOAAoO;IACtO,UAAU,EAAE,+BAA+B;IAC3C,YAAY,EAAE,EAAE;IAChB,KAAK,EAAE;QACL,+EAA+E;QAC/E,iFAAiF;QACjF,yFAAyF;QACzF,gFAAgF;QAChF,wFAAwF;KACzF;IACD,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiFP;CACA,CAAC","sourcesContent":["import type { CommandContent } from \"../contract.js\";\n\n/**\n * The incident-reporting protocol: preserve a small, sanitized reproducer when\n * loam or its agent integration behaves unexpectedly, without turning loam\n * into a telemetry service or retrying a risky write.\n */\nexport const LOAM_REPORT: CommandContent = {\n  name: \"loam-report\",\n  description:\n    \"Record unexpected loam or agent behavior as a sanitized, reproducible Markdown report\",\n  argumentHint: \"\",\n  purpose:\n    \"Collect one unexpected loam or agent-integration incident into a separate, reviewable Markdown file. This is local diagnostics only: redact secrets, never upload automatically, and never repeat a writer merely to reproduce it.\",\n  invocation: \"loam instructions loam-report\",\n  placeholders: [],\n  spine: [\n    \"preserve the user's original symptom and expected result before investigating\",\n    \"collect the binary version, wiring diagnosis and the smallest safe reproduction\",\n    \"classify the failure without repairing, retrying a writer or changing project documents\",\n    \"sanitize commands, paths and output, then write one report under loam-reports/\",\n    \"hand back the report path, classification and any evidence that could not be collected\",\n  ],\n  body: `Record one incident where loam, a generated command/skill, or the agent following it\nbehaved unexpectedly. The result is a local diagnostic document, not a repair and not telemetry.\nDo not change architecture/spec files while collecting it.\n\n## Preserve the symptom first\n\nBefore running anything, write down the user's original request, what they expected, what actually\nhappened, the command or chat entry point involved, and whether any files may already have changed.\nDo not improve or reinterpret the failing command yet: a cleaned-up command is not a reproduction.\n\nClassify the incident as one of these, using \\`inconclusive\\` until the evidence supports another:\n\n- \\`loam-product\\` — the binary violated its documented contract or produced internally inconsistent output;\n- \\`project-data\\` — the binary correctly reported invalid, incomplete or stale repository documents;\n- \\`agent-workflow\\` — the generated command/skill was missing, stale, misrouted or followed incorrectly;\n- \\`host-infrastructure\\` — permissions, filesystem, process, shell or tool-host behavior prevented the run;\n- \\`inconclusive\\` — the available evidence does not distinguish the above.\n\n## Collect only safe evidence\n\n1. Run \\`loam --version\\` and record the result.\n2. Run \\`loam doctor --json\\`. If it succeeds, keep \\`healthy\\`, the finding codes and their structured\n   locations/fixes, the resolved repository role, and the write-path state. If it refuses, keep\n   \\`error.code\\` and the sanitized message. Do not apply the fixes during reporting.\n3. When the repository is wired, run \\`loam status --json\\` and keep only the state and next-action\n   rows relevant to this incident. A refusal is evidence too; keep its \\`error.code\\`.\n4. Re-run the original operation only when it is read-only and safe. Never re-run \\`init\\`, \\`new\\`,\n   \\`rebase\\`, \\`subsystem\\`, \\`archive\\`, \\`unarchive\\`, \\`vouch\\`, a recording form of \\`verify\\`, or\n   any other writer merely to make it fail twice. For a writer, record its original exit/output and\n   inspect \\`doctor\\`, \\`status\\` and version only. Do not repair, roll back or delete anything unless\n   the user separately asks for that action.\n5. Prefer the JSON envelope: record \\`contractVersion\\`, \\`ok\\`, \\`command\\`, \\`error.code\\`, finding\n   codes and \\`locations[]\\`. Quote only the smallest stdout/stderr excerpt that demonstrates the\n   symptom. State what was omitted.\n\n## Sanitize before writing\n\nNever include credentials, tokens, cookies, authorization headers, private keys, environment dumps,\nor values of variables whose names contain \\`TOKEN\\`, \\`SECRET\\`, \\`PASSWORD\\`, \\`AUTH\\`, \\`COOKIE\\` or\n\\`KEY\\`. Replace each value with \\`<redacted>\\`. Replace the user's home directory with \\`<home>\\` and\nprefer repository-relative paths. Do not copy source files, architecture/spec bodies, or a complete\ncommand output when a code and short excerpt prove the same fact. Review the finished report once\nmore for secrets before handing it back.\n\n## Write one separate report\n\nCreate \\`loam-reports/YYYY-MM-DD-<short-slug>.md\\` at the current repository root. Use a short neutral\nslug based on the symptom, not a customer, person or secret. Never overwrite a different incident;\nadd a numeric suffix when the path exists. Reports are ordinary project files so the team can\nreview or commit them deliberately, but do not upload, submit an issue, send telemetry, or contact\nany service automatically.\n\nUse this shape, omitting only fields that truly cannot be known and marking them \\`not collected\\`:\n\n    # loam problem report: <short title>\n\n    - Recorded: <ISO-8601 timestamp>\n    - Classification: <one value above>\n    - Repository role: <docs | service | combined | unresolved>\n    - loam version: <version>\n    - Entry point: <chat command, skill, or CLI command; sanitized>\n    - Side effects observed: <none known | paths changed | unknown>\n\n    ## Summary\n    ## Expected\n    ## Actual\n    ## Minimal safe reproduction\n    ## Machine contract\n    ## Doctor and status evidence\n    ## Files changed or write state\n    ## Workaround\n    ## Missing evidence\n    ## Sanitization\n\nIn \\`Machine contract\\`, include exit code plus the stable envelope fields and relevant finding\ncodes/locations; do not paste an entire large JSON payload. In \\`Sanitization\\`, list the kinds of\nvalues removed without revealing them. If no workaround is known, say so rather than inventing one.\n\nFinish by telling the user the report path, classification, whether project files changed, and which\nevidence was unavailable. Keep diagnosis separate from certainty: a plausible cause belongs under\n\\`Summary\\` as a hypothesis until the reproduction proves it.\n`,\n};\n"]}
+{"version":3,"file":"report.js","sourceRoot":"","sources":["../../../../src/core/agent/support/report.ts"],"names":[],"mappings":"AAEA;;;;GAIG;AACH,MAAM,CAAC,MAAM,WAAW,GAAmB;IACzC,IAAI,EAAE,aAAa;IACnB,WAAW,EACT,uFAAuF;IACzF,YAAY,EAAE,EAAE;IAChB,OAAO,EACL,oOAAoO;IACtO,UAAU,EAAE,+BAA+B;IAC3C,YAAY,EAAE,EAAE;IAChB,KAAK,EAAE;QACL,+EAA+E;QAC/E,iFAAiF;QACjF,yFAAyF;QACzF,gFAAgF;QAChF,wFAAwF;KACzF;IACD,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0HP;CACA,CAAC","sourcesContent":["import type { CommandContent } from \"../contract.js\";\n\n/**\n * The incident-reporting protocol: preserve a small, sanitized reproducer when\n * loam or its agent integration behaves unexpectedly, without turning loam\n * into a telemetry service or retrying a risky write.\n */\nexport const LOAM_REPORT: CommandContent = {\n  name: \"loam-report\",\n  description:\n    \"Record unexpected loam or agent behavior as a sanitized, reproducible Markdown report\",\n  argumentHint: \"\",\n  purpose:\n    \"Collect one unexpected loam or agent-integration incident into a separate, reviewable Markdown file. This is local diagnostics only: redact secrets, never upload automatically, and never repeat a writer merely to reproduce it.\",\n  invocation: \"loam instructions loam-report\",\n  placeholders: [],\n  spine: [\n    \"preserve the user's original symptom and expected result before investigating\",\n    \"collect the binary version, wiring diagnosis and the smallest safe reproduction\",\n    \"classify the failure without repairing, retrying a writer or changing project documents\",\n    \"sanitize commands, paths and output, then write one report under loam-reports/\",\n    \"hand back the report path, classification and any evidence that could not be collected\",\n  ],\n  body: `Record one incident where loam, a generated command/skill, or the agent following it\nbehaved unexpectedly. The result is a local diagnostic document, not a repair and not telemetry.\nDo not change architecture/spec files while collecting it.\n\n## Preserve the symptom first\n\nBefore running anything, write down the user's original request, what they expected, what actually\nhappened, the command or chat entry point involved, and whether any files may already have changed.\nDo not improve or reinterpret the failing command yet: a cleaned-up command is not a reproduction.\n\nClassify the incident as one of these, using \\`inconclusive\\` until the evidence supports another:\n\n- \\`loam-product\\` — the binary violated its documented contract or produced internally inconsistent output;\n- \\`project-data\\` — the binary correctly reported invalid, incomplete or stale repository documents;\n- \\`agent-workflow\\` — the generated command/skill was missing, stale, misrouted or followed incorrectly;\n- \\`host-infrastructure\\` — permissions, filesystem, process, shell or tool-host behavior prevented the run;\n- \\`inconclusive\\` — the available evidence does not distinguish the above.\n\n## Collect only safe evidence\n\n1. Run \\`loam --version\\` and record the result.\n2. Run \\`loam doctor --json\\`. If it succeeds, keep \\`healthy\\`, the finding codes and their structured\n   locations/fixes, the resolved repository role, and the write-path state. If it refuses, keep\n   \\`error.code\\` and the sanitized message. Do not apply the fixes during reporting.\n3. When the repository is wired, run \\`loam status --json\\` and keep only the state and next-action\n   rows relevant to this incident. A refusal is evidence too; keep its \\`error.code\\`.\n4. Re-run the original operation only when it is read-only and safe. Never re-run \\`init\\`, \\`new\\`,\n   \\`rebase\\`, \\`subsystem\\`, \\`archive\\`, \\`unarchive\\`, \\`vouch\\`, a recording form of \\`verify\\`, or\n   any other writer merely to make it fail twice. For a writer, record its original exit/output and\n   inspect \\`doctor\\`, \\`status\\` and version only. Do not repair, roll back or delete anything unless\n   the user separately asks for that action.\n5. Prefer the JSON envelope: record \\`contractVersion\\`, \\`ok\\`, \\`command\\`, \\`error.code\\`, finding\n   codes and \\`locations[]\\`. Quote only the smallest stdout/stderr excerpt that demonstrates the\n   symptom. State what was omitted.\n\n## Sanitize before writing\n\nNever include credentials, tokens, cookies, authorization headers, private keys, environment dumps,\nor values of variables whose names contain \\`TOKEN\\`, \\`SECRET\\`, \\`PASSWORD\\`, \\`AUTH\\`, \\`COOKIE\\` or\n\\`KEY\\`. Replace each value with \\`<redacted>\\`. Replace the user's home directory with \\`<home>\\` and\nprefer repository-relative paths. Do not copy source files, architecture/spec bodies, or a complete\ncommand output when a code and short excerpt prove the same fact. Review the finished report once\nmore for secrets before handing it back.\n\nThe fleet's own names are often confidential too: its services, topics, messages, operation ids and\nrequirement ids. Write \\`Minimal safe reproduction\\` on neutral stand-ins — an order service, a\npayment service, a broker topic, a store — rebuilt until it shows the same finding or refusal, so the\nreport can travel without the fleet. Where the excerpt under \\`Actual\\` must quote the fleet's own\noutput, say in \\`Sanitization\\` that it does, so that whoever forwards the report knows that\nsection stays behind.\n\n## Write one separate report\n\nCreate \\`loam-reports/NNN-YYYY-MM-DD-<short-slug>.md\\` in the directory holding the \\`loam.json\\` that\nresolved — or, when a \\`loam.json\\` was found but does not parse, beside that file, so a report about\nthe broken config joins the corpus already there; only when there is no config file at or above you\nis it the directory you run in.\n\\`loam doctor --json\\` hands you that whole directory — that root WITH \\`loam-reports/\\`\nalready on the end — as \\`reports.dir\\`: write inside the path it gives, never joined onto\n\\`loam-reports/\\` a second time. \\`NNN\\` is an ordinal of at least three digits, zero-padded, one more\nthan the highest already in that directory — read \\`reports.next\\` from the same output, which says\n\\`001\\` when the directory is empty or absent, and widens past three digits rather than reusing a\nnumber once the corpus gets there. Use a short neutral slug based on the symptom, not a customer,\nperson or secret. Never\noverwrite a different incident: a path that already exists means a concurrent report claimed that\nordinal, so take the next one rather than adding a suffix. That check is on the PATH, and the\npromise is about the ordinal, so re-run \\`loam doctor --json\\` after writing: if two entries carry\nthe same \\`ordinal\\`, the one with the later \\`Recorded\\` timestamp renames itself to the next free\nnumber. The ordinal is the report's handle —\ncite one by its number in a commit message, an issue, or another report's cross-references, and\nnever by filename, which is free to be renamed. The ordinal is unique within that directory, not\nacross a fleet: a service repository and the docs repository each number their own, so when two\nrepositories are in play cite \\`<repo>/loam-reports/NNN\\`.\n\nReports are ordinary project files so the team can review or commit them deliberately, but\ndo not upload, submit an issue, send telemetry, or contact any service automatically.\n\\`loam doctor\\` reads the directory — how many reports it holds, how many are in each status, and\nwhich ordinal comes next — and that is a local read of local files: nothing is transmitted.\n\nUse this shape, omitting only fields that truly cannot be known and marking them \\`not collected\\`:\n\n    # loam problem report: <short title>\n\n    - Recorded: <ISO-8601 timestamp>\n    - Classification: <one value above>\n    - Status: open\n    - Repository role: <docs | service | combined | unresolved>\n    - loam version: <version>\n    - Entry point: <chat command, skill, or CLI command; sanitized>\n    - Side effects observed: <none known | paths changed | unknown>\n\n    ## Summary\n    ## Expected\n    ## Actual\n    ## Minimal safe reproduction\n    ## Machine contract\n    ## Doctor and status evidence\n    ## Files changed or write state\n    ## Workaround\n    ## Missing evidence\n    ## Sanitization\n\n\\`Status\\` is written as \\`open\\` and stays the report's own record of where it got to. The vocabulary\nis \\`open\\`, \\`sent\\` (handed to loam's author — the person forwarding a report sets this, never the\nagent writing it), \\`fixed in <version>\\`, and \\`superseded by <NNN>\\` naming the report that\nreplaced this one. Close a report by editing its own \\`Status\\` line: there is no index to keep in\nstep, and \\`loam doctor\\` counts the directory by reading that line's first word, so\n\\`fixed in 0.2.0-alpha.5\\` counts as fixed. It reads that line from the HEADER FIELD BLOCK only —\nthe lines above the first \\`##\\` heading, quoted code skipped in either markdown spelling: a fence\n(closed only by a run of the same character at least as long as the one that opened it, so a\n\\`\\`\\` inside a \\`\\`\\`\\` block is content) and an indented block, which is the shape THIS template is\nprinted in above. So a report that quotes this template, however it quotes it, still counts as\nwhatever its own header says. A report written before this\nfield existed has no \\`Status\\` line and counts as unstated.\n\nIn \\`Machine contract\\`, include exit code plus the stable envelope fields and relevant finding\ncodes/locations; do not paste an entire large JSON payload. In \\`Sanitization\\`, list the kinds of\nvalues removed without revealing them. If no workaround is known, say so rather than inventing one.\n\nFinish by telling the user the report path, classification, whether project files changed, and which\nevidence was unavailable. Keep diagnosis separate from certainty: a plausible cause belongs under\n\\`Summary\\` as a hypothesis until the reproduction proves it.\n`,\n};\n"]}

package/dist/core/agent/tools/dialects.js

@@ -58,6 +58,7 @@ const LOAM_ALLOWED_VERBS = [
     "status",
     "steps",
     "subsystem",
+    "tasks",
     "unarchive",
     "validate",
     "verify",

package/dist/core/agent/tools/dialects.js.map

@@ -1 +1 @@
-{"version":3,"file":"dialects.js","sourceRoot":"","sources":["../../../../src/core/agent/tools/dialects.ts"],"names":[],"mappings":"AAQA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsCG;AACH,MAAM,kBAAkB,GAAG;IACzB,OAAO;IACP,SAAS;IACT,SAAS;IACT,OAAO;IACP,cAAc;IACd,MAAM;IACN,QAAQ;IACR,SAAS;IACT,SAAS;IACT,MAAM;IACN,SAAS;IACT,MAAM;IACN,cAAc;IACd,MAAM;IACN,KAAK;IACL,QAAQ;IACR,MAAM;IACN,QAAQ;IACR,OAAO;IACP,WAAW;IACX,WAAW;IACX,UAAU;IACV,QAAQ;CACA,CAAC;AAEX;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,UAAU,GAA2B;IAChD,gBAAgB,EACd,uHAAuH;IACzH,GAAG,EAAE,mHAAmH;IACxH,kBAAkB,EAChB,iHAAiH;IACnH,IAAI,EAAE,mHAAmH;IACzH,IAAI,EAAE,kIAAkI;IACxI,KAAK,EACH,oLAAoL;CACvL,CAAC;AAEF,MAAM,kBAAkB,GAAG,kBAAkB,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,aAAa,CAAC,KAAK,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEzF;;;;;;GAMG;AACH,MAAM,oBAAoB,GAAG;IAC3B,sBAAsB;IACtB,qBAAqB;IACrB,2BAA2B;IAC3B,qBAAqB;CACtB,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEb,MAAM,iBAAiB,GAAG,CAAC,CAAiB,EAAU,EAAE,CACtD,CAAC,CAAC,IAAI,KAAK,aAAa,CAAC,CAAC,CAAC,oBAAoB,CAAC,CAAC,CAAC,kBAAkB,CAAC;AAEvE;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAG,CAAC,GAAW,EAAoB,EAAE,CAAC,CAAC;IAC1D,IAAI,EAAE,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,GAAG,EAAE,QAAQ,EAAE,IAAI,EAAE,UAAU,CAAC;IACjD,MAAM,EAAE,CAAC,CAAC,EAAE,EAAE,CACZ,cAAc,CAAC,CAAC,IAAI,kBAAkB,CAAC,CAAC,WAAW,IAAI;QACvD,kBAAkB,iBAAiB,CAAC,CAAC,CAAC,YAAY,CAAC,CAAC,IAAI,EAAE;CAC7D,CAAC,CAAC;AAEH;;;;GAIG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,KAAK,EAAE,MAAM,CAAC,CAAC,OAAO,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC7F,MAAM,CAAC,MAAM,SAAS,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,KAAK,EAAE,MAAM,CAAC,CAAC,OAAO,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;AAElG;;;;;gCAKgC;AAChC,+EAA+E;AAC/E,MAAM,CAAC,MAAM,WAAW,GAAG,CAAC,CAAiB,EAAU,EAAE,CACvD,qBAAqB,CAAC,CAAC,WAAW,YAAY,CAAC,CAAC,IAAI,EAAE,CAAC;AACzD,+EAA+E;AAC/E,MAAM,CAAC,MAAM,QAAQ,GAAG,CAAC,CAAiB,EAAU,EAAE,CACpD,qBAAqB,CAAC,CAAC,WAAW,oBAAoB,CAAC,CAAC,YAAY,YAAY,CAAC,CAAC,IAAI,EAAE,CAAC;AAC3F,sEAAsE;AACtE,MAAM,CAAC,MAAM,OAAO,GAAG,CAAC,CAAiB,EAAU,EAAE,CACnD,cAAc,CAAC,CAAC,IAAI,kBAAkB,CAAC,CAAC,WAAW,YAAY,CAAC,CAAC,IAAI,EAAE,CAAC;AAC1E,gEAAgE;AAChE,MAAM,CAAC,MAAM,QAAQ,GAAG,CAAC,CAAiB,EAAU,EAAE,CAAC,KAAK,CAAC,CAAC,IAAI,OAAO,CAAC,CAAC,IAAI,EAAE,CAAC;AAElF,iFAAiF;AACjF,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,IAAY,EAAU,EAAE,CAAC,IAAI,CAAC,OAAO,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC","sourcesContent":["/**\n * How one shared command body is SPELLED per tool family: the markdown and\n * TOML wrapper dialects, and the Agent Skills convention. registry.ts builds\n * its entries from these — nothing here adds prose of its own, so the body\n * stays one source of truth however many tools spell it.\n */\nimport type { AgentFileEmitter, CommandContent } from \"../contract.js\";\n\n/**\n * The loam verbs a generated file pre-approves, so an agent that honors the\n * field stops asking permission for each call. Everything else a command needs\n * (Read, Write, the service's own test runner) stays under the user's normal\n * permission settings, and a tool that does not know the field ignores it.\n *\n * Enumerated rather than spelled `Bash(loam:*)`, for one verb's sake. `vouch`\n * is the only command in loam whose output is a claim about a HUMAN act — a\n * person read the code and says the document matches it — and a blanket\n * allowlist pre-approved it, which handed the agent that wrote a draft the\n * power to promote its own draft to `verified` without anybody being asked.\n * That inverts the argument loam makes everywhere else: it holds test evidence\n * to \"an agent must not be able to SAY a scenario is tested\", and then let one\n * say a spec matches the code. `vouch` now refuses without a terminal or\n * `--yes` (commands/vouch.ts) — this list is the other half, so the refusal is\n * something a person sees rather than something an agent routes around.\n *\n * A verb missing from this list is not forbidden, only unapproved: the agent\n * asks, and the user says yes. That is the correct cost for this one.\n *\n * The rule the list obeys is **every verb the CLI registers except the keys of\n * {@link UNAPPROVED}**, and it admits no silent third category: a verb is\n * either here or there, with a written reason. The rule it does NOT obey is\n * \"read-only\" — that is false of `subsystem`, which writes, and it was never\n * what this list did anyway: `archive`, `rebase` and `new` all write, and all\n * three have been on it since the day the wildcard came off.\n *\n * The rule is written down because a hand-kept list drifts, and this one had.\n * Seventeen of the twenty-nine registered verbs were on it, and three of the\n * twelve missing ones were instructed by loam's own protocols: `loam-implement`\n * opens with `loam context` and calls `loam steps` mandatory before a step\n * definition is written, and `loam-check`'s fix table says to run\n * `loam subsystem sync`. Each stalled on a permission prompt at exactly the\n * step its own protocol calls required. It was worst for `explain`: every\n * generated file now tells the agent to read the protocol narrow\n * (`loam instructions <workflow> --no-fix-tables`) and then look up the codes\n * the run actually reported — so the one command that makes an 84 KB page\n * payable was the one the skill could not invoke unasked.\n */\nconst LOAM_ALLOWED_VERBS = [\n  \"adopt\",\n  \"archive\",\n  \"context\",\n  \"delta\",\n  \"dependencies\",\n  \"diff\",\n  \"doctor\",\n  \"explain\",\n  \"explore\",\n  \"gate\",\n  \"gherkin\",\n  \"init\",\n  \"instructions\",\n  \"list\",\n  \"new\",\n  \"rebase\",\n  \"show\",\n  \"status\",\n  \"steps\",\n  \"subsystem\",\n  \"unarchive\",\n  \"validate\",\n  \"verify\",\n] as const;\n\n/**\n * The verbs deliberately left OFF {@link LOAM_ALLOWED_VERBS}, each with the\n * reason it is off.\n *\n * A map rather than a paragraph, because \"every verb but the named exclusions\"\n * is only a checkable rule if the exclusions are a VALUE. test/agents.test.ts\n * reads this one: the emitted allowlist must equal the CLI's registered\n * commands minus these keys, so an absent verb is either a decision recorded\n * here or a test failure — never something nobody can tell from a forgotten\n * one, which is what the previous list was. Only `vouch` had ever been reasoned\n * in the source, and its reason is the paragraph above, unchanged.\n *\n * The equality is checked in the test layer and cannot be computed here:\n * deriving the allowlist from the command registry would mean `core/`\n * importing `commands/`, which AGENTS.md forbids outright.\n */\nexport const UNAPPROVED: Record<string, string> = {\n  \"audit-openspec\":\n    \"the OpenSpec on-ramp: a one-time migration a person drives against a foreign workspace, named by no workflow protocol\",\n  mcp: \"a long-running stdio server rather than a call that returns — an agent that starts it inside a step waits forever\",\n  \"migrate-openspec\":\n    \"the same on-ramp, and `--apply` materializes a whole target tree from a mapping only a human can have filled in\",\n  open: \"writes a `.code-workspace` for a person's editor; the output is aimed at the human, and no protocol step reads it\",\n  seed: \"templates the fleet map from a human-authored fleet.yaml — who exists and who calls whom is the one thing no generator may state\",\n  vouch:\n    \"a claim about a HUMAN act, so an agent must not be able to SAY a spec matches the code; the refusal has to be something a person sees rather than something an agent routes around\",\n};\n\nconst LOAM_ALLOWED_TOOLS = LOAM_ALLOWED_VERBS.map((v) => `Bash(loam ${v}:*)`).join(\", \");\n\n/**\n * Incident collection is intentionally narrower than a lifecycle workflow.\n * The body names writers so an agent can recognize and avoid retrying them;\n * inheriting the lifecycle allowlist would nevertheless pre-authorize those\n * same writers while diagnosing a bad run. Version, doctor and status are the\n * complete command set the reporting protocol asks to execute.\n */\nconst REPORT_ALLOWED_TOOLS = [\n  \"Bash(loam --version)\",\n  \"Bash(loam doctor:*)\",\n  \"Bash(loam instructions:*)\",\n  \"Bash(loam status:*)\",\n].join(\", \");\n\nconst skillAllowedTools = (c: CommandContent): string =>\n  c.name === \"loam-report\" ? REPORT_ALLOWED_TOOLS : LOAM_ALLOWED_TOOLS;\n\n/**\n * The Agent Skills convention loam EMITS: `<root>/skills/<name>/SKILL.md`, YAML\n * frontmatter, then the shared body verbatim — where `<root>` is whatever the\n * calling registry entry passes.\n *\n * It used to say that every tool in the registry which reads skills spells the\n * path this way. That was an unevidenced universal, and the `agents` entry\n * falsifies it: `.agents/skills/` is a vendor-neutral root several tools read\n * INSTEAD of their own dot-directory, not another tool's directory. Where a\n * path is documented by the tool, the citation lives on that tool's registry\n * entry — this helper states only what it writes.\n *\n * `description` is load-bearing in a way no command file's is — it is the only\n * thing the model sees before deciding whether to load the skill — so it comes\n * from the same `CommandContent.description` the command wrappers use rather\n * than a second, skill-flavoured copy that could drift into a better pitch for\n * a worse protocol.\n */\nexport const skillsIn = (dir: string): AgentFileEmitter => ({\n  path: (name) => [dir, \"skills\", name, \"SKILL.md\"],\n  format: (c) =>\n    `---\\nname: ${c.name}\\ndescription: ${c.description}\\n` +\n    `allowed-tools: ${skillAllowedTools(c)}\\n---\\n\\n${c.body}`,\n});\n\n/**\n * TOML basic-string escapes for the one non-markdown format. Today's bodies\n * carry neither backslashes nor `\"\"\"`, but the escape is what keeps a future\n * body edit from silently corrupting the generated TOML.\n */\nexport const tomlLine = (s: string): string => s.replace(/\\\\/g, \"\\\\\\\\\").replace(/\"/g, '\\\\\"');\nexport const tomlBlock = (s: string): string => s.replace(/\\\\/g, \"\\\\\\\\\").replace(/\"\"\"/g, '\"\"\\\\\"');\n\n/* The four markdown command dialects the registry actually needs. Shared so a\n * tool's entry is its PATH and its dialect's name — the part that differs —\n * instead of a wall of near-identical template literals. `claude` deliberately\n * spells its own wrapper inline even though `hintedMd` matches it byte for\n * byte: an edit made here for some other tool must not be able to re-spell the\n * one format that is frozen. */\n/** Description-only frontmatter — the most common dialect by a wide margin. */\nexport const describedMd = (c: CommandContent): string =>\n  `---\\ndescription: ${c.description}\\n---\\n\\n${c.body}`;\n/** Description plus Claude's `argument-hint`, for the tools that copied it. */\nexport const hintedMd = (c: CommandContent): string =>\n  `---\\ndescription: ${c.description}\\nargument-hint: ${c.argumentHint}\\n---\\n\\n${c.body}`;\n/** Name plus description — the Cascade-style workflow frontmatter. */\nexport const namedMd = (c: CommandContent): string =>\n  `---\\nname: ${c.name}\\ndescription: ${c.description}\\n---\\n\\n${c.body}`;\n/** No frontmatter at all: a title line is the whole wrapper. */\nexport const titledMd = (c: CommandContent): string => `# ${c.name}\\n\\n${c.body}`;\n\n/** The `loam-` prefix a namespace directory carries instead of the file name. */\nexport const unprefixed = (name: string): string => name.replace(/^loam-/, \"\");\n"]}
+{"version":3,"file":"dialects.js","sourceRoot":"","sources":["../../../../src/core/agent/tools/dialects.ts"],"names":[],"mappings":"AAQA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsCG;AACH,MAAM,kBAAkB,GAAG;IACzB,OAAO;IACP,SAAS;IACT,SAAS;IACT,OAAO;IACP,cAAc;IACd,MAAM;IACN,QAAQ;IACR,SAAS;IACT,SAAS;IACT,MAAM;IACN,SAAS;IACT,MAAM;IACN,cAAc;IACd,MAAM;IACN,KAAK;IACL,QAAQ;IACR,MAAM;IACN,QAAQ;IACR,OAAO;IACP,WAAW;IACX,OAAO;IACP,WAAW;IACX,UAAU;IACV,QAAQ;CACA,CAAC;AAEX;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,UAAU,GAA2B;IAChD,gBAAgB,EACd,uHAAuH;IACzH,GAAG,EAAE,mHAAmH;IACxH,kBAAkB,EAChB,iHAAiH;IACnH,IAAI,EAAE,mHAAmH;IACzH,IAAI,EAAE,kIAAkI;IACxI,KAAK,EACH,oLAAoL;CACvL,CAAC;AAEF,MAAM,kBAAkB,GAAG,kBAAkB,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,aAAa,CAAC,KAAK,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEzF;;;;;;GAMG;AACH,MAAM,oBAAoB,GAAG;IAC3B,sBAAsB;IACtB,qBAAqB;IACrB,2BAA2B;IAC3B,qBAAqB;CACtB,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEb,MAAM,iBAAiB,GAAG,CAAC,CAAiB,EAAU,EAAE,CACtD,CAAC,CAAC,IAAI,KAAK,aAAa,CAAC,CAAC,CAAC,oBAAoB,CAAC,CAAC,CAAC,kBAAkB,CAAC;AAEvE;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAG,CAAC,GAAW,EAAoB,EAAE,CAAC,CAAC;IAC1D,IAAI,EAAE,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,GAAG,EAAE,QAAQ,EAAE,IAAI,EAAE,UAAU,CAAC;IACjD,MAAM,EAAE,CAAC,CAAC,EAAE,EAAE,CACZ,cAAc,CAAC,CAAC,IAAI,kBAAkB,CAAC,CAAC,WAAW,IAAI;QACvD,kBAAkB,iBAAiB,CAAC,CAAC,CAAC,YAAY,CAAC,CAAC,IAAI,EAAE;CAC7D,CAAC,CAAC;AAEH;;;;GAIG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,KAAK,EAAE,MAAM,CAAC,CAAC,OAAO,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC7F,MAAM,CAAC,MAAM,SAAS,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,KAAK,EAAE,MAAM,CAAC,CAAC,OAAO,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;AAElG;;;;;gCAKgC;AAChC,+EAA+E;AAC/E,MAAM,CAAC,MAAM,WAAW,GAAG,CAAC,CAAiB,EAAU,EAAE,CACvD,qBAAqB,CAAC,CAAC,WAAW,YAAY,CAAC,CAAC,IAAI,EAAE,CAAC;AACzD,+EAA+E;AAC/E,MAAM,CAAC,MAAM,QAAQ,GAAG,CAAC,CAAiB,EAAU,EAAE,CACpD,qBAAqB,CAAC,CAAC,WAAW,oBAAoB,CAAC,CAAC,YAAY,YAAY,CAAC,CAAC,IAAI,EAAE,CAAC;AAC3F,sEAAsE;AACtE,MAAM,CAAC,MAAM,OAAO,GAAG,CAAC,CAAiB,EAAU,EAAE,CACnD,cAAc,CAAC,CAAC,IAAI,kBAAkB,CAAC,CAAC,WAAW,YAAY,CAAC,CAAC,IAAI,EAAE,CAAC;AAC1E,gEAAgE;AAChE,MAAM,CAAC,MAAM,QAAQ,GAAG,CAAC,CAAiB,EAAU,EAAE,CAAC,KAAK,CAAC,CAAC,IAAI,OAAO,CAAC,CAAC,IAAI,EAAE,CAAC;AAElF,iFAAiF;AACjF,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,IAAY,EAAU,EAAE,CAAC,IAAI,CAAC,OAAO,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC","sourcesContent":["/**\n * How one shared command body is SPELLED per tool family: the markdown and\n * TOML wrapper dialects, and the Agent Skills convention. registry.ts builds\n * its entries from these — nothing here adds prose of its own, so the body\n * stays one source of truth however many tools spell it.\n */\nimport type { AgentFileEmitter, CommandContent } from \"../contract.js\";\n\n/**\n * The loam verbs a generated file pre-approves, so an agent that honors the\n * field stops asking permission for each call. Everything else a command needs\n * (Read, Write, the service's own test runner) stays under the user's normal\n * permission settings, and a tool that does not know the field ignores it.\n *\n * Enumerated rather than spelled `Bash(loam:*)`, for one verb's sake. `vouch`\n * is the only command in loam whose output is a claim about a HUMAN act — a\n * person read the code and says the document matches it — and a blanket\n * allowlist pre-approved it, which handed the agent that wrote a draft the\n * power to promote its own draft to `verified` without anybody being asked.\n * That inverts the argument loam makes everywhere else: it holds test evidence\n * to \"an agent must not be able to SAY a scenario is tested\", and then let one\n * say a spec matches the code. `vouch` now refuses without a terminal or\n * `--yes` (commands/vouch.ts) — this list is the other half, so the refusal is\n * something a person sees rather than something an agent routes around.\n *\n * A verb missing from this list is not forbidden, only unapproved: the agent\n * asks, and the user says yes. That is the correct cost for this one.\n *\n * The rule the list obeys is **every verb the CLI registers except the keys of\n * {@link UNAPPROVED}**, and it admits no silent third category: a verb is\n * either here or there, with a written reason. The rule it does NOT obey is\n * \"read-only\" — that is false of `subsystem`, which writes, and it was never\n * what this list did anyway: `archive`, `rebase` and `new` all write, and all\n * three have been on it since the day the wildcard came off.\n *\n * The rule is written down because a hand-kept list drifts, and this one had.\n * Seventeen of the twenty-nine registered verbs were on it, and three of the\n * twelve missing ones were instructed by loam's own protocols: `loam-implement`\n * opens with `loam context` and calls `loam steps` mandatory before a step\n * definition is written, and `loam-check`'s fix table says to run\n * `loam subsystem sync`. Each stalled on a permission prompt at exactly the\n * step its own protocol calls required. It was worst for `explain`: every\n * generated file now tells the agent to read the protocol narrow\n * (`loam instructions <workflow> --no-fix-tables`) and then look up the codes\n * the run actually reported — so the one command that makes an 84 KB page\n * payable was the one the skill could not invoke unasked.\n */\nconst LOAM_ALLOWED_VERBS = [\n  \"adopt\",\n  \"archive\",\n  \"context\",\n  \"delta\",\n  \"dependencies\",\n  \"diff\",\n  \"doctor\",\n  \"explain\",\n  \"explore\",\n  \"gate\",\n  \"gherkin\",\n  \"init\",\n  \"instructions\",\n  \"list\",\n  \"new\",\n  \"rebase\",\n  \"show\",\n  \"status\",\n  \"steps\",\n  \"subsystem\",\n  \"tasks\",\n  \"unarchive\",\n  \"validate\",\n  \"verify\",\n] as const;\n\n/**\n * The verbs deliberately left OFF {@link LOAM_ALLOWED_VERBS}, each with the\n * reason it is off.\n *\n * A map rather than a paragraph, because \"every verb but the named exclusions\"\n * is only a checkable rule if the exclusions are a VALUE. test/agents.test.ts\n * reads this one: the emitted allowlist must equal the CLI's registered\n * commands minus these keys, so an absent verb is either a decision recorded\n * here or a test failure — never something nobody can tell from a forgotten\n * one, which is what the previous list was. Only `vouch` had ever been reasoned\n * in the source, and its reason is the paragraph above, unchanged.\n *\n * The equality is checked in the test layer and cannot be computed here:\n * deriving the allowlist from the command registry would mean `core/`\n * importing `commands/`, which AGENTS.md forbids outright.\n */\nexport const UNAPPROVED: Record<string, string> = {\n  \"audit-openspec\":\n    \"the OpenSpec on-ramp: a one-time migration a person drives against a foreign workspace, named by no workflow protocol\",\n  mcp: \"a long-running stdio server rather than a call that returns — an agent that starts it inside a step waits forever\",\n  \"migrate-openspec\":\n    \"the same on-ramp, and `--apply` materializes a whole target tree from a mapping only a human can have filled in\",\n  open: \"writes a `.code-workspace` for a person's editor; the output is aimed at the human, and no protocol step reads it\",\n  seed: \"templates the fleet map from a human-authored fleet.yaml — who exists and who calls whom is the one thing no generator may state\",\n  vouch:\n    \"a claim about a HUMAN act, so an agent must not be able to SAY a spec matches the code; the refusal has to be something a person sees rather than something an agent routes around\",\n};\n\nconst LOAM_ALLOWED_TOOLS = LOAM_ALLOWED_VERBS.map((v) => `Bash(loam ${v}:*)`).join(\", \");\n\n/**\n * Incident collection is intentionally narrower than a lifecycle workflow.\n * The body names writers so an agent can recognize and avoid retrying them;\n * inheriting the lifecycle allowlist would nevertheless pre-authorize those\n * same writers while diagnosing a bad run. Version, doctor and status are the\n * complete command set the reporting protocol asks to execute.\n */\nconst REPORT_ALLOWED_TOOLS = [\n  \"Bash(loam --version)\",\n  \"Bash(loam doctor:*)\",\n  \"Bash(loam instructions:*)\",\n  \"Bash(loam status:*)\",\n].join(\", \");\n\nconst skillAllowedTools = (c: CommandContent): string =>\n  c.name === \"loam-report\" ? REPORT_ALLOWED_TOOLS : LOAM_ALLOWED_TOOLS;\n\n/**\n * The Agent Skills convention loam EMITS: `<root>/skills/<name>/SKILL.md`, YAML\n * frontmatter, then the shared body verbatim — where `<root>` is whatever the\n * calling registry entry passes.\n *\n * It used to say that every tool in the registry which reads skills spells the\n * path this way. That was an unevidenced universal, and the `agents` entry\n * falsifies it: `.agents/skills/` is a vendor-neutral root several tools read\n * INSTEAD of their own dot-directory, not another tool's directory. Where a\n * path is documented by the tool, the citation lives on that tool's registry\n * entry — this helper states only what it writes.\n *\n * `description` is load-bearing in a way no command file's is — it is the only\n * thing the model sees before deciding whether to load the skill — so it comes\n * from the same `CommandContent.description` the command wrappers use rather\n * than a second, skill-flavoured copy that could drift into a better pitch for\n * a worse protocol.\n */\nexport const skillsIn = (dir: string): AgentFileEmitter => ({\n  path: (name) => [dir, \"skills\", name, \"SKILL.md\"],\n  format: (c) =>\n    `---\\nname: ${c.name}\\ndescription: ${c.description}\\n` +\n    `allowed-tools: ${skillAllowedTools(c)}\\n---\\n\\n${c.body}`,\n});\n\n/**\n * TOML basic-string escapes for the one non-markdown format. Today's bodies\n * carry neither backslashes nor `\"\"\"`, but the escape is what keeps a future\n * body edit from silently corrupting the generated TOML.\n */\nexport const tomlLine = (s: string): string => s.replace(/\\\\/g, \"\\\\\\\\\").replace(/\"/g, '\\\\\"');\nexport const tomlBlock = (s: string): string => s.replace(/\\\\/g, \"\\\\\\\\\").replace(/\"\"\"/g, '\"\"\\\\\"');\n\n/* The four markdown command dialects the registry actually needs. Shared so a\n * tool's entry is its PATH and its dialect's name — the part that differs —\n * instead of a wall of near-identical template literals. `claude` deliberately\n * spells its own wrapper inline even though `hintedMd` matches it byte for\n * byte: an edit made here for some other tool must not be able to re-spell the\n * one format that is frozen. */\n/** Description-only frontmatter — the most common dialect by a wide margin. */\nexport const describedMd = (c: CommandContent): string =>\n  `---\\ndescription: ${c.description}\\n---\\n\\n${c.body}`;\n/** Description plus Claude's `argument-hint`, for the tools that copied it. */\nexport const hintedMd = (c: CommandContent): string =>\n  `---\\ndescription: ${c.description}\\nargument-hint: ${c.argumentHint}\\n---\\n\\n${c.body}`;\n/** Name plus description — the Cascade-style workflow frontmatter. */\nexport const namedMd = (c: CommandContent): string =>\n  `---\\nname: ${c.name}\\ndescription: ${c.description}\\n---\\n\\n${c.body}`;\n/** No frontmatter at all: a title line is the whole wrapper. */\nexport const titledMd = (c: CommandContent): string => `# ${c.name}\\n\\n${c.body}`;\n\n/** The `loam-` prefix a namespace directory carries instead of the file name. */\nexport const unprefixed = (name: string): string => name.replace(/^loam-/, \"\");\n"]}