diff --git a/CONTRIBUTING_IDEAS.md b/CONTRIBUTING_IDEAS.md
index b4f8d05..2c586ac 100644
--- a/CONTRIBUTING_IDEAS.md
+++ b/CONTRIBUTING_IDEAS.md
@@ -99,7 +99,7 @@ October 2026; "fork" means the fix is on one of the branches listed in
    the library without reinstalling (8.3 s). gpui-mobile only needs a
    loader for the pushed library (`GpuiLibraryLoader`, fork branch
    `dev-hot-loader`). Next: ask upstream where they want it
-   ([issue draft](docs/upstream/hot-reload-discussion.md)). A desktop-hosted
+   ([longbridge/gpui-mobile#34](https://github.com/longbridge/gpui-mobile/issues/34)). A desktop-hosted
    phone-size preview is not started.
 5. **Binary size.** Measured in [docs/binary-size.md](docs/binary-size.md);
    every PR's job summary shows the APK and `.so` sizes.
diff --git a/MOBILE_PATCHES.md b/MOBILE_PATCHES.md
index eba40e5..1b0effd 100644
--- a/MOBILE_PATCHES.md
+++ b/MOBILE_PATCHES.md
@@ -120,8 +120,8 @@ packaged one. It replaces the `loadLibrary()` the lab's `LabActivity`
 carried; the lab keeps a copy in `android/app/src/main/java` (`LabActivity`
 needs it to compile, also in `cargo gpui apk`, which skips `build.sh`). Host-driven Activities
 only (`NativeActivity` loads the packaged library itself). Not proposed
-upstream yet: an [issue draft](docs/upstream/hot-reload-discussion.md) asks
-the maintainers first.
+upstream yet: [longbridge/gpui-mobile#34](https://github.com/longbridge/gpui-mobile/issues/34)
+asks the maintainers first ([text](docs/upstream/hot-reload-discussion.md)).
 
 ### Clear the Java exceptions the accessibility bridge leaves pending — branch `android-a11y-clear-exceptions`, now part of `android-accessibility`
 
diff --git a/docs/upstream/README.md b/docs/upstream/README.md
index 2cedf90..5f142a5 100644
--- a/docs/upstream/README.md
+++ b/docs/upstream/README.md
@@ -39,7 +39,7 @@ captures in [../demos](../demos) and say where a capture is missing.
 | 17 | kit | `input-purpose` (fork branch only) | ⛔ | #4, plus the same GPUI change; conflicts with `main` (to rebase then) | yes | — |
 | 18 | mobile | `android-activity-requests`, `android-picker-files` (fork only) | ⛔ | the JNI rework (issue #31): built on its `jni.rs` | partly ([picker screenshots](../demos/platform-apis)) | — |
 | 19 | mobile | `android-string-arrays` (fork only) | ⛔ | #6, plus the JNI rework (#31): `contacts/android.rs` was rewritten there | no | — |
-| 20 | mobile | [`dev-hot-loader`](https://github.com/Bombatomica64/gpui-mobile/tree/dev-hot-loader) (`GpuiLibraryLoader`) | ⏳ ask first: an issue asking where hot reload should live; the PR only if they want it | — | phone strip from the A1 spike | [issue draft](hot-reload-discussion.md) |
+| 20 | mobile | [`dev-hot-loader`](https://github.com/Bombatomica64/gpui-mobile/tree/dev-hot-loader) (`GpuiLibraryLoader`) | ⏳ asked in [#34](https://github.com/longbridge/gpui-mobile/issues/34) where hot reload should live; the PR only if they want it | — | phone strip from the A1 spike | [issue draft](hot-reload-discussion.md) |
 
 Notes on the triage:
 
diff --git a/docs/upstream/hot-reload-discussion.md b/docs/upstream/hot-reload-discussion.md
index 842a379..2f5678e 100644
--- a/docs/upstream/hot-reload-discussion.md
+++ b/docs/upstream/hot-reload-discussion.md
@@ -1,8 +1,8 @@
-# Draft: hot reload for gpui-mobile apps (not posted)
+# Hot reload for gpui-mobile apps: the upstream issue
 
-> **Status: draft for review, not posted.** longbridge/gpui-mobile has GitHub
-> Discussions turned off, so this would be an **issue**. Title:
-> "Hot reload for Rust on Android: interested, and where should it live?"
+> **Status: posted 2026-10-12 as
+> [longbridge/gpui-mobile#34](https://github.com/longbridge/gpui-mobile/issues/34)**
+> (Discussions are off there). The text below is what was posted.
 
 ---