Block a user
F1 — measure the held-direction repeat: initial delay and interval, in frames
No check in this repo reads a real input device — all four feed their own events
feat(port): adopt the measured held-direction repeat rate (F1)
✅ Verified by hand: "Works now and speed is good."
That is the only instrument that could settle either half, and it settles both — the stick now repeats, and 0.134 s reads as the "medium…
feat(port): adopt the measured held-direction repeat rate (F1)
Found it, and it was not the rate. 07d83c42.
held_direction()'s own comment says "Polled at the DEVICE, never through Input.is_action_pressed". It was not. The d-pad and keyboard…
feat(port): adopt the measured held-direction repeat rate (F1)
F3 — which cue, if any, does the title play? (positive control required)
re: land the F5/F6 title-clock corpus (docs/re, reference data, sylpheed-formats)
re: land the F5/F6 title-clock corpus (docs/re, reference data, sylpheed-formats)
Pushed the mechanical half — d394ba6a, cae0a4bd, e6266b19. Verified in
the CI image (--cpus=6 --memory=7g): **check 0 · build 0 · test 228 passed /
0 failed / 14 ignored · clippy 0 · WASM…
test: make $SYLPHEED_DISC an actual control, not a decoration (#16 remedy 3)
feat: propose-work — push, open the PR, and move the issue, in one command
docs(agents): a red PR is the next unit of work, and check the workspace