docs: close the PR #135 documentation review findings

Group 3 of the validated PR #135 review fixes. Every figure and commit
citation below was re-verified at HEAD before being written.

ADR and architecture:
- #7 ADR-0025 cited 61b0b9c, which no published branch reaches. Repointed
  to 620f20b (identical parent tree, reachable from the PR branch), with a
  note that neither is reachable from origin/main. The parser-drift
  paragraph now credits 598a7c3 (the reachable PR #129 squash) and keeps
  484357a only as a pre-squash parenthetical.
- #8 architecture.md dropped the pointer at the LESSONS.md entry this
  branch deleted.
- #9 architecture.md's ADR entry points now name ADR-0015 (the one
  compiler) and ADR-0024, and list ADR-0024 as superseding ADR-0017.
- #10 ADR-0024 section 4 rewritten: the standing patch-bump rule is
  apm-workflow's configure.md, not ADR-0006's, and this change does not
  trigger it. ADR-0015:93 carries a correction for the misattribution.
- N5 ADR-0021 gained a Correction note for the deleted
  scripts/check-manifests.sh (e647f14).

gates.md:
- #11a the four ADR-0020 constants live in lib-checks-skill.sh:313-316 and
  lib-checks-agent.sh:164-165, not in validate.sh.
- #11b the pretty-format-json exclude is two alternations expanding to
  three tracked files, including .claude/apm-hooks.json.
- #11c the ADR-0020 contract suite runs 28 -> 27 -> 29 (620f20b,
  4de5b6b, ef27c97), 29 at HEAD; the unverifiable 25 is dropped.
- #11d the boundary resolver is one copy since ef27c97.
- #12 apm-audit-ci documents the 10 root checks and the 1 plugin check
  apm 0.28.0 actually runs, that content-integrity IS the hidden-Unicode
  scan, that manifest-parse is not a named check, and that the hook needs
  a completed apm install. The offline claim is qualified accordingly.
- N9 gates.md:142-146 verified to still match the hook description.

AGENTS.md:
- #12 the no-network session rule is qualified to a populated
  apm_modules/.

Audit note:
- A1 hook counts corrected to 27/9 -> 26/8 -> 27/9 -> 26/8 (26 and 8 at
  HEAD) and the dangling pointer dropped.
- A2 skill-size-check.sh is 509 lines with the resolver sourced, not 1,522
  embedded; citations repointed to skill-size-check.sh:323-335 and
  lib-checks-skill.sh:235-283 (fail() at :265 and :280), and that library
  is 627 lines.
- A3 consumers receive 15 test files across 5 skills; 16 tracked test
  paths repo-wide.
- A4 the "do not run apm update on this branch" instruction is marked
  superseded, with the branch-aware guidance in its place.
- Finding 31's "true orphans" claim corrected for HOTL and Sycophancy,
  both still used in core/ai-constitution.md.

Same class, found during group 2:
- skill-author's deployment-modes.md no longer points at .mcp.json
  configs (deleted in c96ca9c); metadata.version 1.0.2 -> 1.0.3.
- git-orchestrate's context contract clarifies that
  user_config_overrides is caller-supplied session state, not a config
  read. The field name is unchanged.
- B3 root apm.yml's executables.allow comment: grants are version-blind
  in apm 0.28.0, so the #2.0.0 suffix is cosmetic to apm and a bump does
  not break the hook; the suffix stays because
  check-executables-allow-sync.sh requires it.

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

docs/adr/0024-apm-is-the-only-supported-install-path.md

@@ -179,14 +179,15 @@ now discoverable in the install output and would otherwise be found and double-r
 they do not belong to — exactly the `apm_modules/` problem ADR-0018 recorded, arriving by a second
 route. Any future script that walks this repo's tree needs both exclusions.
 
-**4. No version bumps.** There is no standing rule that would require one. The patch-bump-on-content-
-change convention this repo once followed was ADR-0006's, and ADR-0015 explicitly retired it as a
-dual-manifest artifact: "Conventions that existed only because of hand-authored dual manifests
-(ADR-0006's version-parity/patch-bump rule …) are obsolete under `apm.yml`'s single-manifest model
-and were deliberately dropped." ADR-0015 also records that apm "has no native version-bump
-automation at all", so nothing mechanical demands one either. What remains is the substantive test,
-and it is satisfied independently: nothing under `.apm/` is touched here, only compiled artifacts are
-removed, so the content every apm consumer receives is byte-identical before and after. This also
+**4. No version bumps.** There *is* a standing rule, and it is not triggered here.
+`plugins/kyberforge/.apm/skills/apm-workflow/references/configure.md` states it: **bump a package's
+own `apm.yml` `version:` whenever anything that reaches its compiled output changes** — either its
+`.apm/` content (a new or removed skill/agent/hook, or a substantive edit to one) or its own
+manifest metadata (`description`, `keywords`, `author`, `license`, `homepage`, `repository`, all
+compiled verbatim into `plugin.json`). This change touches neither: nothing under `.apm/` is edited,
+no manifest metadata changes, and only compiled artifacts are removed, so the content every apm
+consumer receives is byte-identical before and after. apm also "has no native version-bump
+automation at all" (ADR-0015), so nothing mechanical demands one either. This also
 avoids triggering the `executables.allow`
 `kyberforge#<version>` pin cascade ADR-0019 describes, which would otherwise turn a cleanup into a
 multi-file coordinated edit for no functional gain.