BAD CODE™: remove the stale v19.0.0 two-pass migration from the root README

[flyingrobots]

Problem

The root README still instructs operators to run @git-stunts/git-warp@19.0.0 once as a non-mutating rehearsal and again with --apply. That is now false and unsafe:

• v19.0.0 contains the migrator that failed on the real Think retained checkpoint;
• PR Make v18-to-v19 migration safe and observable #825 documents that the retained-state migration requires v19.0.1;
• the corrected command performs confirmation, scratch proof, promotion, and promoted verification in one normal invocation;
• --apply is only a compatibility alias and --dry-run is the explicit disposable rehearsal.

The package landing page therefore contradicts the canonical v19 migration guide on the exact operation users are most likely to copy.

Acceptance

• The root README requires v19.0.1 for retained v18 migration.
• The primary example is one parameterized command with <graph-name>, never hard-coded events.
• The text explains interactive confirmation, one-pass proof and promotion, recovery refs, and the optional --dry-run rehearsal without implying reusable scratch work.
• The root README links to the canonical migration guide for capacity, phases, recovery, and multi-graph details.
• Documentation validation prevents the stale v19.0.0/two-pass instructions from returning.

[coderabbitai]

🔗 Related PRs

#64 - docs: enhance README with traversal directory, seek guide, and runtime compat [merged]
#710 - Release 18.2.1 [merged]
#726 - Move graph exports behind v19 public API boundary [merged]
#788 - Add one-shot v18-to-v19 retained-substrate migration [merged]
#825 - Make v18-to-v19 migration safe and observable [open]

---

📝 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!