feat(kyberforge): give skill-author a procedure for the #99 retrofit

ADR-0020 shipped its gates hot with no baseline file, so 26 of 39 descriptions
and 9 of 39 bodies are over their FAIL tier and editing any of them for any
reason requires bringing the skill into contract first. `references/improve.md`
said exactly that and stopped there — it mandated a retrofit and supplied no
procedure for one.

Four dry-run retrofits confirmed what that costs. Asked the same questions —
what to cut first, when a body is two flows rather than one, what else has to
change alongside — they invented six to ten different answers, so the same skill
retrofitted twice produced two different skills and neither run could be reviewed
against anything.

`references/retrofit.md` fixes the answers: an ordered cut list ranked by tokens
removed against behaviour lost (inverting that order is how a retrofit deletes the
instruction the skill existed to carry), the test for whether a body holds two
mutually exclusive flows, the reference-file conventions, the collateral checklist
for `README.md` and `references/sources.md`, and a worked description retrofit.

It also states the trap the dry runs kept hitting: retrofit the skill in place,
inside its package. The boundary-target universe is built by walking up from the
file being checked, so a scratch copy has no authoring root above it, the check
prints `INFO ... DID NOT RUN`, and the run still exits 0 — a line that reads as a
pass and is not one. A retrofit signed off on a copy carries an unverified
boundary target into the corpus.

Loaded from the improve flow only when a budget is actually exceeded, so a routine
improvement pays nothing for it.

Refs: ADR-0020, #99

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

@@ -76,6 +76,12 @@ contract first — the gates are hot and carry no baseline file, so a one-line f
 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.
 
+If the skill's description exceeds 250 characters, or its body-only word count exceeds 600, read
+`references/retrofit.md` before editing. It carries the ordered cut procedure, the
+mutually-exclusive-flows test, the reference-file conventions this flow needs, the collateral
+checklist for `README.md` and `references/sources.md`, and a worked description retrofit. Do not
+improvise the cuts — four dry runs invented six to ten different answers to the same questions.
+
 If a signal points to a script or reference file, edit that file directly rather than adding a
 workaround in SKILL.md.