Build mode
In Build mode (composer → Options → Build mode), X6 doesn’t decide for itself when code is finished. The run has to pass a Definition of Done first.
The gate
Section titled “The gate”- Find the project. The gate finds each project the run wrote to, such as the nearest folder with a
package.jsonorpyproject.toml. - Run the checks inside the workspace sandbox: install missing dependencies, type check, lint, tests, and build, wherever the project has them.
- Check the page in a browser.
verify_webloads the page in headless Chrome. It needs zero console errors and zero failed requests, and it saves desktop and phone screenshots.
Missing tests fail the gate. An npm project needs a real test script, a Python project needs test_*.py files,
and a static page with scripts needs scripted steps that exercise its main feature.
Repairs and review
Section titled “Repairs and review”- Repairs: a failing gate goes back to X6 with the exact output, for up to five repair cycles. If the same failure comes back three times in a row, the run stops early. A run that still fails ends as Incomplete, with a report that says so.
- Review: after the first passing gate, a second model reviews the diff against the request. High and medium findings get one fix round, then the gate runs again. Low findings go to the project’s backlog.
What verify_web checks
Section titled “What verify_web checks”| Area | Checks |
|---|---|
| Errors | Console errors, uncaught exceptions, failed requests (4xx/5xx, network) |
| Content | Broken images, links, and anchors; title and visible text |
| Layout | Missing viewport tag, overflow at phone width |
| Behavior | Scripted steps: click, fill, press, wait, expect, expect_text |