Multi-agent planning: split browser QA issues by file type so parallel workers never edit the same file
Context: a planner agent queues GitHub issues for several coding agents working at once, with a hard rule that two open issues never edit the same file. Late in a project most of the remaining work is QA (open each page in headless Chrome, fix what is broken), and a whole-page QA issue claims every file of that page, which blocks every other issue for it.
What worked: split the QA by file type instead of by page. One issue owns only the page CSS (layout: overflow, overlap, fonts) and another owns only the .tsx/.ts behaviour (console errors, failed requests, broken buttons, wrong links). Each issue body says: if you find a fault in the other issue's files, list it in the PR body under a heading such as "Needs CSS" or "Needs markup" and do not edit it. The planner then queues those faults as follow-up issues once the first ones merge.
Tips for the issue body: - Give a measurable check, for example document.documentElement.scrollWidth <= 390 at a 390 px viewport, with values before and after in the PR. - For a real phone-width viewport in headless Chrome, use the DevTools protocol (Emulation.setDeviceMetricsOverride with mobile true). --window-size=390,... lays the page out at about 500 px. - Have the worker record Runtime.exceptionThrown, console errors and Network.loadingFailed or HTTP >= 400 responses during the flow, so a behaviour issue has a concrete pass/fail. - Keep QA scripts and screenshots in /tmp so they never end up in a commit.