refactor(kyberforge)!: merge skill-audit and agent-audit into factory-audit

Why

The two audit skills carried 1,724 lines of byte-identical duplication: the ADR-0020 boundary
resolver (1,061), vale-wrap.sh (526), the Vale style rules (44) and the Contributing-files parser
(93). Nothing shared them — they were held in sync by a 413-line pre-push gate and its 797-line
test suite. Sync-by-gate had already failed once: at 484357a the two parser copies drifted into
different spellings of the bullet loop while a docstring asserted they were identical. That drift
was behaviour-neutral and was re-unified by hand at 598a7c3, so the copies were identical at merge
time — but nothing had caught it, and the next drift need not be neutral.

Implementation Notes

Self-containment binds BETWEEN skills, not within one. The agentskills.io spec forbids reaching
across skill directories, which is why two separate skills needed embedded copies; two files inside
ONE skill may source a third. That is the whole reason the merge removes duplication rather than
relocating it.

The union of both bodies measured 1,532 words against BODY_MAX_WORDS=900, and only 211 of those
words were shared, so SKILL.md is a dispatch body. Step 0 resolves the flow from the target path
before any validation, and its table mirrors validate.sh's detection exactly: a directory holding
SKILL.md or a SKILL.md file (skill); a *.agent.md, or a .md directly under an agents/ directory
(agent); anything else stops without running a validator. Steps 1-3 live in
references/skill-flow.md and references/agent-flow.md, and gotchas that apply to one flow live in
that flow's file, since it is loaded on every invocation anyway. If validate.sh reports on the
other artifact type, the body restarts at Step 0.

Named factory-audit rather than forge-audit because forge is a live skill, and a family prefix that
matches a live sibling reads as ownership rather than membership.

The description carries one arrow per boundary target, because ADR-0020 resolves only the first
target after an arrow. It drops the quoted "audit this skill"-style phrases, which restated
"audited" in a second register (ADR-0020's duplicate-register rule). 241 characters, Gotchas 16%
of the body: no size SUGGESTIONs.

The boundary resolver stays embedded in two files rather than imported: a cache-installed plugin
cannot read outside its own directory, and the repo-root hook resolves via .pre-commit-hooks.yaml
where entry[0] is the only token pre-commit rewrites, so no single file is reachable by both.
tests/test-adr0020-contract.sh hashes both copies for byte-identity, and asserts validate.sh sources
the resolver and that no third copy exists.

The entry scripts classify the target from its resolved parent directory, so a bare agent filename
typed inside agents/ works; resolve SCRIPT_DIR CDPATH-safely; and exit 2 when a lib-*.sh is
missing, rather than dying with exit 1, the tier the flows relay as real findings.

The provenance run functions stash their findings code in KYBERFORGE_PROV_RC and
return 0, so validate-provenance.sh calls them UNTESTED. Testing a function's
status (`f || RC=$?`) disables errexit for its entire body, and no subshell or
`set -e` inside can re-arm it once the call sits in a condition context
(measured, both spellings). Their error paths use `exit`, which is unaffected
either way; this keeps errexit armed for anything added later.

Case 0's readability guard reads the file instead of asking `[[ -r ]]`. `-r` is
access(2), which answers yes for uid 0 even on a mode-000 file, and this repo's
dev environment is root -- so the guard could never fire where it exists to fire.
A read attempt is also the stricter question, catching EIO. This is the reasoning
scripts/check-vale-style-sync.sh carried before this commit deleted it; the
hazard did not go with it.

All three entry scripts are CDPATH-safe, vale-wrap.sh included: both of its cd sites are cleared,
the --config resolution and the directory-mirror walk, where an exported CDPATH would otherwise
print a decoy path into the -print0 stream and build the mirror from the decoy's files. The two
remaining bare cd calls take absolute paths, which CDPATH is never consulted for.

Impact

BREAKING: skill-audit and agent-audit no longer exist as invocable skills. kyberforge goes to
2.0.0 (catalog 0.4.7).

Check logic is unchanged: differential runs of the old and new validators across every skill and
agent produced byte-identical stdout, stderr and exit codes, and the reconstructed Python payloads
differ only in comments and the references/field-inventory.md -> agent-field-inventory.md rename.
One doctrine governs the tiers: exit 0 is audited and clean, exit 1 is audited with findings OR a
target present but unreadable, exit 2 is that nothing was audited at all. Edge paths DID change,
deliberately (full table in ADR-0025):
- a missing target exits 2 (never ran), not 1, under its own "does not exist" message; detection is
  by path shape, so a shape-matching path that is simply absent used to reach the validator and come
  back as a FAIL against a file that never existed;
- an unshaped target exits 2 under the generic "matches neither" message, and a directory with no
  SKILL.md under a third, distinct one -- three exit-2 messages, not one;
- a dangling symlink or a symlink loop stays exit 1: it is present but broken, which is a finding
  about the artifact rather than a usage error;
- a SKILL.md file path is audited as its skill directory instead of refused;
- a .md agent outside an agents/ directory is refused rather than audited;
- a missing script library, a missing python3, a missing PyYAML, and no argument at all each exit 2.
  validate-provenance.sh already exited 2 for the last two; validate.sh now matches it.

.pre-commit-hooks.yaml is a published contract consumed by external repos. Both hook IDs and both
files: regexes are unchanged; only entry: and description: moved.

scripts/check-vale-style-sync.sh (413), scripts/sync-vale-styles.sh (21),
tests/test-check-vale-style-sync.sh (797) and agent-audit/scripts/README.md (47) are deleted. The
checker made 17 assertions: 6 compared the two Vale copies and are moot; 10 are rehomed into
tests/test-vale-wrap.sh (case 0, cases 28-31, and the suite's Vale-absent skip); and the
cross-manifest files: agreement check, which selected hooks by entry: and so could not survive both
hooks sharing one, is ported as case 33 pairing hooks by id:. Cases 28, 30 and 33 carry mutation
self-tests; narrowing the local skill prefilter to 6 of 38 SKILL.md files now fails the suite.

Skills go 39 to 38. Pre-push goes 9 repo-authored hooks to 8.

ADR: 0025
BREAKING-CHANGE: the skill-audit and agent-audit skills are removed. Both flows are served by
  factory-audit, which auto-detects whether it was handed a skill directory or an agent file.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YR2CjVumUbEGWcMikcoXBD

plugins/kyberforge/.apm/skills/agent-author/references/contract.md

@@ -7,7 +7,7 @@ source_keys:
 # The agent description and body contract
 
 House contract. The counts and the boundary targets are enforced by
-`agent-audit`'s `scripts/validate.sh`; the prose patterns by the Vale styles it bundles; the
+`factory-audit`'s `scripts/validate.sh`; the prose patterns by the Vale styles it bundles; the
 judgment calls by its reference files.
 
 ## Why the budget exists
@@ -54,7 +54,7 @@ appear depends on the file:
 | Vendor-neutral `.apm/agents/<name>.agent.md` (plugin/APM scope) | **Never.** Same Vale rule, same hard FAIL — the file matches the `**/*.agent.md` glob, and it compiles to a real Copilot agent downstream. |
 
 A pair whose Claude Code half carries the phrase and whose Copilot half omits it is correct, not
-inconsistent: `agent-audit` checks that both halves describe the same job, not that they match
+inconsistent: `factory-audit` checks that both halves describe the same job, not that they match
 word for word.
 
 Indirect triggers ("even if the user doesn't say X") take a similar conditional at every scope:
@@ -126,7 +126,7 @@ One job per agent. An agent covering two jobs gets delegated to for the wrong on
 **Delegation discipline replaces the word gate.** A plugin/APM agent is a single file with no
 sibling `references/` directory: it cannot disclose progressively to itself, so its only way to
 stay short is to *invoke* rather than *restate*. A body that transcribes a procedure a skill it
-can invoke already owns is an `agent-audit` FAIL, and the fix is one line — "invoke `<skill>`".
+can invoke already owns is a `factory-audit` FAIL, and the fix is one line — "invoke `<skill>`".
 
 - Restating: "To commit, check the message against Conventional Commits: type, scope,
   description; header under 100 chars; …"

plugins/kyberforge/.apm/skills/agent-author/references/create.md

@@ -22,7 +22,7 @@ Before touching the filesystem, confirm you have:
 
 If any are missing, stop and ask before proceeding.
 
-`agent-audit` runs the validation in `SKILL.md` Step 4. It ships with the kyberforge plugin and
+`factory-audit` runs the validation in `SKILL.md` Step 4. It ships with the kyberforge plugin and
 is co-installed with this skill; if it is unavailable, stop and ask the user to install
 kyberforge before continuing.
 

plugins/kyberforge/.apm/skills/agent-author/references/deployment-modes.md

@@ -27,7 +27,7 @@ When the same agent `name` appears at multiple scopes, **user scope wins over pr
 Field rules are per scope and live with the scope: `references/plugin-scope.md` for the single
 vendor-neutral file, `references/project-user-scope.md` for the Claude Code / Copilot pair. Read
 one, not both. The short version is that plugin/APM frontmatter is an allowlist read from
-`agent-audit`'s `references/field-inventory.md`, narrow because `apm compile` copies frontmatter
+`factory-audit`'s `references/agent-field-inventory.md`, narrow because `apm compile` copies frontmatter
 verbatim to every target (ADR-0016), while project and user scope carry the full per-provider
 field sets.
 

plugins/kyberforge/.apm/skills/agent-author/references/improve.md

@@ -14,9 +14,9 @@ Confirm the agent file (or, at project and user scope, the pair) exists and that
 improvement signal is present in the conversation or in a referenced file.
 
 If no signals are present, stop: "This skill applies existing signals to an agent. For a blind
-review, run `agent-audit` instead."
+review, run `factory-audit` instead."
 
-`agent-audit` runs the validation in `SKILL.md` Step 4 and is co-installed with this skill; if
+`factory-audit` runs the validation in `SKILL.md` Step 4 and is co-installed with this skill; if
 it is unavailable, stop and ask the user to install the kyberforge plugin before continuing.
 
 **Partial pair — project and user scope only.** If one provider file exists and the other does
@@ -53,7 +53,7 @@ Edit whichever file the signals point to.
 scoped to the cases you have seen overfits and performs worse on new input.
 
 **Delegate rather than grow.** An agent body has no word ceiling, but a body that restates a
-procedure a skill it can invoke already owns is an `agent-audit` FAIL. When a signal reports a
+procedure a skill it can invoke already owns is a `factory-audit` FAIL. When a signal reports a
 missing procedure, check first whether an installed skill owns it and name that skill instead of
 transcribing it. See `references/contract.md`.
 
@@ -81,7 +81,7 @@ the matching `sources.md` entry — the create flow's Step 3 has the rules.
 
 **Check for regressions before handing back.** `SKILL.md` Step 4 tells you to resolve every FAIL,
 which says nothing about a check that passed *before* these edits and no longer does. Compare the
-closing `agent-audit` against the agent's pre-edit state — a PASS that has become a SUGGESTION, or
+closing `factory-audit` against the agent's pre-edit state — a PASS that has become a SUGGESTION, or
 a SUGGESTION that has become a FAIL, is damage this flow caused and is in scope for it. Only the
 improve flow can make that comparison; the create flow has no prior state to compare against.
 

plugins/kyberforge/.apm/skills/agent-author/references/plugin-scope.md

@@ -12,9 +12,9 @@ a Copilot marker — the file is vendor-neutral.
 
 ## Frontmatter
 
-The permitted keys are the `apm-agent-allowlist` section of `agent-audit`'s
-`references/field-inventory.md`. Read them from there as data — that section is the single source
-of truth, `agent-audit`'s `validate.sh` parses it at load time, and it changes. Any restatement of
+The permitted keys are the `apm-agent-allowlist` section of `factory-audit`'s
+`references/agent-field-inventory.md`. Read them from there as data — that section is the single source
+of truth, `factory-audit`'s `validate.sh` parses it at load time, and it changes. Any restatement of
 the roster, here or in a template or in script output, goes stale one step further out than the
 list itself.
 
@@ -60,7 +60,7 @@ when research sources informed the agent, with slugs matching H2 headings in the
 Follow the Body section of `references/contract.md`: role instruction, one job, and delegation
 to installed skills instead of transcribed procedure.
 
-## Before invoking `agent-audit`
+## Before invoking `factory-audit`
 
 - [ ] `name` kebab-case, matching the filename stem, unique in scope
 - [ ] `description` written to `references/contract.md`

plugins/kyberforge/.apm/skills/agent-author/references/project-user-scope.md

@@ -92,7 +92,7 @@ Both formats truncate a body past **30,000 characters** silently.
 Copilot has no `permissionMode`, `maxTurns`, `isolation`, `memory`, `effort`, `hooks` or
 `mcpServers`. Never let those cross over from the Claude Code file.
 
-## Before invoking `agent-audit`
+## Before invoking `factory-audit`
 
 Both files:
 

plugins/kyberforge/.apm/skills/agent-author/references/scripts.md

@@ -15,7 +15,7 @@ All scripts in this skill must follow these rules:
 - **Idempotent** — "create if not exists" per file. The scaffold script skips any file that already exists; agents may safely re-run it.
 - **Meaningful exit codes** — `0` success, `1` invalid arguments or precondition failure. Document in `--help`.
 - **Self-contained** — no external package installs at runtime. The script uses only bash builtins and POSIX tools (`sed`, `mkdir`, `cat`).
-- **No restated field rosters** — no script output, in `--help` or in next-steps guidance, enumerates permitted, forbidden, or required frontmatter fields. Point at the `apm-agent-allowlist` section of `agent-audit`'s `references/field-inventory.md`, which `agent-audit`'s `validate.sh` reads from there as data. A roster copied into script output goes stale one step further out than the list itself: the next-steps hint `(name, description, model, body only)` kept printing after ADR-0016's 2026-08-14 amendment added `disallowedTools` to the permitted set. `tests/new-agent.bats` enforces this for the plugin/APM branch — naming some allowlisted fields but not all is a failure.
+- **No restated field rosters** — no script output, in `--help` or in next-steps guidance, enumerates permitted, forbidden, or required frontmatter fields. Point at the `apm-agent-allowlist` section of `factory-audit`'s `references/agent-field-inventory.md`, which `factory-audit`'s `validate.sh` reads from there as data. A roster copied into script output goes stale one step further out than the list itself: the next-steps hint `(name, description, model, body only)` kept printing after ADR-0016's 2026-08-14 amendment added `disallowedTools` to the permitted set. `tests/new-agent.bats` enforces this for the plugin/APM branch — naming some allowlisted fields but not all is a failure.
 
 ## Template variables