Release v19.0.2 migration operator feedback

[flyingrobots]

Patch thesis

v19.0.2 makes the safe v18-to-v19 migration observable and unambiguous for operators without changing the v19 runtime API, storage format, or application grammar.

Must ship

• Emit inventory and rewrite progress for every commit.
• Bound terminal redraw work while preserving phase, writer, named-step, and final progress.
• Print durable success, authority-change, scratch-verification, and recovery-ref evidence after TUI teardown.
• Prevent terminal and scheduled renderer failures from replacing or terminating migration outcomes.
• Prepare synchronized v19.0.2 metadata, changelog, and operator signposts.
• Pass release-prep and merged-main final preflight.
• Publish npm and JSR artifacts from immutable tag v19.0.2.
• Verify registry visibility, installed CLI behavior, and release evidence.
• Record the lightweight release retrospective and close this milestone.

May slip

Nothing. This is a narrow patch release.

Explicitly not included

• Runtime API or package-entrypoint changes.
• Storage-format or WARP-ref changes.
• Application grammar changes.
• Streaming recursive materialization implementation; PR Define streaming indexed recursive WARP architecture #813 is architecture planning only.

Evidence already landed

• Keep migration progress and completion visible #834
• merge commit 8b324a39de491119c25165b374437d94cd0a4f48

[coderabbitai]

🔗 Related PRs

#680 - release: prepare v18.1.2 [merged]
#788 - Add one-shot v18-to-v19 retained-substrate migration [merged]
#802 - Release v19.0.0 [merged]
#825 - Make v18-to-v19 migration safe and observable [merged]
#832 - Release v19.0.1 with safe migration guidance [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!

[flyingrobots]

Released v19.0.2.

• PR Release v19.0.2 with observable migration progress #836 merged normally at 7ed1fd2b82f831f109303c6a8afe36dd4bde5f45.
• Immutable v19.0.2 tag resolves to that merge commit.
• Official release workflow succeeded: https://github.com/git-stunts/git-warp/actions/runs/30502172617
• npm @git-stunts/git-warp@19.0.2 is published with latest set to 19.0.2; integrity sha512-nmmiH7tmVaZMejGCtnCsu57t7scvMqyhfMFpCajJ37B6eI5zTaX/6ruNj6Ik4HX5qC2NqcYeokc9u7Zee2VPSg==.
• JSR @git-stunts/git-warp@19.0.2 published successfully with provenance.
• GitHub Release: https://github.com/git-stunts/git-warp/releases/tag/v19.0.2
• Think resolved the official npm artifact and passed its 155-test fast suite.

Retrospective: the first tag-workflow attempt was correctly blocked by an accidental priority:asap label on this release issue. Removing that scheduling label allowed the unchanged tagged commit through the release guard; no tag rewrite, rebase, amend, or force operation occurred.