Two register-terminal pain points from Narong's v0.2 batch, both verified on prod — H5.2 with physical keyboard + paste simulation, H5.6 with end-to-end latency timing.
31c177d.
Verified on prod by driving the unlock with page.keyboard.type + Enter (no on-screen
button clicks) AND by dispatching a synthetic ClipboardEvent("paste").
Both unlock paths (unlockRegisterAction + unlockRegisterAsUserAction) now fan their
independent DAO reads through Promise.all. Measured PIN-Enter → screen-transition latency
on get-coffee Pro, warm Worker:
router.refresh() re-running ~20 DAOs in the register page server component — that's structural rework reserved for a future slice.
ClipboardEvent("paste") with "5678": 4 dots filled, no on-screen taps
page.keyboard.type("1379"): 4 dots filled, ready to EnterClipboardEvent fills the PIN dots| test-phase1-prod.mjs | 11/11 |
| test-phase2-sso-outdoor-prod.mjs | 6/6 |
| test-phase2-cafe-multishop-prod.mjs | 6/6 |
| test-m1-prod.mjs | 10/10 |
| test-r7-prod.mjs | 14/14 |
| test-r8-prod.mjs | 4/4 |
| + test-v0-2-slice-c-prod.mjs | 8/8 |
| Total | 59/59 |
app/(authed)/pos/_components/lock-screens.tsx ·
lib/actions/register.ts