docs: reconcile the ADRs, gates and audit log with the shipped behaviour

Why

A six-agent review of the two preceding commits found their code sound -- the
differential claim holds, the published hook contract is byte-unchanged -- but
their prose drifted from it in three ways: statements of fact the code
contradicts, markers in a convention this repo does not use, and figures that
went stale when the merge changed what they counted.

Implementation Notes

ADR-0025's edge-path table is rewritten around one stated doctrine: 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. Its old row 1 promised "one
generic matches-neither message" for three different inputs; there are three
distinct messages, and the missing-path case exited 1 until the preceding commit
fixed it. Rows are added for the preflight and CDPATH changes, because a table
claiming to enumerate every entry-point behaviour change reproduces its own
"an earlier revision of this ADR said they were behaviour-neutral" failure if it
omits any.

ADR-0025 also gains a Consequences supersession record in ADR-0016's form:
partially-superseded entries for 0008, 0014, 0020 and 0021, and explicit
"is not superseded" entries with reasoning for the rest. Twelve ADRs are amended
and it previously listed none.

ADR-0008 moves from an amendment note to partially superseded. Its contract
genuinely narrowed -- an agent .md outside an agents/ directory was audited
before the merge and is refused now -- and ADR-0020 already recorded that the
merge "reopens ADR-0008". Its detector description said "a path under
.apm/agents/", the phrasing ADR-0025 rejects as wider than the script and
circular; the shipped rule is a .md whose immediate parent is named agents/, at
any scope.

ADR-0020's amendment claimed the boundary resolver is sourced by
validate-provenance.sh. It is not, and never was; only validate.sh sources it,
once per mode branch. Three Home-column entries pointed at reference filenames
the merge renamed, one of which now resolves to two files because its row covers
skills and agents.

Five ADRs opened with "Skill renamed per ADR-0025", a form this repo does not
use, in the same commit that used the conventional "Amended by ADR-0025" twice.
They are normalized. "Renamed" was also wrong: the BREAKING-CHANGE trailer says
the skills were removed and their flows merged.

SIMPLIFICATION-AUDIT.md had 2026-09-15 notes attached to headlines that were
never updated, against its own convention of correcting in place with
strikethrough. Every figure here was re-derived at HEAD by command, and several
differed from the review's own numbers, so the notes record the basis rather
than the result alone.

LESSONS.md asserted the two review-time suite failures were the SIGPIPE race.
The commit that fixed that race explicitly declined to claim it -- the suite was
running while agents edited live config files -- so the hedge is restored.

Impact

No code, test or configuration change; documentation only. Suites stay 20/20
strict with 0 skipped and 374/374 bats. No gate parses ADR or gates.md content,
so nothing here is load-bearing for a hook.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YR2CjVumUbEGWcMikcoXBD

docs/adr/0020-skill-description-and-body-context-contract.md

@@ -17,7 +17,9 @@ three: `scripts/skill-size-check.sh`, `skill-audit/scripts/validate.sh` and
 `scripts/skill-size-check.sh`, which still embeds the 1,061-line block between `BEGIN`/`END ADR-0020
 SHARED BOUNDARY RESOLVER` markers, and one plugin copy — extracted out of the merged validator into
 `plugins/kyberforge/.apm/skills/factory-audit/scripts/lib-boundary-resolver.sh` and sourced by
-`factory-audit`'s `validate.sh` and `validate-provenance.sh` rather than pasted into each. The
+`factory-audit`'s `validate.sh`, once in each of its two mode branches, rather than pasted into
+both. `validate-provenance.sh` is not a third reader: it sources `lib-contributing-files.sh` and one
+of `lib-provenance-skill.sh`/`lib-provenance-agent.sh`, and never touches the resolver at all. The
 Enforcement table's "constants mirrored in `skill-audit/scripts/validate.sh` and
 `agent-audit/scripts/validate.sh`" is one path now, `factory-audit/scripts/validate.sh`, which
 auto-detects the artifact type; the skills/agents columns are unaffected, since the merged validator
@@ -275,7 +277,7 @@ which tier each rule is in, because the failure this ADR is most exposed to is a
 | Check | Applies to | Tier | Home |
 |---|---|---|---|
 | description characters (250 SUGGESTION † / 400 FAIL) | skills, agents | deterministic | `scripts/skill-size-check.sh`; constants mirrored in `skill-audit/scripts/validate.sh` and `agent-audit/scripts/validate.sh` |
-| body-only words (600 SUGGESTION / 900 FAIL) | skills | deterministic | `skill-size-check.sh`, `skill-audit/scripts/validate.sh` |
+| body-only words (600 SUGGESTION / 900 FAIL) | skills | deterministic | `skill-size-check.sh`, `skill-audit/scripts/validate.sh` (now `factory-audit/scripts/validate.sh`, see ADR-0025) |
 | description present and non-empty (ERROR) | skills, agents | deterministic | same |
 | boundary target resolves to a real skill or agent — **three** verdicts, not two (ERROR when written in route notation — `/name`, or any arrow form; or when a *terminal* bare name's own sentence names another target that resolves. SUGGESTION otherwise. INFO, "DID NOT RUN", exit 0, when no skill universe could be determined for the path at all — no authoring root above it, no apm package root, no declared apm dependencies, no deployed `.claude/` or `.agents/` tree: the targets are named and left unchecked) | skills, agents | deterministic | same |
 | boundary clause absent — `absent` (SUGGESTION) † | skills, agents | deterministic | same |
@@ -285,10 +287,10 @@ which tier each rule is in, because the failure this ADR is most exposed to is a
 | Gotchas over 25% of the body (SUGGESTION) | skills | deterministic | same |
 | every `references/<file>.md` a body names exists (ERROR) | skills | deterministic | same |
 | description opener, composition notes in a description | skills, agents | prose pattern | `plugins/kyberforge/.apm/skills/*/assets/vale/styles/Kyberforge/` |
-| a Gotcha paraphrasing a body step | skills | **auditor judgment** | `references/body-discipline.md` |
-| dispatch at two or more mutually exclusive flows | skills | **auditor judgment** | `references/body-discipline.md` |
+| a Gotcha paraphrasing a body step | skills | **auditor judgment** | `references/body-discipline.md` (now `references/skill-body-discipline.md`, see ADR-0025) |
+| dispatch at two or more mutually exclusive flows | skills | **auditor judgment** | `references/body-discipline.md` (now `references/skill-body-discipline.md`, see ADR-0025) |
 | delegation: an agent body restating a skill's procedure | agents | **auditor judgment** | `agent-audit` (now `factory-audit`'s agent flow, see ADR-0025) |
-| capability enumeration, restatement, trigger quality | skills, agents | **auditor judgment** | `references/description-quality.md` |
+| capability enumeration, restatement, trigger quality | skills, agents | **auditor judgment** | `references/description-quality.md` (now two files, `references/skill-description-quality.md` and `references/agent-description-quality.md`, see ADR-0025 — this row applies to both artifact types, and the merge splits every flow-specific reference by flow) |
 
 The rows in bold are stated as FAILs in the Decision above and are FAILs an *auditor* issues. None of
 them is countable: "does this Gotcha paraphrase step 4", "are these two flows mutually exclusive" and
@@ -524,7 +526,8 @@ Upstream citations below are relative to
   growth. Would have made the retrofit a visible burn-down instead of a wall. Rejected in favour of
   hot gates.
 - **A sync gate over the duplicated spans** instead of a merge rule — generalising
-  `scripts/check-vale-style-sync.sh` to cover shared prose so duplication persists but drift cannot.
+  `scripts/check-vale-style-sync.sh` (live when this was written; ADR-0025 deleted it along with the
+  second copy it diffed) to cover shared prose so duplication persists but drift cannot.
   Rejected for the audit pair in favour of merging, which removes the duplication rather than
   policing it, and removes a mutually-excluding near-miss pair from the router at the same time. It
   remains the only available answer for the author pair.