docs: correct the apm-only change after a five-agent review

A five-agent review of 718c79a and d2480b8 found no skill, agent or hook
regressions (39 skills before and after) and confirmed both hook removals
are genuinely moot -- verified against the tree, not taken on the commit's
word. It did find one functional regression (fixed separately) and this
documentation drift.

Counting errors, all from a git pathspec `*` crossing `/`:
  - 17 .bats files shipped to consumers is really 10; 17 counted tracked
    paths merely containing /tests/, one of them a template asset
  - "roughly 88s off every push" is ~92.4s; 88 omitted validate-plugins
  - "roughly 70% of each plugin remains live" holds only for kyberforge;
    the real spread is 44.3% (bin) to 70.6%, now a table
  - the pre-push enforcement row was half-corrected: 33 entries stood
    unstruck (now 27) and 14 -> 11 switched counting basis mid-sentence
  - the root .claude-plugin/plugin.json was described as "kept"; it has
    never been tracked

gates.md said "Ten hooks" above a nine-row table (11 was decremented for
one removal, not two), and "both need the claude CLI" for one remaining
validator. Its pretty-format-json exclude rationale claimed six
alternations expanding to sixteen files in a passage headed "Mind which
number you are quoting" -- four alternations, two live files; the two
dead ones are dropped from the pattern. check-useless-excludes could not
catch this: it only flags an exclude matching nothing at all.

ADR-0024 cited ADR-0006 for a patch-bump rule it does not contain and
which ADR-0015 explicitly retired; stated apm's marketplace probe order
backwards (.claude-plugin/ is the last candidate, not the first, so the
earlier .github/plugin/ deletion only demoted resolution); undercounted
apm's skill-deploying targets as seven when there are fifteen; and never
recorded that validate-plugins was removed. The symlink hedge is resolved:
apm_cli/security/gate.py's ignore_non_content() drops symlinks silently on
deploy while apm_modules/ materialization dereferences them, so content
survives that far and vanishes at install. Accepted with no replacement
guard, per decision -- kyberforge/docs/hooks.md previously asserted a
guard that had been deleted with its script.

Four plugin READMEs still advertised `claude plugin install`; ADRs 0001,
0006, 0013, 0014, 0015 and 0019 described deleted machinery in the present
tense, 0019 most consequentially as the live justification for the
SessionStart hook's .apm/ path. CONTEXT.md's "apm package" entry forbade
"plugin" while using it in its own body, and "Output profile" lost the
antecedent for "one catalogue serves both".

run-tests.sh gains the .claude/skills/ exclusion run-bats.sh already had.
Latent today -- no test-*.sh lives under any .apm/skills/*/tests/ -- but
apm now deploys those directories, so one would be discovered twice.

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

CONTEXT.md

@@ -52,15 +52,16 @@ _Avoid_: command, prompt, macro
 
 **apm package**:
 The deployable unit apm builds and installs — one or more skills, agents, hooks, commands, and MCP
-servers under a single directory `plugins/<name>/`, consisting of that plugin's `apm.yml` plus the
-hand-authored `plugins/<name>/.apm/` tree it deploys from (ADR-0015).
-_Avoid_: plugin, package, bundle, module, plugin directory, source tree
+servers under a single directory `plugins/<name>/`, consisting of that directory's `apm.yml` plus
+the hand-authored `plugins/<name>/.apm/` tree it deploys from (ADR-0015).
+_Avoid_: bundle, module, source tree; and bare "plugin" for the *installable artifact*, which since
+ADR-0024 is an apm package and not a Claude Code plugin. "Plugin" stays correct as a modifier in the
+repo's settled compounds — **Plugin marketplace**, "plugin units", `plugins/`.
 
 **Output profile**:
-An `apm pack` target format for the generated *marketplace* catalogue compiled from root
-`apm.yml`'s `marketplace:` block. Only `claude` is declared
-(`.claude-plugin/marketplace.json`); apm's own marketplace consumers read that same file, so one
-catalogue serves both. Mechanics: `docs/spec/architecture.md`.
+A named ecosystem format `apm pack` can compile the marketplace manifest into, declared per profile
+under root `apm.yml`'s `marketplace.outputs:`. apm defines `claude` and `codex`; each writes to its
+own default path unless overridden. Mechanics: `docs/spec/architecture.md`.
 _Avoid_: build target, export format
 
 **Plugin marketplace**:
@@ -167,6 +168,11 @@ _Avoid_: ticket, card, task
 - Skills can answer to two names, bare (`gitea-prs`) and namespaced (`gitea:gitea-prs`), depending on
   whether a native install exists at user scope alongside the apm one (ADR-0018) — resolved: write
   the bare name, which is the only form `apm install` produces.
+- "plugin" was used both for the installable artifact under `plugins/<name>/` and as a modifier in
+  settled compounds (**Plugin marketplace**, "plugin units", the `plugins/` directory itself) —
+  resolved: the installable artifact is an **apm package**, because ADR-0024 ended native
+  `claude plugin install` support and it is no longer a Claude Code plugin in any operative sense;
+  the compounds keep the word and are not being renamed.
 - "context" means both the model's live token window and the bounded domain this file describes —
   resolved: unqualified "context" in this repo means the token window.
 - "audit" was used for both an author skill's inline closeout and `forge`'s independent