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/skill-audit/references/body-discipline.md

@@ -135,9 +135,16 @@ Constraints:
 Worked negative example — **`git-commits` v0.1.2 at commit `5e23250`, a fixed pre-retrofit
 snapshot, not the current file.** The live skill is v0.1.3 and matches none of the citations below;
 they are quoted as they stood before the ADR-0020 retrofit, and are not to be refreshed against
-`HEAD`. Read the snapshot with
-`git show 5e23250:plugins/git/.apm/skills/git-commits/SKILL.md`. That body carried
-twelve Gotchas, four of which restated content already below them or already in the description:
+`HEAD`. The snapshot is reachable only from a checkout of the authoring repo — an installed plugin
+cache holds no git history and no such path — so read the citations below as quoted rather than
+going to look for the file. From a checkout:
+
+```text
+git show 5e23250:<the git plugin>/.apm/skills/git-commits/SKILL.md
+```
+
+That body carried twelve Gotchas, four of which restated content already below them or already in
+the description:
 
 | Gotcha | Restates |
 |---|---|

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

@@ -40,8 +40,11 @@ A model-invoked description carries exactly three things:
    the agent is deciding whether to act, not reading a catalogue entry.
 2. **At most one capability clause.** What it does, in one clause. Never an enumeration.
 3. **Boundary clause.** Compressed form: `Not <thing> -> <skill-name>.` The target must resolve to
-   a real skill directory or agent file in the authoring source; `validate.sh` checks that
-   deterministically and a dangling target already surfaces as a Structure FAIL.
+   a real skill directory or agent file in the authoring source. `validate.sh` checks that
+   deterministically and grades it by notation: an unresolved `/name` or arrow target is an ERROR
+   and reaches the report as a Structure FAIL, while an unresolved prose-form target ("use `y`
+   instead") is only a SUGGESTION unless a second target in the same sentence resolves. Take the
+   script's tier as given and report it once, under Structure.
 
 Everything else belongs in the body or in `README.md`.
 

plugins/kyberforge/skills/skill-audit/references/finding-criteria.md

@@ -42,8 +42,6 @@ Flag as FAIL if:
 - **Vague capabilities** ("helps with APIs" where "parses and validates OpenAPI specs" 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` reports the unresolved name.
 - **Trigger-list, boundary or indirect-trigger content on a hand-invoked skill** — see Step 0 of
   `references/description-quality.md`.
 - **Over 1024 characters** — the agentskills.io specification ceiling, unchanged and independent
@@ -56,6 +54,14 @@ Flag as SUGGESTION if:
 - 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.
 
+**An unresolved boundary target is not graded here.** `validate.sh` owns that call and tiers it by
+notation — `/name` or an arrow form is an ERROR, the bare prose form a SUGGESTION unless a second
+target in the same sentence resolves — and Step 1 has already filed it under `### Structure` at that
+tier. Re-grading it as a description FAIL puts one target in the report twice at two tiers. What is
+left to judgment here 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.
+
 ## body-discipline — `references/body-discipline.md`
 
 Flag as FAIL if: