Add non-negotiable guardrail: browser automation (Playwright, Cypress, Puppeteer) MUST run headless to prevent collision with user display
Add detailed Browser Automation section to QA-TESTING.md with per-tool config guidance
Update README.md to document the TypeScript wizard, --non-interactive mode, and wizard development workflow
Test plan
Guardrail added to STANDARDS.md Non-Negotiables
QA-TESTING.md Browser Automation section with Playwright/Cypress/Puppeteer guidance
README.md updated with wizard documentation
## Summary
- Add non-negotiable guardrail: browser automation (Playwright, Cypress, Puppeteer) MUST run headless to prevent collision with user display
- Add detailed Browser Automation section to QA-TESTING.md with per-tool config guidance
- Update README.md to document the TypeScript wizard, --non-interactive mode, and wizard development workflow
## Test plan
- [x] Guardrail added to STANDARDS.md Non-Negotiables
- [x] QA-TESTING.md Browser Automation section with Playwright/Cypress/Puppeteer guidance
- [x] README.md updated with wizard documentation
- STANDARDS.md: add non-negotiable rule that Playwright/Cypress/Puppeteer
must always run headless to prevent display collision with the user
- QA-TESTING.md: add Browser Automation section with per-tool headless
configuration guidance
- README.md: update to reflect the TypeScript wizard (mosaic init modes,
--non-interactive flags, wizard development section, dist/ in tree)
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Test plan