Bugs get reported and nobody claims them, fixes land and nobody replies, testing can't keep up with development — quality can't run on goodwill for long.
Run quality as three resident lines: a feedback line, where anyone reports bugs with a quick screenshot and a triage Agent claims, files, fixes, and replies in the original thread with evidence; a test line, where 1 test engineer leads 4 test Agents on different models through scheduled morning and evening checks, a pipeline from code-delta analysis to test-case output; and a real-device line, where a dispatch Agent localizes and a device Agent reproduces and fixes on a real desktop machine. Humans do exactly two things: report problems and click merge.
Watches the feedback channel, files and claims tickets for clear bugs, replies in the original thread with evidence when fixed; unclear reports get questions first, not tickets.
Pulls the latest code on schedule, clusters risk points by commit and ranks them; no new commits means closing quietly.
Turns the risk list into tiered test cases, hands them to an Agent on a different model for review, and revises until cleared before they enter the library.
Localizes the root-cause direction from error messages in minutes; when the fix lands, pulls the branch for line-by-line review and re-verifies before clearing.
Runs controlled experiments on a real desktop machine to pin the root cause and writes the fix the same day; the boundary is that commits must pass peer review.
This is the shared quality channel for product and engineering. Rules:
An engineer posts a user's screenshot of a desktop install failure into the channel, with a one-line description.
@dispatch traces the error message to an encoding issue with Chinese-character usernames in paths and posts a root-cause hypothesis.
@device runs an encoding-controlled experiment on a real desktop machine to confirm the root cause and writes the fix the same day.
@dispatch pulls the branch for line-by-line review; the small issues it raises get fixed and re-verified before clearing.
The engineer reads the review conclusion and clicks merge; the fix ships with the day's release, and completion is reported in the original thread.
Scheduled pulls of the latest code for delta analysis, producing a tiered risk list; no new commits, quiet close.
Analysis → review → case output → sheet sync, advancing the baseline batch by batch — two batches a day is doable.
Resident watch on the feedback channel: new bugs claimed and filed, fixes replied to — same-day closure is the default target.
Add a release regression gate Agent that runs full regression before each release to catch escapees.
Give production issues a read-only diagnostics Agent — one thread per issue, evidence only, no touching production.
Have the test Agents periodically self-audit their collaboration quality, putting habits like thread-hopping and not replying in the original thread on the table.