queue: OPEN Q64 -- Leathermint isometric build; one design decision for Alexander (zoomed worktable or whole workshop) and the honest distance to milestone 1. The ask (L' Artisan, 2026-10-20 15:14Z) reached the troupe only as chat and the artifact shipped at 15:24Z with NO queue item and no issue, so the follow-up had nowhere to live in the open set -- this record fixes that, not the build. LIVE: https://leathermint.alexanderwhitestone.com/v2/ -- 18505 B, Phaser 3.80.1 vendored locally (1181917 B, no CDN at runtime), 390x844 phone-native frame, isometric 7x7 diamond floor with two walls, four stations as separate interactive objects with hit areas and depth sorting, one contextual panel on a single pointer path, HUD Cash/Leather/Cardholders only, sim state with zero Phaser references, products as data, localStorage; v1 at / untouched (19636 B, mtime 14:49:05Z). VERIFIED BY DRIVING IT with real taps at 390x844 dpr 2: 8,000 ms craft -> leather 3->2 and cardholders 0->1; 15,000 ms listing -> cash 100->145 (+45) and cardholders 1->0; progress bar in flight; zero page errors; scrollHeight == innerHeight -- reproduced independently by a second lane. DISTANCE TO MILESTONE 1: JS in one file with vendored UMD Phaser, not TypeScript + Vite; procedural vector stations, not chibi sprite art; no day clock, order queue, furniture progression, reputation or photo-trading. STATUS OPEN awaiting Alexander's answer; build held by the pipe. No issue/PR/release surface beyond the static path; no secret printed.

docs/queue-index.md

@@ -4,7 +4,7 @@
 
 **What this is.** One row per `## ` section of `WORK-QUEUE.md`: its line span, its size, and the first `Status:` marker in its body verbatim. Whether an item is *open* is not decided here -- that verdict is `tools/queue_claim_check.py`'s, and this document does not overrule it.
 
-**What it exposes.** The queue is two-tier. 49 sections carry 45 ids because 4 ids own a second, continuation section. A further **9 ids have no heading at all** and are opened as records nested inside another item's section -- so grepping `^## Q41` finds nothing while Q41 is a live item the file names 28 times. Those are listed in their own table below.
+**What it exposes.** The queue is two-tier. 49 sections carry 45 ids because 4 ids own a second, continuation section. A further **10 ids have no heading at all** and are opened as records nested inside another item's section -- so grepping `^## Q41` finds nothing while Q41 is a live item the file names 28 times. Those are listed in their own table below.
 
 | # | id | lines | bytes | role | title | first `Status:` |
 |---|---|---|---|---|---|---|
@@ -56,7 +56,7 @@
 | 46 | Q44 | 6162-6705 | 88496 | opening | The pin class: redirect every constant composed from the live data root, not only `SNAPSHOT_PATH` *(Helm lane; opened 2026-10-12 by the pipe, per Q43's own closing sentence — "extend the redirect … | DONE 2026-10-12 — `recoveries/helm-root-redirect.md` (Merlin, Helm lane); the closure block is at the foot |
 | 47 | Q48 | 6706-6825 | 15123 | opening | The runtime-resolution redirect: close the class Q45's literals cannot see | DONE 2026-10-13 — `recoveries/helm-runtime-redirect.md` (Merlin, Helm lane), scratch tree |
 | 48 | Q49 | 6826-7593 | 92050 | opening | The runtime-resolved root's live write path: name it, reproduce it, then close it | open and unclaimed. Opened by the pipe 2026-10-13 |
-| 49 | Q45 | 7594-10305 | 465280 | opening | §9 follow-on — the home-directory channel *(Helm lane; Merlin)* | -- |
+| 49 | Q45 | 7594-10320 | 468233 | opening | §9 follow-on — the home-directory channel *(Helm lane; Merlin)* | OPEN — awaiting Alexander's zoom/whole-shop answer; build is the pipe's. |
 
 ## Ids with no `## ` heading
 
@@ -73,6 +73,7 @@ Opened as records inside another section. `line` is the record's own opening lin
 | Q52 | 7167 | 7167 | 90 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q53 | 7292 | 7246 | 140 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q63 | 9918 | 9909 | 17 | Q45 | BULLET+BOLD | BOLD-LEAD |
+| Q64 | 10308 | 10308 | 1 | Q45 | BULLET+BOLD | BOLD-LEAD |
 
 **Not in this document.** Ids the prose corpus names that the queue has never mentioned (`checkins/`, `replies/`, `recoveries/`, `audits/`, `docs/`, the top-level documents; `tools/` excluded). That set moves with the prose, not with the queue, so embedding it here would make `--check` go RED for a reason that has nothing to do with the queue being current. It is reported on demand: `python3 tools/queue_index.py --outside`.
 
@@ -229,6 +230,15 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "refs": 17,
    "section": "Q45",
    "shape": "BULLET+BOLD"
+  },
+  {
+   "first_mention": 10308,
+   "form": "BOLD-LEAD",
+   "id": "Q64",
+   "line": 10308,
+   "refs": 1,
+   "section": "Q45",
+   "shape": "BULLET+BOLD"
   }
  ],
  "preamble": {
@@ -236,9 +246,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1357541,
- "queue_lines": 10305,
- "queue_sha256": "f0feef0b6a1c7c24054ee159a8d8ad2dc833eab8f82a865291b645f21580616d",
+ "queue_bytes": 1360494,
+ "queue_lines": 10320,
+ "queue_sha256": "936e76bb29c0eb1d60524b6cb1617fddfed7a790de17cca3a56f7427d7f02fe5",
  "sections": [
   {
    "bytes": 3139,
@@ -817,15 +827,15 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "The runtime-resolved root's live write path: name it, reproduce it, then close it"
   },
   {
-   "bytes": 465280,
-   "end_line": 10305,
+   "bytes": 468233,
+   "end_line": 10320,
    "id": "Q45",
    "line": 7594,
-   "lines": 2712,
+   "lines": 2727,
    "role": "opening",
    "role_detail": "",
-   "status": null,
-   "status_line": null,
+   "status": "OPEN \u2014 awaiting Alexander's zoom/whole-shop answer; build is the pipe's.",
+   "status_line": 10320,
    "title": "\u00a79 follow-on \u2014 the home-directory channel *(Helm lane; Merlin)*"
   }
  ]