Capture and review workflow

Reproduce the evidence

• Run audit-teachkit.mjs against the sibling repositories and save the baseline.
• Run measure-teachkit-contrast.mjs for effective app and marketing color pairings.
• Run prepare-teachkit-system.mjs to build the ignored Vite fixture and disposable marketing snapshot.
• Start those previews with a minimal environment; do not inherit service credentials.
• Run capture-teachkit-system.mjs. CAPTURE_ONLY can target families or resume remaining records.
• Inspect every image on labeled review sheets and inspect questionable crops at full resolution. Correct clipping, empty space, missing fonts, or incomplete controls before accepting.
• Register the reviewed hashes, install the capture manifest, and generate the authored system JSON.
• Publish the selected assets through the existing site-assets workflow, then verify dimensions, references, routes, sitemap, viewer behavior, and source immutability.

Isolation

The app imports the real source components with local session/router/API adapters. Browser requests are restricted to local GETs and an intercepted offline media poster. Marketing is copied without .env files or API handlers; its catalog is replaced with a fictional class and analytics mounts are removed. No owner database export or customer records are used.

Framing and resolution

Complete controls receive surrounding padding; open menus include their trigger and panel. Applied screens use meaningful feature bounds rather than full-page height. Desktop specimens use higher density for small controls; all captures are at least 2× and lossless WebP. Fonts must be ready, images decoded, and the intended state visible.

What fixtures do not prove

Local success, delay, and conflict responses prove presentation branches. They do not verify live provider credentials, email delivery, checkout, server permissions, or concurrency correctness.