Record the wgpu 30 upgrade and why it is not pushed yet

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/IRIS_EXTRACTION_HANDOFF.md

@@ -41,6 +41,13 @@ packing images into arrays like atlas pages, and a bindless `binding_array`
 - **#11** `split/11-texture-bindings`, worktree `/home/bob/repos/iris-pr11`,
   head `b9c4856`, fifteen commits on top of `0f6a28b`. Reviewed seven times,
   all answered.
+- **wgpu 30** `split/13-wgpu30`, worktree `/home/bob/repos/iris-pr13`, head
+  `d887426`, **committed but deliberately not pushed**. It is branched from
+  #11's head rather than `upstream/main`, because the renderer it has to fix
+  is the one #11 leaves behind -- doing it on canonical main would mean
+  writing the same fixes twice. Once #11 is squash-merged, rebase this single
+  commit onto the new `upstream/main` and push it then; pushing now would fix
+  a history that has to be rewritten.
 - **#12** `split/12-pointer-routing`, worktree `/home/bob/repos/iris-pr12`,
   head `028521b`. A scroll falling through a hovered button. Not reviewed as
   of the last check. Independent of #11 and can merge in either order.
@@ -179,11 +186,12 @@ on what needs tested."*
 So the order is by how much else depends on a thing, not by what is nearest
 ready, and a slice lands with tests rather than with a script in `/tmp`.
 
-1. **wgpu 28.0.0 -> 30.0.1.** Two majors behind, and it is under everything
-   the renderer does; any renderer slice written first is written twice.
-   `winit` is at 0.30.12 with only a 0.31 prerelease available, so it stays
-   until that is stable; `image` 0.25.9 -> 0.25.10 is a patch to take at the
-   same time. `parley` 0.11.1 is current.
+1. **wgpu 28.0.0 -> 30.0.1.** Done in `d887426`, waiting on #11 (see above).
+   `winit` stays on 0.30.12 until 0.31 is out of prerelease; `parley` 0.11.1
+   is current. The API changes were: the instance takes the display handle it
+   presents on (GLES on Wayland needs it), `get_current_texture` returns a
+   status enum rather than a `Result`, presenting moved to the queue, and
+   bind group and vertex buffer layouts became sparse.
 2. **The headless rig and the test harness** -- `scripts/run-headless.sh`,
    `headless.conf`, `rig-input` and `iris::harness` live in ai-app's iris
    submodule, not in canonical Iris. Until they are extracted, canonical Iris