diff --git a/.fork/notes/RELEASE-NOTES-PENDING.md b/.fork/notes/RELEASE-NOTES-PENDING.md
index 154fe0661da1..691c27e41684 100644
--- a/.fork/notes/RELEASE-NOTES-PENDING.md
+++ b/.fork/notes/RELEASE-NOTES-PENDING.md
@@ -3,9 +3,4 @@
 Lines to fold into the next fork release's notes, then delete from here.
 Each entry names the sync or PR that created the obligation.
 
-- **v0.0.30 sync (PR #33):** Prompt stashes saved before this release are
-  cleared on first launch. Upstream moved the stash store to a new
-  storage key and deliberately deletes the old one at startup without
-  migrating (localStorage quota rationale, `promptStashStore.ts`); the
-  sync keeps that behavior. Users with stashed prompts they care about
-  should send or copy them before upgrading.
+(none pending)
diff --git a/.github/workflows/fork-release.yml b/.github/workflows/fork-release.yml
index 97899db7d5c0..2b20d34a6b1a 100644
--- a/.github/workflows/fork-release.yml
+++ b/.github/workflows/fork-release.yml
@@ -164,6 +164,10 @@ jobs:
             release-publish/*.blockmap
             release-publish/*.yml
           fail_on_unmatched_files: true
+          # The upgrade warnings below are durable: they ride every release
+          # body because the hazards they describe fire on any version jump,
+          # not just the release that introduced them. Drop the prompt-stash
+          # stanza only when installs at v0.1.5 or earlier no longer matter.
           body: |
             Unsigned macOS arm64 build of this fork, built from `${{ github.sha }}`.
 
@@ -185,6 +189,12 @@ jobs:
             database and left an orphaned `~/.t3/userdata-fork` directory you
             can also delete. Details: `.fork/notes/FORK-DATA-ISOLATION-HANDOFF.md`.
 
+            If you are upgrading from v0.1.5 or earlier: prompt stashes saved
+            by those versions are deleted on first launch. v0.1.6 moved the
+            stash to a new storage key and unconditionally purges the old one,
+            so copy anything you need out of the prompt stash before upgrading.
+            Details: the [v0.1.6 release notes](https://github.com/NoahHendrickson/t3code/releases/tag/v0.1.6).
+
             Cloud features (T3 Connect remote access and sign-in) are not
             configured in fork builds and will be unavailable. Everything local
             works normally.