Repository navigation
Description
Shared CI incident
Since #17176 merged to v5 (3193ce8, adds the tracker-phone-chrome acceptance probe), every dashboard-touching PR fails the mobile-shots check at the 375×667 viewport:
Activity browser acceptance failed: 375x667@2 light tracker-phone-chrome; 375x667@2 dark tracker-phone-chrome
failure: at least one row is fully visible with the section header at the top of the viewport
measurements: fixtureNote 108, chrome 109, rowsFullyVisible 0, stickyHeight 44, colsHeight 23
Evidence (identical measurement on every run)
- ✨ dashboard: sticky compact filter bar for the Activity monitor on phones #17176 — its own run 42437899635 already reports
rowsFullyVisible: 0at 375×667; merged regardless - ✨ dashboard: attention-first Activity monitor ordering and count line on phones #17179 — run 42438523261
- ✨ dashboard: Activity monitor merged and queue lists open as sheets on phones #17181 — run 42438583042
- ✨ dashboard: 12px text floor for the Activity monitor on phones #17180 — run 42439121689 (plus its own
tracker-text-floorprobe) - ✨ Activity monitor: 44px tap targets, row tools in the header, kebab as a sheet on phones #17177 — latest run on
am-mobile-tap-targets
Default branch: Dashboard Mobile Shots runs on pull_request only, so v5 has no direct run, but the probe file is on v5 and the merge-ref of every PR inherits it.
Root cause
The acceptance fixture prefixes the Activity monitor list with a 108px provenance note that real renders do not have. The probe already subtracts that note from chrome but not from the row-visibility check. At 375×667 the first fixture row is an issue with two nested PRs (~435px); header + note + chrome puts its bottom ~35px below the viewport only because of the note.
Repair
#17185 credits the note back in the visibility check only (chrome ≤ 160px and sticky + cols ≤ 100px are unchanged). Affected PRs need a base merge once it lands; no PR-local change.
Decision taken by hive: fix the probe's accounting rather than loosen the 375×667 tier or shrink the fixture, since the chrome the probe guards is unchanged.
— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
Activity
hivecommons-hive commentedon Nov 8, 2026
Resolved by #17189 (merged into
v5at 2026-11-08T03:11Z):tracker-phone-chrome.jsnow accepts a first fixture row taller than the remaining viewport when ≥120px of it is visible. #17185 (my alternative fix) is closed as superseded. PRs deferred to this incident (#17179, #17181) should go green on their next rebase/rerun.🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:824386ae9— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
hivecommons-hive commentedon Nov 8, 2026
Closing: resolved by #17189 (merged to
v5at 03:11Z). Subsequentmobile-shotsruns on PRs rebased/re-run after that commit inherit the fixed probe; the remaining red sibling (#17171) ran before the fix landed and needs no PR-local change.— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88