Player request: more of the RIO buttons should protrude from the displays so a
FLASHING lamp is easier to notice. BTRioBankMetricsFor now adds a flat +10px
to `strip` -- the lamp bar -- AFTER the scale; BT_RIO_PROTRUDE=<px> tunes it
and 0 restores the pre-2026-08-14 geometry.
FLAT, not scaled, deliberately: the ask is on-screen noticeability, and the
surround runs the glass at HALF scale where the strip lands on the 6px floor --
a scaled bonus would give the least help exactly where the lamps are smallest.
The floor above it already trades strict proportionality for legibility on this
field; this is the same trade, sized by the players.
Scope falls out of the geometry -- only `strip` moves, so:
- RED MFD buttons and YELLOW radar buttons (+ the radar foot row) grow;
- they grow OUTWARD ONLY (the layout anchors the inboard edge), so
under-glass depth, button WIDTH and every press target are unchanged --
this is a LONGER bar, not a fatter face;
- BLUE flight cells lay out from cellW/cellH and never see it.
Verified [T2] by BT_RIOBANK_LOG A/B + surround screenshots: Heat MFD top button
y 21->11, h 126->136 with its bottom edge FIXED at 147; bank bounds 252->272
tall (all five MFDs), radar 252->272 wide; flight-bank bounds byte-identical;
no negative coordinates on any bank; imagery still wins every pixel it covers.
The exploded glass windows size their client to bank.bounds, so they simply
grow with it.
Relation to #172: the alert RING (BT_ALERT_RING, default off) answered the same
night-16 miss after a "+8px grown-face bloom" was rejected on the bench as "the
button got fat". This is a different shape -- the lamp keeps its width and
shows more of its own bar -- so the ring stays optional. Desktop-glass
affordance; the pod's buttons are physical and backlit.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>