shots record (web): frames at device pixels through Page.captureScreenshot (clip scale = dpr, long side capped at 1920, 3 requests in flight, midpoint timestamps into the ffmpeg concat); Chromium's screencast stayed at CSS size. Warnings for frames smaller than asked and under 20 frames/s; record-web browser test, pitfall 85

skills/store-pitfalls/SKILL.md

@@ -1038,3 +1038,14 @@ that fails without the fix (see CONTRIBUTING.md).
 - **Guard:** `cli/shots/weights.ts` (templateWeights, fetchFaces, weightIssues), `cli/shots/palette.ts` (bgIssue in
   config validation, bgCss, contrastIssues, coverCrop); report.json `weights` / `contrast`; `tests/shots-look.test.ts`,
   `tests/browser/palette-bg.browser.ts`.
+
+## 85. Web app previews at CSS size (blurry 1080x1920 promo)
+- **Symptom:** `shots record --source web` clips of a 430x932 @2x page came out 430x932, so a 1080x1920 preview was a
+  2.5x upscale. Chromium's `Page.startScreencast` sends frames at the viewport's CSS size whatever the deviceScaleFactor
+  (`maxWidth` / `maxHeight` only shrink); forcing scale 2 through `Emulation.setDeviceMetricsOverride` breaks the layout
+  (innerWidth 980).
+- **Do:** update storebound; the recorder takes `Page.captureScreenshot` frames with `clip.scale` = the frame's dpr
+  (long side capped at 1920), 3 requests in flight. Re-record old web clips. If it still warns that frames are
+  smaller than asked, point `STOREBOUND_CHROME` at a current Chromium or record with `--source folder`.
+- **Guard:** `recordSize` / `captureShortfall` in `cli/shots/devices.ts` (first frame size checked per clip, plus a
+  frames-per-second warning under 20); `tests/video.test.ts`.