capturing-product-medialisted

# Capturing Product Media DorkOS product media is a **general system**: one shot registry (`apps/e2e/capture/shots.ts`) feeding the marketing site, docs, and changelogs, from **real** UI rendering **seeded** demo data — never mockups, never doctored screenshots. Automated captures can be beaten by human overrides, and any published set can be frozen into a versioned archive. This skill is the map: the registry, the phases, overrides, archives, docs embeds, the honesty rules, and how to add a shot. ## When To Use - The UI changed and a screenshot or loop on the site or docs now looks stale or wrong. - A new feature needs a "money shot" (hero still or animated loop) on `/features`, or a docs page needs an embedded `<ProductShot>`. - A person wants to override an automated capture with hand-captured media. - A release calls for a fresh capture or a frozen archive of the shots its notes embed. - A media-guard test (`features.test.ts` or `shots.test.ts`) fails because an asset or registry entry is missing. ## Commands ```bash pnpm --filter @dorkos/e2e capture # record + process (the full refresh) pnpm --filter @dorkos/e2e capture:record # boot + drive + save raws to the library pnpm --filter @dorkos/e2e capture:record --shards N # same, but record on N parallel isolated stacks pnpm --filter @dorkos/e2e capture:process [run-id] # edit raws + apply overrides → product/ (default: latest) pnpm --filter @dorkos/e2e capture:archive <label> # freeze the c