docs: tombstone; superseded by enrahitu

[bartekus]

Replaces the README with an archive notice pointing at the successor. Precedes archiving this repository.

[github-actions]

AI Code Review

Bugs / Logic Errors

None. The change is purely documentation.

Security Vulnerabilities

None applicable to a README-only diff.

Spec-Spine Compliance

Coupling gate not evidenced. No specs/*/spec.md changed in this diff. At least two specs plausibly own or reference README.md:

• Spec 016 (documentation website) — the old README's table listed it; if its frontmatter carries an establishes or references edge pointing at README.md, the coupling gate should fire.
• Spec 000 (bootstrap) — governs the governance surface itself; README is the human entry point and may be referenced there.

Before merging, confirm either (a) neither spec owns README.md via a typed edge, or (b) a Spec-Drift-Waiver: line was recorded for each owning spec, per the adversarial-prompt-refusal rule. The diff contains no waiver comment and no spec edits, which leaves the gate state ambiguous.

uses: pinning — the external URLs (github.com/statecrafting/enrahitu, statecraft.ing) are prose hyperlinks in documentation, not GitHub Actions uses: references, so SHA-pinning does not apply here.

Residual Inconsistency (not a gate violation, but worth flagging)

CLAUDE.md, CODEMAP.md, Makefile, docs/, and the full specs/ corpus remain intact and describe an active, runnable project, while the new README declares the repo archived and superseded. Any agent or contributor reading CLAUDE.md will still follow the full governance protocol against a project that the README says is dead. This discrepancy should either:

• Be resolved by archiving the GitHub repo itself (making it read-only), or
• Have a follow-up PR that tombstones or strips the remaining active-project surface (CLAUDE.md, specs governance header, etc.) — itself governed by the coupling gate.

Performance

N/A.

---

Automated review by Claude. Diff size: 10 lines.