refactor(kyberforge): move audit guidance out of the per-run rubric load

skill-audit loaded roughly 4,268 words of rubric on every run, most of it
criteria for findings a clean skill never triggers. The auditing guidance moves
into finding-criteria.md, read only when a finding is actually raised, cutting
a clean audit to about 999 words. The named-skill exemption is replaced with
properties, so the rubric stops carrying a list that ages the moment a skill
is renamed.

apm-workflow's `type:` trap sat in one flow while biting several, so it is
promoted to a common gate reachable from all of them; its claim to be
self-contained was untrue once it started routing to apm-install. skill-author's
contract had drifted from body-discipline.md and is realigned, and agent-audit's
field inventory is brought in line with the same split.

plugins/kyberforge/.apm/skills/agent-audit/SKILL.md

@@ -20,7 +20,7 @@ metadata:
 
 - Do not narrate PASS/FAIL per check while auditing. Gather findings internally and surface them only in the Step 4 report. Narrating each check as you go is the default failure mode here.
 - Agents take the same 250/400-character description gates as skills and **no body word gate at all** — an agent body becomes the system prompt of a fresh context, so the 900-word skill ceiling does not transfer. Judge an over-long agent body through the delegation check, never by word count.
-- At plugin/APM scope the agent is a single vendor-neutral file by design: never raise a pair-consistency finding there, and provider safety stops meaning Claude-Code-versus-Copilot field leakage.
+- At plugin/APM scope the agent is a single vendor-neutral file by design, so provider safety stops meaning Claude-Code-versus-Copilot field leakage there.
 - Vale reporting `0 files` scanned means NOT RUN, not clean. Fall back to full Step 3 judgment for every dimension it would have covered.
 
 ## Step 1 — Deterministic checks
@@ -30,7 +30,7 @@ Resolve all three paths against this skill's own directory so they work from a r
 ```bash
 bash scripts/validate.sh <agent-file>
 bash scripts/validate-provenance.sh <agent-file>
-scripts/vale-wrap.sh <agent-file> [<counterpart-file>]
+bash scripts/vale-wrap.sh <agent-file> [<counterpart-file>]
 ```
 
 `validate.sh` takes either half of a project/user-scope pair or the single plugin/APM-scope file, detects the provider from the extension and the scope by walking up, then checks required fields, kebab-case `name`, `FILL IN:` placeholders, template HTML comments left in frontmatter, the ADR-0020 description budget (250 chars SUGGESTION, 400 FAIL, measured on the folded YAML value) and the fields that scope permits. Its findings become the `### Structure` dimension — its FAILs and its SUGGESTIONs both — except the ones the Step 2 scope contract re-routes.

plugins/kyberforge/.apm/skills/agent-audit/references/field-inventory.md

@@ -38,9 +38,9 @@ whose vocabulary differs per harness — Claude Code names its own tools, Copilo
 other, and `apm compile` copies frontmatter verbatim with no per-target integrator to reconcile
 them. `disallowedTools` is a **denylist**, and denying by name is safe under verbatim copy: a name
 the other harness does not recognise denies nothing, so the worst case is that the fence is absent
-there, never that the wrong capability is granted. Claude Code honours it for plugin subagents —
-`docs/research/docs/claude-code-plugins/agent-definition.md:99` names the fields plugin agents
-silently ignore (`hooks`, `mcpServers`, `permissionMode`) and `disallowedTools` is not among them.
+there, never that the wrong capability is granted. Claude Code honours it for plugin subagents: its
+plugin agent-definition reference names the fields plugin agents silently ignore (`hooks`,
+`mcpServers`, `permissionMode`), and `disallowedTools` is not among them.
 
 `disallowedTools` also appears in `claude-code-only-fields` above, and that stays correct: at
 project/user scope it is still a Claude-only field and must not appear in a Copilot `.agent.md`.