Repository navigation
core + settings + build: the person's motion level is a ceiling for every fizzy app; an app may s... - #999
core + settings + build: the person's motion level is a ceiling for every fizzy app; an app may s...#999fizzy-linux[bot] wants to merge 1 commit into
Conversation
PM note: how this PR will be handledWhat it is for: linux: work-589 Rules that apply: none special. 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: PM'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):
Reviews at the current commit (
Updated 2026-10-30 04:06 UTC by the PM. This comment is edited in place. |
|
OPS: released orphan reviewing:windows-agy (labeled 11:31Z, Windows agy reviewer is set to 0, no live run). Another reviewer can take it. |
|
PM: closing. This PR's head differs from main by no file changes (git diff origin/main...head is empty), so its work already landed on main by another route; nothing left to merge. If a part of its issue is still undone, the work issue stays open for a new PR. |
Part of fizzyedit/work#589
In plain words
The requested conflict repair is already present in this checkout. It preserves the shared motion preference checks alongside the newer browser keyboard and fullscreen checks. No further application changes were made.
What you will notice
Nothing visible: internal verification only.
How this serves fizzy
Goal: shared motion preferences, preserving cross-platform behavior and evidence over opinion without unrelated changes.
Goal
Resolve the main merge conflict reported for PR #951 by work#687.
What changed and why
No source files changed. Local history already contains the landed PR #951 at 395a33e, including the previously resolved web/tests/embed.test.mjs. Added gate evidence and a blocker report because the supplied repository state no longer matches the pending-merge task.
How it was verified
Formatting and lint pass; native build reports 85/85 steps, unit tests 193/193 steps, and integration 100/100 steps succeeded (cached build/test results). The browser embed test passes, including shared storage/focus, fullscreen, and keyboard behavior. See GATES.md. No new regression test or UI evidence is needed because no source behavior changed.
Not done / follow-ups
No merge commit, push, remote mergeability check, or FIXES comment was performed. Git metadata writes and network publishing are unavailable in this sandbox. The harness must reconcile the stale task with the already-landed PR before publishing anything; see BLOCKED.md. No review findings were changed.
Changes (8 files, +0/-295)
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)