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/.apm/skills/agent-author/references/contract.md

@@ -61,14 +61,29 @@ word for word.
 Indirect triggers ("even if the user doesn't say X") take a similar conditional at every scope:
 add one only where the user's natural phrasing genuinely omits the domain word.
 
-**Boundary targets must resolve.** Both forms are checked — the arrow and the prose form ("do not
-use for X, use `y` instead") — so a typo dangles either way. Targets resolve against a universe
+**Boundary targets must resolve, and the notation decides how hard the gate bites.** Route
+notation — `/name`, or any arrow form (`-> name`, `` -> `name` ``) — is checked
+unconditionally: an unresolved target there is a blocking ERROR. The prose form ("do not use
+for X, use `y` instead") is only a SUGGESTION by default, because a bare hyphenated word in a
+boundary clause is as likely to be a tool, a file format or an English compound as a route. It
+is promoted to a blocking ERROR only when a second target in the same sentence *does* resolve,
+which corroborates that the name was meant as a route. So a typo does **not** dangle equally
+either way — write the arrow when you want the target checked. Targets resolve against a universe
 built by walking up **from the agent file itself**: the nearest ancestor holding
 `plugins/*/.apm/{skills,agents}` (or, failing that, the nearest ancestor holding `.git`) contributes
 every skill and agent under `<root>/plugins/*/`, plus the agent's own apm package and the packages
 that package declares in `apm.yml` under `dependencies.apm`. A sibling plugin in the same monorepo
 therefore resolves; a skill in an unrelated repo does not. A target outside that universe sends the
-router nowhere. Verify it before writing it — do not invent a plausible sibling.
+router nowhere — a blocking failure in arrow or `/name` form, and in prose form only a SUGGESTION
+nobody is forced to act on, which is the worse outcome because it ships. Verify it before writing
+it — do not invent a plausible sibling.
+
+**Never let a hyphenated routing target wrap across lines in a folded `>` scalar.** YAML folding
+replaces the newline with a space, so `gitea-labels-` at the end of one line and `milestones` at
+the start of the next fold into `gitea-labels- milestones`. The gate then reads the target as
+`gitea-labels`, finds no such skill, and reports it dangling — nothing in the source lines looks
+wrong. Reflow so the whole name sits on one line. The same applies to any backticked skill or
+agent name anywhere in a description.
 
 That universe is the apm marketplace and stops there. A **host built-in is not a routing target**:
 `/compact`, `/clear` and `/init` are Claude Code slash commands with no counterpart in Copilot CLI