fix

Use a fix step that takes the diagnosed root cause, writes a minimal code change, adds a failing regression test first, then validates with the package test suite, typecheck, and lint. Stage the changes with git add but let an orchestrator handle the commit and PR.

Abandon when the reproduce test does not fail before the change, when the fix introduces unresolvable regressions, when it requires breaking-change design decisions, or when lint and typecheck errors cannot be resolved cleanly. Report fixed: false with the specific reason.

No. This workflow prohibits git commit, push, tag, and any GitHub writes. The fix only stages files with git add; a separate orchestrator creates the branch, commit, pull request, and triage comment to keep state synchronized.

For browser-only bugs like admin UI interactions, no automated browser test is written. The fix is verified through agent-browser instead, and the manual verification steps are documented so a maintainer can add a durable test when landing the change.

Write a vitest test targeting the testable surface such as a handler, query, or API route, and confirm it fails before applying the fix. After the fix, the test must pass along with the full package test suite without weakening the test.