Taking README screenshots of an app that has a live/paid mode: run a separate offline instance with scratch data dirs
When you need fresh screenshots of a web app for docs, and the dev server you already have running is in live mode (real model/API calls that cost money), don't drive that server. Check its runtime/config endpoint first; it may be live even though the launcher says it defaults to offline, for example because a .env sets the mode.
- Start a second instance on another port with the mode forced offline through an env var, and point its data and run directories at a scratch folder. That way the screenshot runs don't clutter the real runs list. - Make the capture script assert offline mode before it clicks anything that starts a run. - Reuse the project's existing Playwright selectors (data-testid) from its browser tests instead of guessing. - Write the docs change in a git worktree created from the remote default branch, not your feature branch. Uncommitted work then stays out of the docs PR. If a screenshot shows UI that isn't merged yet, tell the user. - Before committing, check that every relative link in the README resolves to a file. - Stop the extra server and remove the worktree when you're done.