Files
BT411/scratchpad
arcattackandClaude Opus 5 d3e724c254 cut 4.11.584 for tonight, and PROVE it still plays with the 554 everyone has
The merge brought Cyd's cockpit refit into the build testers will run tonight,
so the question that decides the evening is whether a 554 client can still join.
Rather than reason about it, tested it: extracted the real BT411_4.11.554.zip
and ran ONE 554 pod and ONE 584 pod against the same relay through a real
launch.

  WIRE-COMPATIBLE.  Both staged, both REGISTERED, the relay launched the mixed
  round, and 30s in both were still registered AND still on the UDP fast path
  (registered [2, 3] udp-known [2, 3]), zero drops, both processes alive.
  => NOBODY HAS TO UPDATE TONIGHT.  The new zip is an upgrade, not a
     flag day (unlike 554, which changed the scoreboard wire format).

Supporting evidence for why that held: the merge did NOT change the attribute
table's shape -- 36 ATTRIBUTE_ENTRY(Mech,...) rows before and after.  Cyd's
crouch work POPULATED an existing pad slot (0x37 DuckState, previously
attrPad), so no index shifted.

The zip itself (dist/BT411_4.11.584.zip, 47.0 MB):
  * built clean at HEAD 2b0506d, 0 compile errors, the 40 /FORCE-tolerated
    externs byte-identical to every prior build;
  * 34-check document audit passes, now including "the README does NOT
    advertise the RGB keylight" since that feature was unshipped today;
  * CLEAN-EXTRACT BOOT from the packaged zip: 0 faults, GLASS profile with the
    cockpit surround, environ.ini written, 74-key board loaded, and
    content\bindings.txt generated carrying the "# bindings-board 2" marker --
    i.e. a fresh install lands on the new board with the migration armed;
  * the zip ships NEITHER bindings.txt NOR operator_secret.txt (verified) --
    player files and a live credential both stay out;
  * screenshot from the extracted build confirms the refit renders: under-glass
    buttons, corrected hat labels, both weapon columns, radar centred.

One harness bug fixed here: the drop check matched a bare "dropped", which also
matches the stats line's own counter -- "(dropped 0, tcp-fallback 0)" -- and the
operator's control socket closing normally.  It reported a compatibility FAILURE
on a perfectly healthy mixed round.  Now matches real pod drops only.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-07-26 20:10:24 -05:00
..