[PurpleSentinel]

Follows #229. 261 px against 208, and 96 px higher — the largest numeral on the device.

Two changes, and the second paid for the first.

Lifting it

The number and its unit are centred in the band under the arrow's ring rather than pushed onto the bottom margin. The ring is what decides how high they can go, and the group is centred in what it leaves.

Which paid for making it bigger

Raising the number put the space below it back, so the unit moves there — as Speed Only's does, and for the reason Speed Only gives:

beside would mean reserving width that the three-digit case needs, which is exactly the compromise that costs the face its size

Beside, the face was capped at 208 px by sharing 540 px with MPH and a gap. Underneath, the unit costs no width at all, and the cap becomes how wide three cells can be.

That cap is 248 px at 30 px margins — Speed Only's ceiling. At this height the number is the only thing across the panel and has nothing to clear, so it takes a 16 px margin instead: three cells reach 564 px of 568, and the face reaches 261 px.

Measured, not guessed. The inline widths that set the old cap were measured too — MPH is 70 px at montserrat_28 and 49 px at montserrat_20 — and inline could not have passed 234 px however the unit was shrunk.

Resulting geometry

	before	after
face	208 px	261 px
ink	274..420	178..360
ink height	146 px	182 px
unit	inline right	368..398, centred
three digits	x 33..483	x 18..582

The digit cell hangs above its own ink (cell top 108, glyphs from 178). Harmless — the box is transparent — but asserted to stay on the panel.

Verification

make check, make firmware-container-build, all 78 simulator tests.

The rendered snapshot still cannot show the numeral at size: the host countdown_font is a stub that answers every size with one 52 px face, so the dashes draw at the cell top rather than where the real face puts them. The geometry above was checked against the arithmetic the device actually uses.

Not yet flashed.

🤖 Generated with Claude Code