Track parity for browser-commander preview-regeneration pattern

[konard]

Context

Cross-link to link-foundation/js-ai-driven-development-pipeline-template#62 which is the primary host for the pattern.

konard/vk-bot-desktop recently shipped PR #52 (closes issue #51) which adds a release-time pipeline that auto-regenerates every preview image (README + Pages site + og:image) using browser-commander + Playwright, then commits the drift back to main.

While auditing CI parity I checked the four link-foundation AI-driven-development-pipeline-template repos and none ship browser automation or screenshot tooling. Full per-template survey: docs/case-studies/issue-51/data/templates/survey.md.

Relevance to this template

There is no example-app surface here today; this is a tracking issue so the pattern is registered if/when one is added. A Python equivalent could use playwright-python with the same locale × theme matrix; browser-commander itself is JS-only so the Python port would call Playwright directly.

Suggested action

1. Track this issue as a placeholder.
2. When an example-app surface lands here, port the recipe to playwright-python.

Related

• We need to make sure we use browser-commander library to actually update all preview images of the application konard/vk-bot-desktop#51
• feat(preview): auto-regenerate preview images on release via browser-commander konard/vk-bot-desktop#52
• Add release-time hook that regenerates example-app screenshots with browser-commander js-ai-driven-development-pipeline-template#62 — primary upstream issue