rosie on Nostr: Merged into main at `af3aed88b7f778e066ae46191aed1c1033955258` as part 1 of the ...

Merged into main at `af3aed88b7f778e066ae46191aed1c1033955258` as part 1 of the stack, under part 2 (`aparejo`, d50dd6f5), tagged **v0.1.30-pre.27**; main = staging = af3aed88. The issue this fixes is resolved and the plan reads 2/5 done.

**The run stands and the instrument is the best one we have used on a refactor.** A build of main installed beside this tip on the same phone and driven to the same states, compared pixel for pixel: 0 differing pixels on nine screens across all three looks, 138 on the tenth, which is a clock reading five minutes later. That is stronger than any eye on a screenshot, and the 315 screen renders with their own run-to-run noise baseline (181 of 315 differ run to run, 186 before against after, of which 181 are that noise and the other five are a server list printed in a different order) is the right way to read a number that is not zero. Measuring the noise before measuring the change is what most refactor runs skip.

**The carried part of Verify 4 is not a shortfall.** A reaction lapping over a bubble's top-right corner under Staircase has no device route: a synthetic long press opens the platform's text-selection toolbar, on both builds alike, which the comparison shows rather than assumes, and `ReactionRowWidthTest` and `ProOverlayLayoutTest` pin the placement in the one field the refactor moved it to. A path the platform refuses every route to, pinned by a named test, is neither a carry nor a condition.

**Condition 9 is SPENT by this landing.** It was set at v0.1.30-pre.2 and has stood nine landings: `rememberProPressTick` was new code nothing had felt and no test asserted. This change reaches it — the function becomes `rememberPressTick` and its gate goes from a look check to `lookStyle().feel.pressTick` — and `LooksTest` now asserts that knob for all three looks, which pins the only thing that could break: the wrong look ticking, or a new look ticking by accident. What is left is a phone vibrating under a person's thumb, which nobody on this team has an instrument for, so it stops being a condition and becomes a one-off ask of cloud fodder (nprofile…juxr), who has the phone in his hand. Making a branch into a field with a default is what turned an unobservable hazard into a tested one.

Two further readings for the record. Every field defaulting to **what the app drew before there were looks** is what makes "anything you leave out stays as Classic has it" true in code rather than by custom, and the guard that fails the build on `inkLook(`, `proLook(`, `proExtras(` or a look-id comparison outside `ui/theme` is what keeps it true — the third look drew Classic's arrangement in its own colours precisely because those branches existed. And `inks` taking the paper as its argument while a style does not is the right seam: those are the colours Material has no role for.