docs(9/10): delete historical packets and generated audit sludge

[flyingrobots]

Decision

After the current truth has been rewritten into topics, delete historical packets and generated audit companions. Do not move them into a new attic. Git history is the archive.

This is documentation reconstruction slice 9 of 10.

Scope

Resolve exact tracked targets from the authoritative indexes/manifests, clear inbound links, extract any last current invariant, then delete the historical/documentary residue, including:

• docs/archive/
• docs/audit/
• docs/design/
• historical retros and release packets still under docs/method/ or docs/releases/
• obsolete case studies, extraction notes, feature plans, technical teardowns, drift reports, and one-off evidence pages outside the topic tree
• every generated *.audit.md companion in the repository, including the 284 locally committed claim-audit sidecars if they are present on the implementation branch

Before deleting design packet 0017, move its active node-retirement-ledger.json to a durable machine-policy location outside the documentation tree, update the xtask constant and tests, and prove that retired package/path drift remains enforced. Relocate other genuinely active machine assets similarly; prose history is not an active asset.

This issue authorizes the listed deletions only after exact read-only target resolution. It does not authorize deleting root project artifacts, source code, schemas, fixtures, or current topic content.

RED

First demonstrate that deleting packet 0017 currently breaks the Node-retirement guard, and that historical pages still have inbound links or truth-manifest reachability. Add focused regression coverage for the relocated policy and for forbidden history/audit sidecars.

Acceptance

• Active machine policy survives outside the historical docs tree and its tests remain green.
• No historical packet, archive directory, retro, release packet, or generated claims-audit companion remains as reader-facing documentation.
• No replacement archive, historical, graveyard, retired, or similar docs directory is created.
• All surviving current claims live in the owning topic or a root project artifact.
• No inbound links or manifest entries reference deleted paths.
• Docs-check, Node-retirement tests, relevant Bats suites, preflight, and git diff --check pass.

Scheduling

• Ordered after docs(8/10): consolidate validation CI security and invariants #750.
• Blocked by refactor(governance): replace goalposts with version milestones #742 and by completion of slices 3–8, which extract the current truth first.
• The v0.3.0 label is temporary until the plain version-milestone cutover.

[coderabbitai]

🔗 Related PRs

#475 - Merge-worthy unmerged branches into omnibus reconciliation branch [merged]
#476 - Release/v0.1.0 [merged]
#610 - Add runtime-neutral Continuum Edict packet [merged]
#623 - docs(release): record v0.1.0 publication evidence [merged]
#686 - docs: add plain Wesley onboarding path [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!