browser-qa

# Browser qa ## Contract | Field | Bound contract | |---|---| | Trigger | The user runs /browser-qa to run a QA verification pass and get report-only results. | | Authority | Write one local QA report under the working tree. No source, VCS, credential, paid, published, deployed, or remote mutation. Reversible by deleting the report. | | Side effect | A QA report only. No fix loop, no file edits, no further checks after the report is returned. | | Done | Report-only verification results are returned: per-check status and findings in one local report file. | ## Inputs - The working tree or change set to verify. Supply a scope (paths or diff range) to narrow the pass; without one, verify the whole tree. - Optional: an ordered list of check commands to run. If omitted, run the project's configured QA checks in order: build, then tests, then lint. ## Procedure 1. Bound scope to the supplied paths or diff range, or the whole tree when none is given. Do not read or change files outside that scope. Done when: the scope boundary is established and enforced. 2. Run each configured QA check in order (build, then tests, then lint) and capture exit status, stdout, and stderr for each. Done when: every check has been run or recorded as non-runnable. 3. Collect every finding into a single list tagged by check name and severity. Done when: all findings are collected with their check and severity tags. 4. Write the findings to one local QA report file under the repository working tree. ...