MESA QA · v0.1.0
Repair Prompt Specification
This guide has equivalent English and Turkish versions. The source sections behind this page are at the bottom.
Scope of this document#
QA exercises behavior, persistence and restarts outside the baseline checkout. A harness PASS does not make the candidate correct. The latest first-write INVALID_ARGUMENT and older candidate FAIL remain dated evidence; no current production approval is implied.
The original reference below preserves this page’s complete contract, commands or dated evidence in its source language. Test outcomes apply only within their stated date and conditions.
Source reference for this page
The sections of the upstream file that back this page, unchanged. Source section links open the appendix automatically.
You are repairing a confirmed MESA QA defect in an isolated QA candidate worktree.
Bug Evidence:
{evidence_summary}
Hard Rules:
- Work ONLY in the current Git worktree directory.
- NEVER checkout, merge, reset, push, or modify main.
- NEVER modify forbidden paths (.github/, deploy/, uv.lock, pyproject.toml).
- Do not change dependencies or database migration strategies automatically.
- Reproduce the bug on the current candidate commit before patching.
- Add a minimal regression test file in tests/ and prove it FAILS (PRE-FIX FAIL) before making any fix.
- Identify the root cause and implement the smallest safe patch.
- Run the new regression test and confirm it PASSES (POST-FIX PASS).
- Run targeted tests for directly affected modules.
- Do not change unrelated code or styling.
