docs(kyberforge): restore the retrofit cut order in skill-author

improve.md still required a retrofit before extending but lost the
procedure with retrofit.md. Restore the ordered cuts inline, and fix
the stale hook name and plugin-mode wording in skill-author's tests and
deployment-modes reference.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

plugins/kyberforge/.apm/skills/skill-author/references/improve.md

@@ -76,6 +76,19 @@ into compliance first — the gates are hot and carry no baseline file, so a one
 non-compliant skill cannot be committed until the description and body meet
 `references/contract.md`. Treat that retrofit as part of the same change, not a follow-up.
 
+Retrofit against the number that actually failed: the audit reports description characters and
+body-only words separately. Audit the skill in its real package directory, never a scratch copy,
+where boundary resolution reports `DID NOT RUN` and exits 0 without checking anything. Cut in this
+order, stopping once the gate clears; the order puts the cuts that lose the least behaviour first:
+
+1. Gotchas that paraphrase a step below them — delete the Gotcha, keep the step.
+2. Spec restatements — text repeating a published spec, a tool's `--help`, or a limit the
+   validator already enforces.
+3. Capability enumeration — keep one capability clause in the description; drop the rest.
+4. Per-flow prose — move each flow into its own `references/` file behind a dispatch table.
+
+Still over after all four means the skill does two jobs: split it rather than compressing prose.
+
 If a signal points to a script or reference file, edit that file directly rather than adding a
 workaround in SKILL.md.