A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I1021
A browser proves the interface, at the widths people use
Where it stands
devtask.issue- Readiness
- blocked 2 of its dependencies are not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
5- Waiting on
- Holds back
- Behind it in all
2- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I1014 | I1014 is not DONE |
| issue | I1016 | I1016 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Extend the existing browser checking to cover navigation on desktop and mobile, search and filtering, the detail view, graph initialisation, conditional runtime exposure, link integrity and console errors.
- Why
- Everything in this milestone is finally judged by whether a person can open it. Server-side tests cannot see an overflowing table, a menu that does not open or a script that throws on load.
- Now
- scripts/ui audits every surface the executable serves, not only static directories: scripts/lib/ui-routes.mjs derives a served surface's routes from its own anchors, crawled from its mount, and both browser instruments import it, so the Cockpit, the home page and the Swagger shell are inside the ADR 0022 width, contrast and accessibility sweep (PR #178, 2026-09-10). scripts/cockpit-probe keeps the shell, the security headers, the design fingerprint, the interactions and the no-JavaScript claim. What this issue still owes is its own assertions -- search and filtering, the detail view, graph initialisation, conditional runtime exposure and link integrity, at named viewports -- and its dependencies I1014, I1015 and I1016 are not recorded as done. Measured on master 6042f4286, 2026-09-10.
- Wanted
- The probe covers the derived surfaces at representative viewports, uses stable selectors and runs in CI.
- Done when
- unknown: the record declares no `completion`
- Risk
- Browser tests are the flakiest thing in any suite. Bounded waits on stable selectors, and no sleeps.
Acceptance
- Desktop and mobile navigation, search and filtering, the detail view and graph initialisation are all exercised
- Representative viewports from a narrow phone to a wide desktop are asserted, including the absence of horizontal overflow
- The runtime-only surfaces appear when a backend is present and are not offered when it is not
- Internal links resolve and the console is free of errors
- Selectors are stable identifiers rather than presentational classes
- Validation
scripts/cockpit-probe- Evidence required
browser_coverageviewport_assertions- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
scripts/cockpit-probe- Not
Pixel comparison of a rendered graphSelectors coupled to presentational class names- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-06
- Updated
- 2026-09-10
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.