Integrated candidate recheck — 2026-10-09
The candidate evidence
identifies the normal yl3si5ak system, q2rxmp Rust client and actual g7xzww
Sway executable/library separately from their service wrappers. This is the
same normal boot the operator accepts for HDMI fill and Home/All Apps/Settings
targets. It is a later candidate than the dated October 1 baseline; old and new
captures retain their own identities, output sizes and evidence classes.
Severity and before/after reconciliation
The findings ledger has no P0/P1 assignment. The coordinator rechecked all four listed findings instead of inventing a high-severity finding to satisfy the recheck task. Current captures were visually inspected; the original baseline Home was also inspected for the clock comparison. None establishes a physical motion, reach or readability result.
| Finding | Baseline → current evidence | Review result and remaining owner |
|---|---|---|
| UX2-01 clock emphasis | Old 568×1232 Home over a bright wallpaper → current 800×1280 Home over the selected dark waveform wallpaper, same normal boot as the new native set. | Large outlined time remains visible. Different theme/layout/geometry preclude attributing the pixel difference to a clock refinement. This remains optional taste, with no selected implementation or new optical contrast claim. Existing clock-design research owns any future user-selected exploration; the accepted Home capability stays closed. |
| UX2-02 missing current deck image | Older f39cb7eb Overview / baseline capture gap → current overview.png, actual g7xzww service compositor and q2rxmp client. | The current-image gap is resolved for the observed one-Terminal-card state. Label and content are visible with no blank card. Multi-card motion, refusal and optical tracking are outside this settled image and retain coherent-shell/frame-budget owners. |
| UX2-03 output-picker density | Old injected/native open picker → current initial/loading and later loaded Settings images. | Loaded current Settings has recognizable sink/volume/keyboard/motion/power controls. The picker itself was not opened in this recheck, so its optional density question is not cleared or reported failed. Existing coherent-shell Settings review owns it. The one-second loading image is superseded as the settled state by the later loaded capture; no persistent loading issue is inferred. |
| UX2-04 eight-entry drawer fixture | Old eight-entry host render → current native 19-entry, six-column catalog. | The realistic installed catalog and search are now visible. Quiet space remains after the finite catalog; whitespace alone is not a defect. Overflow, search execution and physical label reading remain separate evidence gaps under the accepted launcher capability/current journey review. |
No new P0/P1 defect is established by these captures. The functional current Home/All Apps/Settings report is reused exactly, without turning injected Overview/Settings commands into real-finger interaction. New optical/finger claims remain UNVERIFIED; no camera is available in this focused native review. The named camera procedure remains with the corresponding runtime physical owners if a changed motion or reach behavior needs that proof.
Remaining journey coverage and next work
The operator now confirms the requested current keyboard show/type/hide, two-app Overview switch/Home and media play/stop/Home functional journeys in operator-report.json. Task 2.2 is complete as a journey review with explicitly retained unknowns. The captured catalog has no named Help/System entries, so the older matrix’s separate routes are not claimed as walked. The actual current recovery destination is Home, with device controls exposed in Settings. Empty/stale/error/denied, refusal, keyboard-visible reach and cold startup are explicit unknowns, not invented successful journeys. Use the current journey review for the full coverage map.
The three priorities keep their existing owners: measured theme-picker motion; integrated card/keyboard functional and physical review; theme-token/control consistency. This analysis implements none of them and proposes no duplicate renderer or feature scope. The current-image portion of priority 2 is now done; its functional/physical remainder is still explicit. The reports and candidate recheck can land as a bounded checkpoint while those gates remain open.