[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7593T9532KN3VHS59CRCPFD":3,"skill-same:01M7593T9532KN3VHS59CRCPFD":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7593T9532KN3VHS59CRCPFD","control-plane-validation",null,"Canonical workflow for validating changes to this repository's control plane — establishes Git baseline, classifies each changed path by owning plane, checks current official Codex docs for format drift, runs tools\u002Fcontrol-plane\u002Fverify.mjs and syntax\u002Funit tests for changed scripts, inspects git diff --check, and reports exact diff scope while distinguishing tested evidence from assumptions. Use whenever work touches AGENTS.md, .codex\u002F**, .agents\u002F**, .claude\u002F**, control-plane tooling (tools\u002Fcontrol-plane\u002F**), source-control governance, CI governance (.github\u002Fworkflows\u002F**), or production-policy documentation (docs\u002Fcontrol-plane\u002F**, netlify.toml).","JackSmack1971\u002Ffreeforge-chat","JackSmack1971","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128181597?v=4","01M6KS1FH32N6WNWZ68JC9FFDJ","01M7593JRZ0MV9B0VVTRGWZ0WC",0,"MIT","https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcontrol-plane-validation\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: control-plane-validation\ndescription: Canonical workflow for validating changes to this repository's control plane — establishes Git baseline, classifies each changed path by owning plane, checks current official Codex docs for format drift, runs tools\u002Fcontrol-plane\u002Fverify.mjs and syntax\u002Funit tests for changed scripts, inspects git diff --check, and reports exact diff scope while distinguishing tested evidence from assumptions. Use whenever work touches AGENTS.md, .codex\u002F**, .agents\u002F**, .claude\u002F**, control-plane tooling (tools\u002Fcontrol-plane\u002F**), source-control governance, CI governance (.github\u002Fworkflows\u002F**), or production-policy documentation (docs\u002Fcontrol-plane\u002F**, netlify.toml).\n---\n\n# Control Plane Validation\n\n## Contents\n\n1. Objective\n2. Authority statement (non-negotiable)\n3. Trigger scope\n4. Workflow\n5. Owning-plane classification\n6. Evidence and status vocabulary\n7. Failure handling\n8. Resources\n\n## 1. Objective\n\nProve — with fresh, on-disk evidence — that a change touching this\nrepository's control plane is structurally sound and correctly scoped,\nwithout ever implying that a passing check authorizes shipping it. This\nskill produces a validation report; it does not implement fixes, and it\nnever pushes, merges, or deploys.\n\nThe default deliverable is:\n\n- a Git baseline (branch, HEAD, dirty-state inventory);\n- a per-path plane classification for every changed file;\n- a Codex-docs drift check for any changed Codex-native file format;\n- a `tools\u002Fcontrol-plane\u002Fverify.mjs` run;\n- syntax\u002Funit-test evidence for changed scripts;\n- a `git diff --check` inspection;\n- an exact diff-scope report;\n- an explicit evidence-vs-assumption breakdown;\n- a release-readiness statement that is blocked, not guessed, when\n  required checks are unavailable.\n\n## 2. Authority statement (non-negotiable)\n\nState these explicitly in every report this skill produces, not just once\nat skill-authoring time:\n\n- **Skills are workflow knowledge, not permission grants.** This skill\n  tells you *how* to validate a control-plane change once you are already\n  permitted to look at and edit those files. It does not itself authorize\n  any tool call, write, commit, or publication.\n- **Hooks are guardrails, not complete authorization.** A hook firing (or\n  not firing) is not proof that an action is safe or approved.\n- **Tests passing does not authorize push, merge, or deploy.** A green\n  `tools\u002Fcontrol-plane\u002Fverify.mjs` run, a green Biome check, or a green\n  `node --test` run is evidence (§1.11 of the migration contract), not\n  approval (§1.5). Approval is a separate, human act.\n- **`main` publication triggers Netlify production.** Merging to `main` is\n  an automatic, public production deploy with no separate gate\n  (`netlify.toml` has no branch\u002Fcontext restriction). Treat it with\n  release-action weight every time, regardless of what this skill reports.\n\nFull rationale: [references\u002Ftopology.md](references\u002Ftopology.md), \"Authority\nstatement\" section.\n\n## 3. Trigger scope\n\nRun this skill when a task touches any of:\n\n- `AGENTS.md`, `.agents\u002F**`, `.codex\u002F**`, `.claude\u002F**`;\n- `tools\u002Fcontrol-plane\u002F**` (the verifier itself);\n- CI governance: `.github\u002Fworkflows\u002F**`;\n- production-policy documentation: `docs\u002Fcontrol-plane\u002F**`, `netlify.toml`;\n- `security\u002Fconstitution.md` (machine-readable security invariants that\n  `AGENTS.md` restates in prose).\n\nIf the task touches none of these, this skill does not apply — do not run\nit defensively on unrelated product-code changes.\n\n## 4. Workflow\n\nCopy and maintain this checklist for the current change:\n\n```text\nControl Plane Validation Progress\n- [ ] 1. Establish Git baseline and dirty state\n- [ ] 2. Identify owning plane for each changed path\n- [ ] 3. Check current official Codex docs for format drift (if applicable)\n- [ ] 4. Run tools\u002Fcontrol-plane\u002Fverify.mjs\n- [ ] 5. Run syntax\u002Funit tests for changed scripts\n- [ ] 6. Inspect git diff --check\n- [ ] 7. Report exact diff scope\n- [ ] 8. Distinguish tested evidence from assumptions\n- [ ] 9. State release-readiness honestly (block the claim if unverifiable)\n```\n\n### Step 1: Git baseline and dirty state\n\nDo not trust a prior summary, `.planning\u002F**` artifact, or this skill's own\nreference files for current state — re-derive it:\n\n```bash\ngit status --porcelain=v1\ngit rev-parse HEAD\ngit rev-parse --abbrev-ref HEAD\n```\n\nOr let the bundled script do it (see Step 4 — it captures the same baseline\nas part of one evidence object).\n\n### Step 2: Identify owning plane for each changed path\n\nClassify every changed path against\n[references\u002Ftopology.md](references\u002Ftopology.md)'s plane map. A path that\nmatches no row is out of this skill's scope — note it, do not force-fit a\nplane onto it. Watch specifically for a single diff that touches two planes\nin a way that collapses their separation (e.g. a rule file edit that also\nadds executable logic, or a skill edit that also changes a permission\nallowlist) — that is exactly the failure mode\n`docs\u002Fcontrol-plane\u002FMIGRATION_CONTRACT.md` §3.3 calls out, and it is a\nfinding to surface, not silently pass through.\n\n`scripts\u002Frun-checks.mjs` (Step 4) performs this classification\nautomatically and includes it in its JSON output under `diffScope`.\n\n### Step 3: Check current official Codex docs for format drift\n\nOnly required when the diff touches a Codex-native file format:\n`.codex\u002Fconfig.toml`, `.codex\u002Fhooks.json`, `.codex\u002Frules\u002F*.rules`,\n`.codex\u002Fagents\u002F*.toml`, or `.codex\u002Fworkflows\u002F**`. `tools\u002Fcontrol-plane\u002Fverify.mjs`\nvalidates these files against this repository's *current understanding* of\ntheir grammar (see its embedded TOML\u002Fexecpolicy parsers) — it cannot detect\nthat Codex CLI's actual contract for one of these formats changed upstream.\n\nWhen applicable, fetch the current official Codex CLI documentation for the\nspecific format(s) touched and compare against what\n`tools\u002Fcontrol-plane\u002Fverify.mjs` currently enforces. If network access is\nunavailable, do not silently skip this — record it as **UNVERIFIED** (see\n[references\u002Fevidence-schema.md](references\u002Fevidence-schema.md)) and carry\nthat into Step 9's release-readiness statement.\n\nWhen not applicable (the diff doesn't touch a Codex-native format), record\nthat this step was correctly skipped and why — do not spend a network call\nproving a negative.\n\n### Step 4: Run `tools\u002Fcontrol-plane\u002Fverify.mjs`\n\nRun the bundled deterministic script, which wraps `verify.mjs` and adds\nSteps 1, 2, 6, and 7 of this workflow in one evidence object:\n\n```bash\nnode .agents\u002Fskills\u002Fcontrol-plane-validation\u002Fscripts\u002Frun-checks.mjs\n```\n\nOr run the verifier directly if you only need its own checks:\n\n```bash\nnode tools\u002Fcontrol-plane\u002Fverify.mjs\n```\n\nRead every FAIL, including non-authoritative\u002Finformational ones (the\nClaude-compatibility check is informational by design — see\n`tools\u002Fcontrol-plane\u002Fverify.mjs`'s own comments — but still worth reporting\nif it fails). Never treat a SKIPPED check as a PASS.\n\n### Step 5: Run syntax\u002Funit tests for changed scripts\n\n`scripts\u002Frun-checks.mjs` syntax-checks (`node --check`) every changed\n`.js`\u002F`.mjs`\u002F`.cjs` file inside a recognized control-plane plane and reports\nthe results under `syntaxCheck`. This proves the file parses — it is not a\nsubstitute for running its actual tests. Separately:\n\n- if the change touches `tools\u002Fcontrol-plane\u002Fverify.mjs` or anything it\n  imports, also run whatever test suite currently covers it (check\n  `tests\u002FAGENTS.md` and `tests\u002Fsecurity\u002F` for a matching file — e.g.\n  `tests\u002Fsecurity\u002Fcodex-config.test.mjs` covers `.codex\u002Fconfig.toml`\n  parseability);\n- if no test currently covers a changed control-plane script, say so\n  explicitly rather than reporting untested code as verified.\n\n### Step 6: Inspect `git diff --check`\n\n```bash\ngit diff --check\ngit diff --cached --check\n```\n\n`scripts\u002Frun-checks.mjs` runs both and classifies the result: real conflict\nmarkers (`\u003C\u003C\u003C\u003C\u003C\u003C\u003C`, `=======`, `>>>>>>>` at line start) are an authoritative\nfailure; trailing-whitespace-only findings are informational (this\nrepository has a known pre-existing trailing-whitespace finding in\n`.repository-hygiene\u002Freport.md` — do not treat that class of finding as\nblocking by default, but do report it).\n\n### Step 7: Report exact diff scope\n\nState precisely which paths changed, their Git status code, and their\nplane — not a paraphrase (\"some control-plane files changed\"). Use\n`diffScope.byPlane` from the script output directly; it is already grouped\ncorrectly. Call out `outOfScopeCount` if non-zero so the reader knows the\nreport is deliberately narrowed to control-plane paths, not silently\nincomplete.\n\n### Step 8: Distinguish tested evidence from assumptions\n\nApply [references\u002Fevidence-schema.md](references\u002Fevidence-schema.md)'s\nevidence-vs-assumption rule to every claim in the report: a claim is\n**evidence** only if it is backed by this session's own script\u002Ftool output\nor a freshly fetched doc; anything sourced from\n`docs\u002Fcontrol-plane\u002FCURRENT_STATE.md`, `MIGRATION_CONTRACT.md`, a prior\nsummary, or this skill's own reference files is a **hypothesis** until\nre-confirmed in this session.\n\n### Step 9: State release-readiness honestly\n\nFollow [references\u002Fevidence-schema.md](references\u002Fevidence-schema.md)'s\n\"Blocking a release-ready claim\" section. In particular: if Step 3 was\nrequired and could not be performed, or `tools\u002Fcontrol-plane\u002Fverify.mjs`\ncould not run at all, do not say the change is \"ready\" — say what is\nunverified and why, plainly, in the same report.\n\n## 5. Owning-plane classification\n\nFull plane map, target topology, and authority statement:\n[references\u002Ftopology.md](references\u002Ftopology.md).\n\n## 6. Evidence and status vocabulary\n\nFull JSON shape for `scripts\u002Frun-checks.mjs`, the PASS\u002FFAIL\u002FSKIPPED\u002FUNVERIFIED\nvocabulary, and the evidence-vs-assumption rule:\n[references\u002Fevidence-schema.md](references\u002Fevidence-schema.md).\n\n## 7. Failure handling\n\n- `tools\u002Fcontrol-plane\u002Fverify.mjs` fails to load or throws: report it as a\n  tool failure (not a SKIPPED sub-check) and block any release-readiness\n  claim — do not fall back to reasoning about control-plane correctness\n  from memory.\n- Codex docs are unreachable for Step 3: mark that specific claim\n  UNVERIFIED, do not treat the rest of the report as invalidated, and do\n  not silently drop the step from the checklist.\n- A changed path does not match any plane rule: report it explicitly as\n  unclassified rather than guessing a plane or omitting it from the diff\n  scope.\n- `git diff --check` reports real conflict markers: stop and resolve them\n  before any further validation — a diff with conflict markers is not in a\n  reviewable state.\n- No test currently covers a changed control-plane script: report that gap\n  by name; do not report the script as verified because it parses.\n\n## 8. Resources\n\nLoad only what the current step requires:\n\n- Plane ownership map, target topology, authority statement:\n  [references\u002Ftopology.md](references\u002Ftopology.md)\n- Evidence JSON shape, status vocabulary, evidence-vs-assumption rule,\n  release-readiness gating: [references\u002Fevidence-schema.md](references\u002Fevidence-schema.md)\n- Deterministic evidence collector (wraps `tools\u002Fcontrol-plane\u002Fverify.mjs`):\n  [scripts\u002Frun-checks.mjs](scripts\u002Frun-checks.mjs)\n- Underlying cross-runtime verifier (not owned by this skill — read, don't\n  fork it): `tools\u002Fcontrol-plane\u002Fverify.mjs`\n- Full migration contract this skill operationalizes:\n  `docs\u002Fcontrol-plane\u002FMIGRATION_CONTRACT.md`\n- Point-in-time baseline the contract was derived from:\n  `docs\u002Fcontrol-plane\u002FCURRENT_STATE.md`\n\nBefore treating this skill itself as validated after an edit, run:\n\n```bash\nnode .agents\u002Fskills\u002Fcontrol-plane-validation\u002Fscripts\u002Frun-checks.mjs\nnode tools\u002Fcontrol-plane\u002Fverify.mjs\n```\n\nand confirm the `agents-skills:control-plane-validation` check reports\nPASS (valid `name`\u002F`description` frontmatter) and that neither run reports\nthis skill's own files as `.gitignore`-hidden. Only report **Done &\nVerified** when that fresh run backs the claim — not this file's own\nmemory of a prior run.\n","# Control Plane Validation\n\n## Contents\n\n1. Objective\n2. Authority statement (non-negotiable)\n3. Trigger scope\n4. Workflow\n5. Owning-plane classification\n6. Evidence and status vocabulary\n7. Failure handling\n8. Resources\n\n## 1. Objective\n\nProve — with fresh, on-disk evidence — that a change touching this\nrepository's control plane is structurally sound and correctly scoped,\nwithout ever implying that a passing check authorizes shipping it. This\nskill produces a validation report; it does not implement fixes, and it\nnever pushes, merges, or deploys.\n\nThe default deliverable is:\n\n- a Git baseline (branch, HEAD, dirty-state inventory);\n- a per-path plane classification for every changed file;\n- a Codex-docs drift check for any changed Codex-native file format;\n- a `tools\u002Fcontrol-plane\u002Fverify.mjs` run;\n- syntax\u002Funit-test evidence for changed scripts;\n- a `git diff --check` inspection;\n- an exact diff-scope report;\n- an explicit evidence-vs-assumption breakdown;\n- a release-readiness statement that is blocked, not guessed, when\n  required checks are unavailable.\n\n## 2. Authority statement (non-negotiable)\n\nState these explicitly in every report this skill produces, not just once\nat skill-authoring time:\n\n- **Skills are workflow knowledge, not permission grants.** This skill\n  tells you *how* to validate a control-plane change once you are already\n  permitted to look at and edit those files. It does not itself authorize\n  any tool call, write, commit, or publication.\n- **Hooks are guardrails, not complete authorization.** A hook firing (or\n  not firing) is not proof that an action is safe or approved.\n- **Tests passing does not authorize push, merge, or deploy.** A green\n  `tools\u002Fcontrol-plane\u002Fverify.mjs` run, a green Biome check, or a green\n  `node --test` run is evidence (§1.11 of the migration contract), not\n  approval (§1.5). Approval is a separate, human act.\n- **`main` publication triggers Netlify production.** Merging to `main` is\n  an automatic, public production deploy with no separate gate\n  (`netlify.toml` has no branch\u002Fcontext restriction). Treat it with\n  release-action weight every time, regardless of what this skill reports.\n\nFull rationale: [references\u002Ftopology.md](references\u002Ftopology.md), \"Authority\nstatement\" section.\n\n## 3. Trigger scope\n\nRun this skill when a task touches any of:\n\n- `AGENTS.md`, `.agents\u002F**`, `.codex\u002F**`, `.claude\u002F**`;\n- `tools\u002Fcontrol-plane\u002F**` (the verifier itself);\n- CI governance: `.github\u002Fworkflows\u002F**`;\n- production-policy documentation: `docs\u002Fcontrol-plane\u002F**`, `netlify.toml`;\n- `security\u002Fconstitution.md` (machine-readable security invariants that\n  `AGENTS.md` restates in prose).\n\nIf the task touches none of these, this skill does not apply — do not run\nit defensively on unrelated product-code changes.\n\n## 4. Workflow\n\nCopy and maintain this checklist for the current change:\n\n```text\nControl Plane Validation Progress\n- [ ] 1. Establish Git baseline and dirty state\n- [ ] 2. Identify owning plane for each changed path\n- [ ] 3. Check current official Codex docs for format drift (if applicable)\n- [ ] 4. Run tools\u002Fcontrol-plane\u002Fverify.mjs\n- [ ] 5. Run syntax\u002Funit tests for changed scripts\n- [ ] 6. Inspect git diff --check\n- [ ] 7. Report exact diff scope\n- [ ] 8. Distinguish tested evidence from assumptions\n- [ ] 9. State release-readiness honestly (block the claim if unverifiable)\n```\n\n### Step 1: Git baseline and dirty state\n\nDo not trust a prior summary, `.planning\u002F**` artifact, or this skill's own\nreference files for current state — re-derive it:\n\n```bash\ngit status --porcelain=v1\ngit rev-parse HEAD\ngit rev-parse --abbrev-ref HEAD\n```\n\nOr let the bundled script do it (see Step 4 — it captures the same baseline\nas part of one evidence object).\n\n### Step 2: Identify owning plane for each changed path\n\nClassify every changed path against\n[references\u002Ftopology.md](references\u002Ftopology.md)'s plane map. A path that\nmatches no row is out of this skill's scope — note it, do not force-fit a\nplane onto it. Watch specifically for a single diff that touches two planes\nin a way that collapses their separation (e.g. a rule file edit that also\nadds executable logic, or a skill edit that also changes a permission\nallowlist) — that is exactly the failure mode\n`docs\u002Fcontrol-plane\u002FMIGRATION_CONTRACT.md` §3.3 calls out, and it is a\nfinding to surface, not silently pass through.\n\n`scripts\u002Frun-checks.mjs` (Step 4) performs this classification\nautomatically and includes it in its JSON output under `diffScope`.\n\n### Step 3: Check current official Codex docs for format drift\n\nOnly required when the diff touches a Codex-native file format:\n`.codex\u002Fconfig.toml`, `.codex\u002Fhooks.json`, `.codex\u002Frules\u002F*.rules`,\n`.codex\u002Fagents\u002F*.toml`, or `.codex\u002Fworkflows\u002F**`. `tools\u002Fcontrol-plane\u002Fverify.mjs`\nvalidates these files against this repository's *current understanding* of\ntheir grammar (see its embedded TOML\u002Fexecpolicy parsers) — it cannot detect\nthat Codex CLI's actual contract for one of these formats changed upstream.\n\nWhen applicable, fetch the current official Codex CLI documentation for the\nspecific format(s) touched and compare against what\n`tools\u002Fcontrol-plane\u002Fverify.mjs` currently enforces. If network access is\nunavailable, do not silently skip this — record it as **UNVERIFIED** (see\n[references\u002Fevidence-schema.md](references\u002Fevidence-schema.md)) and carry\nthat into Step 9's release-readiness statement.\n\nWhen not applicable (the diff doesn't touch a Codex-native format), record\nthat this step was correctly skipped and why — do not spend a network call\nproving a negative.\n\n### Step 4: Run `tools\u002Fcontrol-plane\u002Fverify.mjs`\n\nRun the bundled deterministic script, which wraps `verify.mjs` and adds\nSteps 1, 2, 6, and 7 of this workflow in one evidence object:\n\n```bash\nnode .agents\u002Fskills\u002Fcontrol-plane-validation\u002Fscripts\u002Frun-checks.mjs\n```\n\nOr run the verifier directly if you only need its own checks:\n\n```bash\nnode tools\u002Fcontrol-plane\u002Fverify.mjs\n```\n\nRead every FAIL, including non-authoritative\u002Finformational ones (the\nClaude-compatibility check is informational by design — see\n`tools\u002Fcontrol-plane\u002Fverify.mjs`'s own comments — but still worth reporting\nif it fails). Never treat a SKIPPED check as a PASS.\n\n### Step 5: Run syntax\u002Funit tests for changed scripts\n\n`scripts\u002Frun-checks.mjs` syntax-checks (`node --check`) every changed\n`.js`\u002F`.mjs`\u002F`.cjs` file inside a recognized control-plane plane and reports\nthe results under `syntaxCheck`. This proves the file parses — it is not a\nsubstitute for running its actual tests. Separately:\n\n- if the change touches `tools\u002Fcontrol-plane\u002Fverify.mjs` or anything it\n  imports, also run whatever test suite currently covers it (check\n  `tests\u002FAGENTS.md` and `tests\u002Fsecurity\u002F` for a matching file — e.g.\n  `tests\u002Fsecurity\u002Fcodex-config.test.mjs` covers `.codex\u002Fconfig.toml`\n  parseability);\n- if no test currently covers a changed control-plane script, say so\n  explicitly rather than reporting untested code as verified.\n\n### Step 6: Inspect `git diff --check`\n\n```bash\ngit diff --check\ngit diff --cached --check\n```\n\n`scripts\u002Frun-checks.mjs` runs both and classifies the result: real conflict\nmarkers (`\u003C\u003C\u003C\u003C\u003C\u003C\u003C`, `=======`, `>>>>>>>` at line start) are an authoritative\nfailure; trailing-whitespace-only findings are informational (this\nrepository has a known pre-existing trailing-whitespace finding in\n`.repository-hygiene\u002Freport.md` — do not treat that class of finding as\nblocking by default, but do report it).\n\n### Step 7: Report exact diff scope\n\nState precisely which paths changed, their Git status code, and their\nplane — not a paraphrase (\"some control-plane files changed\"). Use\n`diffScope.byPlane` from the script output directly; it is already grouped\ncorrectly. Call out `outOfScopeCount` if non-zero so the reader knows the\nreport is deliberately narrowed to control-plane paths, not silently\nincomplete.\n\n### Step 8: Distinguish tested evidence from assumptions\n\nApply [references\u002Fevidence-schema.md](references\u002Fevidence-schema.md)'s\nevidence-vs-assumption rule to every claim in the report: a claim is\n**evidence** only if it is backed by this session's own script\u002Ftool output\nor a freshly fetched doc; anything sourced from\n`docs\u002Fcontrol-plane\u002FCURRENT_STATE.md`, `MIGRATION_CONTRACT.md`, a prior\nsummary, or this skill's own reference files is a **hypothesis** until\nre-confirmed in this session.\n\n### Step 9: State release-readiness honestly\n\nFollow [references\u002Fevidence-schema.md](references\u002Fevidence-schema.md)'s\n\"Blocking a release-ready claim\" section. In particular: if Step 3 was\nrequired and could not be performed, or `tools\u002Fcontrol-plane\u002Fverify.mjs`\ncould not run at all, do not say the change is \"ready\" — say what is\nunverified and why, plainly, in the same report.\n\n## 5. Owning-plane classification\n\nFull plane map, target topology, and authority statement:\n[references\u002Ftopology.md](references\u002Ftopology.md).\n\n## 6. Evidence and status vocabulary\n\nFull JSON shape for `scripts\u002Frun-checks.mjs`, the PASS\u002FFAIL\u002FSKIPPED\u002FUNVERIFIED\nvocabulary, and the evidence-vs-assumption rule:\n[references\u002Fevidence-schema.md](references\u002Fevidence-schema.md).\n\n## 7. Failure handling\n\n- `tools\u002Fcontrol-plane\u002Fverify.mjs` fails to load or throws: report it as a\n  tool failure (not a SKIPPED sub-check) and block any release-readiness\n  claim — do not fall back to reasoning about control-plane correctness\n  from memory.\n- Codex docs are unreachable for Step 3: mark that specific claim\n  UNVERIFIED, do not treat the rest of the report as invalidated, and do\n  not silently drop the step from the checklist.\n- A changed path does not match any plane rule: report it explicitly as\n  unclassified rather than guessing a plane or omitting it from the diff\n  scope.\n- `git diff --check` reports real conflict markers: stop and resolve them\n  before any further validation — a diff with conflict markers is not in a\n  reviewable state.\n- No test currently covers a changed control-plane script: report that gap\n  by name; do not report the script as verified because it parses.\n\n## 8. Resources\n\nLoad only what the current step requires:\n\n- Plane ownership map, target topology, authority statement:\n  [references\u002Ftopology.md](references\u002Ftopology.md)\n- Evidence JSON shape, status vocabulary, evidence-vs-assumption rule,\n  release-readiness gating: [references\u002Fevidence-schema.md](references\u002Fevidence-schema.md)\n- Deterministic evidence collector (wraps `tools\u002Fcontrol-plane\u002Fverify.mjs`):\n  [scripts\u002Frun-checks.mjs](scripts\u002Frun-checks.mjs)\n- Underlying cross-runtime verifier (not owned by this skill — read, don't\n  fork it): `tools\u002Fcontrol-plane\u002Fverify.mjs`\n- Full migration contract this skill operationalizes:\n  `docs\u002Fcontrol-plane\u002FMIGRATION_CONTRACT.md`\n- Point-in-time baseline the contract was derived from:\n  `docs\u002Fcontrol-plane\u002FCURRENT_STATE.md`\n\nBefore treating this skill itself as validated after an edit, run:\n\n```bash\nnode .agents\u002Fskills\u002Fcontrol-plane-validation\u002Fscripts\u002Frun-checks.mjs\nnode tools\u002Fcontrol-plane\u002Fverify.mjs\n```\n\nand confirm the `agents-skills:control-plane-validation` check reports\nPASS (valid `name`\u002F`description` frontmatter) and that neither run reports\nthis skill's own files as `.gitignore`-hidden. Only report **Done &\nVerified** when that fresh run backs the claim — not this file's own\nmemory of a prior run.\n",{"name":5,"description":7},"main","a5bed13dcca926e006d2681d548e722fffa499ab",".agents\u002Fskills\u002Fcontrol-plane-validation","https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat","https:\u002F\u002Fgithub.com\u002FJackSmack1971","2026-10-02 05:58:57",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add JackSmack1971\u002Ffreeforge-chat --skill control-plane-validation",{"tool":35,"command":36},"bunx","bunx skills add JackSmack1971\u002Ffreeforge-chat --skill control-plane-validation",{"tool":38,"command":39},"pnpm","pnpm dlx skills add JackSmack1971\u002Ffreeforge-chat --skill control-plane-validation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcontrol-plane-validation\u002FSKILL.md",true,[43,49,53],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fevidence-schema.md","REFERENCE","参考文档",5070,"https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcontrol-plane-validation\u002Freferences\u002Fevidence-schema.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Ftopology.md",7008,"https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcontrol-plane-validation\u002Freferences\u002Ftopology.md",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"scripts\u002Frun-checks.mjs","SCRIPT","脚本",11847,"https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcontrol-plane-validation\u002Fscripts\u002Frun-checks.mjs",[60,67,73,78,83,88],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7596K2F59EBMTV0GEA7G1DF","sample","Fixture skill.","https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002Ftests\u002Fcontrol-plane\u002Ffixtures\u002Fsnapshot-good\u002F.agents\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":68,"name":62,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7596HMJGJCK6C1BBBP6YFWM","A minimal fixture skill used only to exercise the verifier.","https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002Ftests\u002Fcontrol-plane\u002Ffixtures\u002Fmalformed\u002Fwriter-configured-read-only\u002F.agents\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":74,"name":62,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7596FVEYPJ99D4XJZZ07HB1","https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002Ftests\u002Fcontrol-plane\u002Ffixtures\u002Fmalformed\u002Fstale-identifier-under-codex\u002F.agents\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":79,"name":62,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7596ECKJNJE0G09SFTENYTW","https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002Ftests\u002Fcontrol-plane\u002Ffixtures\u002Fmalformed\u002Freviewer-configured-write-enabled\u002F.agents\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":84,"name":62,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7596BMRAMMD4P3MW4N25ZAV","https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002Ftests\u002Fcontrol-plane\u002Ffixtures\u002Fmalformed\u002Fno-rules-dir\u002F.agents\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":89,"name":62,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M759695BRBKRSK4KDY4VCFR4","https:\u002F\u002Fgithub.com\u002FJackSmack1971\u002Ffreeforge-chat\u002Fblob\u002Fmain\u002Ftests\u002Fcontrol-plane\u002Ffixtures\u002Fmalformed\u002Fmissing-skill-md\u002F.agents\u002Fskills\u002Fsample\u002FSKILL.md",[],[]]