pagination-evidence¶
Provenance¶
- Source:
.spec/spexcode/spec-dashboard/dashboard-ui/review-surfaces/review-chrome/pagination-evidence/spec.md - Source SHA-256:
2c3c4cc8d51e8997312418070cc96f013064c22c9a5e55d66aeec71c2f5c7d42
pagination-evidence¶
The product evidence starts before either review page opens. It records the first /api/graph response and
rejects any Issues/Evals row, scenario, or measurement arrays that could reconstruct a main list; it then opens
Issues, trunk Evals, and scoped Evals and records every response's status, bytes, current-page item count,
total, navigation fields, and revision beside the rendered row count. Thus a bounded page endpoint cannot
hide a simultaneous full-list bootstrap.
The same real Chromium journey exercises the observable GitHub contract: anchor PUSH, both page-1 history forms, refresh and Back/Forward replay, filter reset, last and overflow pages, detail Back scroll restoration, loading/failure, and the shared scroll owner below the sticky status/header stack. A second 390px recording measures wrapping, target geometry, overflow, keyboard activation, and the named accessibility navigation. The run emits desktop/mobile videos, screenshots, a timeline, and the machine-readable network ledger used for before/after review.