Add recovery protocol for closing gaps in specs, tests, and coverage

[0xhackerfren]

Summary

• Adds a formal recovery protocol (
  eference/recovery.md) defining how teams handle gaps discovered after code exists: spec gaps, mold gaps, coverage erosion, and contract gaps
• Adds a gap assessment template (harness/templates/gap-assessment-template.md) for structured gap documentation
• Wires recovery into every layer: manifesto (Section VII), playbook (recovery procedure with exit criteria), agent rules (R11/R12), Cursor rules, workflow feedback loops, agent operating model failure modes, glossary (6 new terms), README, changelog, and roadmap
• Fixes all harness references to use GitHub URLs instead of dangling
  eference/ paths that break after init

What changed (13 files, 470 insertions)

New files:

eference/recovery.md - Full protocol: discovery triggers, classification taxonomy, triage, recovery sequence (audit, spec patch, mold patch, recast, re-review), kanban integration, recurrence prevention, metrics

• harness/templates/gap-assessment-template.md - Structured gap documentation template

Manifesto and philosophy:

• MANIFESTO.md - Recovery acknowledgment in Section VII (Fracture Lines)

Operational harness:

• harness/PLAYBOOK.md - Recovery procedure, exit criteria, human/agent responsibilities, quick reference row
• harness/agent/AGENT_RULES.md - R11 (halt and report gaps), R12 (recovery behavior, now references R1-R11)
• harness/.cursor/rules/codex-automata.mdc - Recovery constraint and terminology
• harness/.cursor/hooks.json - Self-contained gap assessment prompt

Reference docs:

eference/workflow.md - Retroactive gap discovery section, companion list

eference/agent-operating-model.md - Retroactive gap discovery failure mode, companion list

eference/glossary.md - 6 new terms: contract gap, coverage erosion, gap assessment, mold gap, recovery, spec gap

Meta:

• README.md - Recovery section, tree update, template mention
• CHANGELOG.md - Unreleased section
• ROADMAP.md - Recovery in current section

Test plan

• Verify
  eference/recovery.md cross-references resolve within the repo
• Verify harness files use GitHub URLs (not
  eference/ paths) for recovery protocol references
• Verify glossary terms are in alphabetical order
• Verify R12 references R1-R11 (not R1-R10)
• Run markdownlint CI to confirm no formatting regressions
• Verify scripts/init.ps1 / init.sh still copy harness correctly (gap-assessment-template.md included)

Made with Cursor