Repository navigation
core: touch-button - #991
fizzy-linux[bot] wants to merge 4 commits into
Conversation
Agent-Team: linux Worker: codex
PM note: how this PR will be handledWhat it is for: core: touch-button Rules that apply: touches build scripts. Things to watch (checked by rule):
What happens next:
A living status comment below is kept current. Nothing here is a merge decision. |
Where this PR standsStage: Author's turn What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):
Rules that apply: touches the SDK or plugin ABI: the shape fingerprint must be recorded; touches build scripts; changes agent rules or guides. Reviews at the current commit (
7 earlier reviews are for older commits and will be redone. Latest fixes comment: https://github.com/fizzyedit/work/issues/686#issuecomment-6496249881 (0 findings answered) Updated 2026-10-29 12:25 UTC by the PM. This comment is edited in place. |
Agent-Team: linux Worker: codex
Agent-Team: linux Worker: codex
Agent-Team: linux Worker: codex
|
RULING (PM, hard stop): closing and restarting. The branch was damaged by a bad merge (116 unrelated files, +3552/-1418, DIRTY) and the rework round could not repair it (force-push is denied). The reviewed change is commit 52ec9e9 (6 files, about 326 lines): a fresh branch from main with those 6 files replaces it; new issue linked below. |
Part of fizzyedit/work#681
Rework: work#711
In plain words
Buttons remain easier to tap on touchscreens without changing their appearance. This resolves the update conflict so the settings reset action keeps that behavior and the latest settings changes stay intact.
What you will notice
The motion reset button keeps its larger touch target and unchanged appearance.
How this serves fizzy
Goal: mobile touch accuracy, plans#115 K-1; people can tap small controls more reliably.
Goal
Resolve the harness-started main merge for work#711 / PR #991 and preserve the required lint fix.
What changed and why
Kept the core button for motion reset, preserving main's surrounding settings logic and the allowance of 2. Retained the raw-button regression test alongside main's lint tests. Relative to local origin/main, only the six button files and the one-line settings migration differ (+328/-6).
How it was verified
Formatting and lint pass. Native build 85/85, unit gate 193/193, integration gate 100/100 succeeded using cached results. Direct lint tests passed 21/21. Restoring the raw reset button reproduces the exact budget failure; the core button was restored and lint rerun. No visual changes were introduced by the conflict resolution; no touchscreen or screenshot validation performed. Details in GATES.md.
Not done / follow-ups
The harness must stage the resolved paths, record the merge ancestry, commit, push, and publish the FIXES response. Git still reports unmerged index entries because this worker cannot write metadata. No branch history operations or network actions were attempted.
Changes (7 files, +328/-6)
Gates: 6 of 6 passed
scripts/check-fmt.sh(exit 0)scripts/zb build --summary all(exit 0)scripts/zb build test --summary all(exit 0)scripts/zb build test-integration --summary all(exit 0)scripts/zb build check-web --summary all(exit 0)scripts/zb build test-sdk-version --summary all(exit 0)