scribe-kb-tidy

# scribe KB tidy — agent skill `scribe lint` flags four content-quality problems it **cannot** fix mechanically because each needs judgment: **bloated** articles (split), **thin** stubs (expand or merge), **overgrown rolling files** (archive), and **directories named after the KB** (merge). This skill is the procedure for working that queue — the fixes `scribe lint --fix` deliberately never attempts. This is destructive-adjacent work: you rewrite, split, and move real curated knowledge. The golden rules below are not optional. **Trust map (see `references/FIELD_NOTES.md` for the evidence).** Two of these classes have a battle-tested procedure from real KB cleanups — reuse it. The other two have never actually been hand-executed; this skill is their *first* written procedure, grounded in the KB's stated principles. | Class | Status | How to move | |---|---|---| | Rolling archive | **Proven** — done on ~12 real projects | Reuse the recipe below | | Self-named dir | **Proven triage**, but merge is propose-only | Warn, distinguish, propose | | Bloated split | **Greenfield** — never hand-done | Propose split points first | | Thin expand/merge | **Greenfield** — never hand-done | Propose the target first | ## Golden rules (read before touching anything) 1. **Mechanical = safe; judgment = propose first.** Deterministic edits (moving whole rolling entries, backfilling frontmatter) you can just make — git is the safety net. Anything that decides *which page wins* or *which...