You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Clear stale meter-brand suggestions on retake and skip #94
At 916838f, retakeCloseUp, skipCloseUp, and close-up entry clear meterNumber but can retain the prior meterBrand suggestion. Retake followed by skip leaves the old suggestion beside a skipped number. No current scene or packet export consumes it, so this is local state cleanup, not a transmission defect.
Clear the brand alongside the number in the real and demo engines, and add a retake-then-skip assertion. Preserve number candidates when the explicit brand-reject action is used.
The manager explicitly deferred this P3 under the 11:00 CDT convergence rule. It does not block #89 integration once the 6.68 focus threshold, 44-point reject width, and required checks pass.
Verified at PR#89 head0a3a05e: meterBrand is only exposed when meterNumber is choose or confirmed, and nil during retake/reading/skipped states. The getter makes the reported stale visible-state case unreachable. Current-head CI passed on attempt2; no separate UI-test gate was added under convergence. Closing as addressed, not as a claim that all close-up lifecycle behavior is verified.
Activity
ios: 44 pt reject target, and the brand lives only beside its number
SamGu-NRX commentedon Sep 27, 2026
Verified at PR#89 head0a3a05e: meterBrand is only exposed when meterNumber is choose or confirmed, and nil during retake/reading/skipped states. The getter makes the reported stale visible-state case unreachable. Current-head CI passed on attempt2; no separate UI-test gate was added under convergence. Closing as addressed, not as a claim that all close-up lifecycle behavior is verified.
Document the dense, coverage, and scene stages. (#94)