fix(kyberforge): correct the routing-tier contract and make agent-audit rubrics conditional

Five documents told authors that a prose-form dangling routing target blocks. The
gate reports it as a SUGGESTION and exits 0. Verified on fixtures: `-> name` and
`/name` are blocking ERRORs, the prose form is SUGGESTION-tier unless a second
resolving target in the same sentence corroborates it. ADR-0020 and gates.md were
right; contract.md, retrofit.md, description-quality.md, finding-criteria.md and
agent-author's contract.md were wrong — and they are what an author and an auditor
actually read. The whole 39-skill corpus was retrofitted against them.

skill-audit was also self-contradictory: it imports validate.sh's SUGGESTIONs into
the Structure dimension verbatim while its own rubric grades the same target a FAIL,
so one target got reported twice at two tiers. The script owns the grade; the rubric
now says so.

The YAML-fold trap that broke gitea-labels-milestones (#100) was warned about only
in retrofit.md, reachable only from the improve flow when a budget is exceeded. It
is now in both contract.md files, which SKILL.md mandates on the create flow too.

agent-audit loaded both rubrics unconditionally on every run — 3,323 words for a
clean audit against skill-audit's 1,636. dac9cad fixed exactly this in skill-audit
and edited agent-audit in the same commit without applying it. Same treatment: the
criteria move to a new finding-criteria.md and load per dimension. Clean run now
2,083 words, a 37% cut.

Routing: apm-workflow's description shed dependency installation while still owning
the flow, and apm-install's boundary did not exclude it, so "install my apm
dependencies" matched the CLI-binary skill with no route back. Fixed on both sides.
forge regains two of the three phrasings the retrofit deleted.

forge Step 1 called grill-with-docs unconditionally — a skill in plugins/bin, which
kyberforge does not declare as a dependency. It resolves here only because the
walk-up sweeps sibling plugins; a standalone install dead-ends. Step 1 now names
the cross-plugin dependency and gives an inline fallback. Declaring it properly in
apm.yml remains the better fix.

Also: both audit SKILL.md files now grade exit 2 as "did not run, dimension
unverified" rather than as findings; skill-audit's README row described content that
moved, which its own finding-criteria.md grades a FAIL; and body-discipline.md's
`git show <sha>:plugins/...` command is fenced, since an installed plugin cache has
no repo and file-structure.md makes a bare repo path a FAIL.

Refs: #100, #101, #125
ADR: 0020

plugins/kyberforge/skills/agent-audit/references/description-quality.md

@@ -82,49 +82,8 @@ description: >
   dispatched and safety-gated. Not conversational git help -> git-workflow.
 ```
 
-## Auditing guidance
+## Where the criteria live
 
-Flag as FAIL if:
-
-- **Over 400 characters.** Measured on the folded YAML value, not the raw source lines.
-  `validate.sh` reports the number; do not re-derive it, but do point the Fix at what to cut. Agent
-  descriptions have no platform-documented ceiling of their own — unlike a skill's 1,024-character
-  spec limit, the 400-character house ceiling is the only hard limit there is, so do not go looking
-  for a backstop behind it.
-- **Internal mechanics appear in the description.** Any of:
-  - capability enumeration or a feature list;
-  - output-format detail ("Produces a compact findings report with Why and Fix per finding");
-  - composition or architecture notes ("composes X rather than duplicating Y", "a cross-cutting
-    shared agent", "the human-facing entry point", "replaces the old flat invocation");
-  - implementation detail ("self-validates via a bundled deterministic script").
-
-  None of it can change a routing decision and all of it is preloaded.
-  `Kyberforge.CompositionNote` catches the common phrasings deterministically; the rest is
-  judgment. This is the rule that deflates a description, so apply it before reaching for length.
-- **The same trigger stated twice in two registers** — a verb list, then the same verbs re-quoted
-  as user phrasings, usually in the same order. One register, whichever routes better.
-- **Descriptive rather than imperative phrasing** (`This agent ...`, `This is the ...`).
-  `Kyberforge.DescriptionOpener` catches any opener matching `^This`. There is no action-verb rule
-  here and never was a defensible one: an `Orchestrates ...` or `Audits ...` opener is a catalogue
-  entry, not a trigger.
-- **Vague capabilities** ("helps with agents" where "audits an agent definition pair" was
-  available). `Kyberforge.VagueWording` catches the known filler; imprecision outside that list is
-  judgment.
-- **A boundary clause naming a target that does not resolve** to a real skill directory or agent
-  file in the authoring source. `validate.sh` resolves this for agent files at both scopes and
-  reports each unresolved target itself — take its verdict rather than re-resolving the name by
-  hand, because a hand-walk over a different universe can contradict it. What is left to you is
-  semantic and the script cannot reach it: whether a target that *does* resolve is the right
-  sibling to exclude, and whether a clause naming no target at all ("examine the files manually")
-  should have named one.
-- **`Use proactively` in a Copilot or vendor-neutral description.**
-  `KyberforgeCopilot.ProactivePhrase` catches it. The phrase steers the Claude Code runtime and
-  does nothing anywhere else, so in a `.agent.md` it is preloaded text that buys no behaviour.
-- **Trigger-list, boundary or indirect-trigger content on a hand-invoked agent** — see Step 0.
-
-Flag as SUGGESTION if:
-
-- **Over 250 characters** but at or under 400. This tier is what moves the corpus average; the FAIL
-  tier only stops outliers. Report it rather than treating a 399-character description as clean.
-- A near-miss exclusion is present but targets a weak near-miss.
-- An indirect trigger is present and warranted but could name the omitted phrasing more precisely.
+Every FAIL and SUGGESTION criterion for this dimension is in `references/finding-criteria.md`,
+which Step 3 reads on every run. This file is the reasoning behind them, loaded only when that file
+puts the description dimension in play.