Lane B R39: §39 note — the classic fetch-delta arm on the magpie GLB, as a table

The network-log assertion behind the previous commit, written into the lane notes so F's gate can
read the numbers rather than re-derive them: default boot 1 magpie GLB request (asset 'glb', 894
tris) · ?classic=1 0 · ?magpie=0 0 · ?noassets=1 0 (asset 'primitive', 182 tris).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
m3ultra 2026-08-03 21:40:42 +10:00
parent f0b9a1d30f
commit 43c7f4281e

View File

@ -277,6 +277,19 @@ inferring it from a fetch.
of hovering over it. And `folded` (the 0.42× X squash that makes the primitive's flight geometry
sit) is **1 for the GLB**, which is already the perch pose.
3. **THE FETCH IS ARMED BY `createMagpie()`, NOT BY THE IMPORT — and that is the classic covenant.**
`index.html` imports this module unconditionally and gates only the *construction*, so
`furniture.js`'s module-scope load shape would have put a **brand-new GLB request on the
`?classic=1` boot** — a fetch delta on the one boot that is not allowed one. Asserted on the
**network log**, not on the code:
| boot | magpie GLB requests | `state.asset` |
|---|---|---|
| default (and `?magpie=1`) | **1** | `glb`, 894 tris |
| `?classic=1` | **0** | *(never constructed)* |
| `?magpie=0` | **0** | *(never constructed)* |
| `?noassets=1` | **0** | `primitive`, 182 tris |
**A defect my own edit introduced into ANOTHER LANE'S TOOL, caught by running it.** A module-scope
`loadGLB` fires GLTFLoader's fetch path under node, and Lane E's `pipeline/dump_bird.mjs` imports this
module unmodified — `ReferenceError: ProgressEvent is not defined`, E's A/B tool dead, my fault. The