Phase 9c is done, and with it the Asset Bridge. §16's row 9c records what the leg
actually was, and §17.17 what it found.
The site is the only repo whose checks read the platform over the API instead of
describing it, so its starting state is a measurement rather than an opinion:
- `checkFacts` red in **ten** places — the protocol in all three independent reads,
the bundle triple, and the three releases the cutover cut. `moduleApi` and the
capability list did not move, which is §17.16's finding restated by a different
mechanism.
- `checkReference` red in **nine nobody planned for** — every `Bridge.cfg` key phases
5, 6 and 7 added, none of them ever mentioned on the public reference page. No phase
row in this plan could have caught that: the rows name the repos a change edits, and
this is a repo that only describes them.
Two corrections only prose could make: §17.15's "five repositories" had become a page
on the site that named `website` among them (protocol 8 touched four, and core's
absence is the interesting half), and the site said the bridge has two ways in when the
asset plane is a third — a paged bulk read on the reply path, which must not ride the
event stream for a structural reason rather than a throughput one.
The defect the phase found is a version pinned in a rig: `seedDemo.mjs` pinned protocol
**4** under a comment explaining a debt since paid. It reads `platform.json` now.
Screenshots retaken against the real shard (D42 holds): 1,095 portraits in 2.1 s,
67,496 names in 1.4 s, 313 item pictures in 0.8 s.
Site: RunicGateway/runicgateway.com#31.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4
wtclaude
bc5b43e1a4