- Playwright MCP: browser automation available via
.playwright-mcp/config, used for manual or AI-driven UI testing on downstream projects
- No unit test runner configured at framework level
- Skills are validated by running each action's
## Testend-to-end against a real environment - Framework correctness validated by running actual skills against a real project (integration)
- Each action declares a
## Test(a command to run, an artifact check, or an observable side-effect) that must pass before the next action runs scripts/build-dist-verification.mddocuments how to verify the build output
Not applicable: the framework has no runtime; all logic is markdown interpreted by an LLM.