re: record the MiscBin name resolution in the backlog

docs/re/BACKLOG.md

@@ -409,8 +409,26 @@ search cannot find a *schedule*.
   `tools/re-capture/mcol_probe.py verify` reproduces it
   ([`data/mcol-verify.txt`](data/mcol-verify.txt)); `mcol_probe.py obj` exports
   any object as a Wavefront OBJ.
-  ❔ Still open: the objects are **not name-resolved**, so the map each belongs
-  to — and the `MCOL`↔`REGN` pairing — is unknown, as is the runtime consumer.
+  ✅✅ **And all 40 `MiscBin` entries are now name-resolved (2026-08-26).** The
+  names are the `MapPath` / `MapMesh` / `CollisionMeshes` values of the per-stage
+  `StageResource` object (IDXD schema `3c9ae32e`, in every
+  `GP_MAIN_GAME_<lang>.pak`), each hashing with the ordinary pak `name_hash`
+  straight to a TOC entry — **40/40, no collisions**: 11 `<stem>.rgn`, 11
+  `<stem>.col`, and the 18 remaining blobs as `CollisionSet_S01…S16` /
+  `_Tutorial` / `_test.bin`. The `.pe` string table at 651 540 was the way in.
+  This **upgrades the pairing** from "matching bbox/cell-size distributions" to
+  an object-to-object link: a phase names one `.rgn` and one `.col`, and
+  **11/11** share a stem and agree exactly on bbox and cell size.
+  It also checks the format work from outside: `mapmesh_box_500km.col` is the
+  object decoded as 8 vertices / 12 triangles spanning exactly ±250 000, and its
+  name says 500 km — so **one world unit is one metre**. **70 of the 87 phases**
+  use that bare box; `_AsteroidVolume_` names the rest.
+  `tools/re-capture/miscbin_names.py <root> [--pairs]`
+  ([`data/miscbin-names.txt`](data/miscbin-names.txt)).
+  ❔ Still open: the 18 `CollisionSet_*.bin` are named but **not decoded** (magic
+  `0x00000810`, all exactly 1 675 148 bytes). The runtime consumer now has a
+  name — `CMapColliderBridge` in the `.pe` RTTI at 9 044 264 — but has not been
+  followed into the code.
   See [`structures/mcol-collision.md`](structures/mcol-collision.md).
 * 🔴 **`hidden/DefTables.pak` is NOT it** (checked 2026-08-24). The three
   unnamed schemas are more **model/render** tables in the same vocabulary as the