Skip to content
Motir
Start free

moooon

Motir

Vibe your whole project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.

  • Vibe Project
  • Open Source
  • AI Agent
  • AI Loop
1
requests
0
upvotes
145
planned
1,361
shipped
Follow  — continues on app.motir.co
Request a featureAtom feed

← Motir · Work items

MOTIR-311Done

5.6.3 The loaded issue at scale — bounded-read + bounded-DOM specs and the full-page strict a11y sweep over every Epic-5 surface at once

Estimate: 30m · Depends on: 5.6.1, 5.1.7, 5.2.8, 5.3.8, 5.4.11, 5.5.5

The finding-#57 sentinel for Epic 5: tests/e2e/collab-at-scale.spec.ts over the 5.6.1 loaded issue.

Bounded reads: opening the loaded issue's detail page issues only PAGED requests — comments (one page + Show more), attachments (one page + Show more), History/All (one page each, the composite cursor on All), watchers (count + paged list on popover open) — asserted at the network layer (no response carries the full collection; request census against the helper counts). The rail renders within the 50-field cap with "Show more fields" for the empties. Bounded DOM: the first-paint node count stays within a budget derived from the page sizes (the board-at-scale assertion style), and extending one page appends exactly one page's worth. Interaction at load: Show-more on each collection, the sort toggle, a tab switch, and one comment post on the loaded issue all complete without timeout at the CI cap (the smoke that catches accidental load-all-then-filter regressions).

The full-page strict a11y sweep: the loaded detail page with EVERY Epic-5 surface populated simultaneously — comments thread + attachments panel + full rail (custom fields, labels, components) + watch control + activity tabs — passes the strict axe config in light AND dark. No per-story sweep renders this combined state; landmark/heading uniqueness and focus order across the stacked sections are exactly the class of bug only the combined page shows.

Acceptance criteria

  • The network census proves every collection read is paged on the loaded issue (zero full-set responses); the DOM budget + append-exactly-one-page asserts hold; the interaction smoke passes at the CI cap.
  • The combined-page strict axe sweep reports zero violations in both themes.
  • The spec runs in the reduced-cap CI lane (the board-at-scale lane precedent) and full-size locally; green in CI.
  • The spec header documents the bounded-read census as the Epic-5 finding-#57 sentinel (future Epic-5-touching PRs inherit it as the regression net).

Context refs

  • 5.6.1 fixture + helpers (the counts the census asserts against)
  • tests/e2e/board-at-scale.spec.ts (3.5) + the 4.7 at-scale specs — the assertion style + CI-lane pattern to mirror
  • The per-story paging contracts (5.1.2 comments, 5.2.2 attachments, 5.5.1/2 activity, 5.4.4 watchers, 5.3.3 rail cap)
  • The strict-a11y sweep configs (2.4.6 lineage); findings #35/#57