fix(kyberforge): reconcile the authoring rules the ADR-0020 trim left disagreeing

Six defects, each one a place where two files that an author reads in the same
sitting told them different things — or where the trim dropped a rule and nothing
noticed because no gate covers prose.

**"Use proactively" contradicted itself across the pair.** All three agent
templates said to add it where the runtime should delegate unprompted, while
`agent-audit`'s `KyberforgeCopilot.ProactivePhrase` rule grades it a hard FAIL in
any `*.agent.md` — which is the Copilot half of every project/user pair *and* the
vendor-neutral plugin-scope file, since that compiles to a real Copilot agent
downstream. Following the template produced a file the repo's own gate rejects.
The phrase is now permitted in exactly one place, the Claude Code `.md`, and
`references/contract.md` carries the per-file table plus the consequence authors
ask about next: a pair whose CC half has it and whose Copilot half does not is
correct, because `agent-audit` checks that both halves describe the same job, not
that they match word for word.

**The output-schema rule contradicted itself inside one file.** `contract.md`
said any content only one branch reaches moves to `references/`, and then offered
an "Output format template" body pattern with no qualification. Stated once now,
so it is not re-litigated: an output schema stays in the body only when every flow
produces it and it is roughly 50 words or less. No third option.

**Gotchas tiers disagreed with the script.** `validate.sh` emits the entry count
through `suggest()` and exits 0, while `skill-author` and `skill-audit` both
called more than five entries a FAIL. Whether a given gotcha earns its place is
judgment, so the prose moves to the script's tier rather than the reverse. The
paraphrase rule stays a FAIL and is explicitly marked as the auditor's call — no
script detects it.

**The dispatch exemplar was cited at the wrong number.** `apm-workflow`'s body is
421 words; 554 is its whole-file count. Both `contract.md` and `body-discipline.md`
cited 554 while describing a body budget, so an author calibrating against the
exemplar overshot by ~30% — the exact whole-file/body-only conflation those two
sections exist to warn against, reproduced inside the warning.

**"Error handling" came back as a required body element.** It was one of four and
is the one that gets dropped, and dropping it is not neutral: an agent handed
malformed input with no instruction invents a recovery, and a subagent's invented
recovery is invisible to its caller until the output is wrong. Restored in
`agent-audit`'s rubric as a SUGGESTION, in `agent-author`'s contract and both
scope checklists as a required element, and as an `## Errors` section in all three
templates.

**`skill-author` Step 4 gains the one check the audit misses.** An empty body
reports `PASS SKILL.md body word count 0` — a word gate cannot tell "concise"
from "absent". Step 4 now hand-checks for a non-empty section, and its commit
verification is conditioned on actually being inside a git worktree, which a skill
under `~/.claude/skills/` is not.

Also here: absolute repo paths removed from `skill-author`'s SKILL.md and
contract.md in favour of naming the skill (`zoom-out`'s description is quoted
inline instead of pointed at), the boundary-target universe documented to match
the resolver, a two-hops-from-SKILL.md limit on reference chains, and
`new-agent.sh`'s next-steps output naming the description budget and the
deliberate absence of an agent body gate.

Refs: ADR-0020

plugins/kyberforge/.apm/skills/skill-author/assets/templates/SKILL.md

@@ -10,14 +10,22 @@ name: SKILL_NAME
 # Examples: my-tool, data-analyzer, pdf-processor
 
 description: >
-  Use when FILL IN: trigger — when should an agent activate this skill?
+  Use when FILL IN: trigger.
   FILL IN: at most ONE capability clause, stated specifically
   (e.g. "parses and validates OpenAPI specs", not "helps with APIs").
-  Not FILL IN: near-miss case -> FILL IN: real sibling skill name.
+  Not FILL IN: near-miss case -> FILL IN: real sibling skill.
 # Required. Preloaded into EVERY session whether or not the skill is invoked.
 # Exactly three parts, in this order: trigger clause, at most one capability
 # clause, boundary clause. Drop the boundary line if no near-miss skill exists.
-# Budget: 250 characters target, 400 hard ceiling (counting this value only).
+# Trigger clause: when should an agent activate this skill? Describe the user's
+# intent, not the skill's internal mechanics.
+# Budget: 250 characters target, 400 hard ceiling (counting this value only,
+# with YAML folding resolved). This scaffold sits at 214 — keep the fill-in
+# under the target rather than growing past it.
+# Boundary clauses may be plural: write one per genuine near-miss, and none
+# where no sibling could steal activations.
+# Never let a hyphenated skill name wrap across two lines of this folded block
+# — folding turns the break into a space and the routing target stops resolving.
 # Banned here: capability lists, output-format detail, composition notes,
 # implementation detail, and restating one trigger twice in two registers.
 # The boundary target must resolve to a real skill or agent — it is checked.