responsive-sweep

# Responsive sweep Run only when `pnpm design:route` includes `responsive-sweep`. Use its scope: affected bands for a breakpoint-local change, the full matrix for a new surface or information architecture. - A **breakpoint** is a width where layout changes (`md` 768px, `lg` 1024px). - A **rect** is the measured `getBoundingClientRect()` geometry. - **Chrome** is the frame around content: header, toolbar, tab bar, and panels. Static class reading missed three live defects: `max-lg:pb-*` lost to a later `md:py-*` rule at 768–1023px, three chrome rows overlapped by 79px, and a tab bar intercepted content. Only computed geometry and `elementFromPoint` proved them. ## Width matrix | Viewport | Band | |---|---| | 600×900 | phone/small portrait tablet; below `md` | | 768×1024 | `md` boundary; side panels begin, tab bar remains | | 834×1112 | 11-inch tablet | | 1024×768 | `lg` boundary; vertical navigation begins, tab bar leaves | | 1440×900 | 14-inch laptop; labels progressively compact | | 1920×1080 | FHD | | 2560×1440 | QHD | Use the router's returned bands. A local chrome or layout repair does not independently require the full matrix. If additional breakpoints are affected, update the change facts and use the resulting scope. ## Loop at each width 1. Resize and navigate to a URL reproducing the exact state, such as `?index=expanded` or `?recent=auto`. Set `guides=off` as a query parameter (use `&` when a query already exists); the first-run overlay otherwise cap...