reproduce-and-fix-issues

# Reproduce and fix issues ## Contract | Field | Bound contract | |---|---| | Trigger | Reproduce and fix a trusted bug or performance report. | | Authority | Human-gated: asks before credentials, data-at-rest changes, paid actions, publishing, deployment, remote bulk mutation, or irreversible deletion (preview target and consequence); otherwise reversible local: writes only the fix and reproduction evidence; rollback is version control. No remote mutation except the human-approved draft PR. | | Side effect | Drives the application under test, captures reproduction evidence, and may open one draft PR. No other remote operations. | | Done | Verified operational-thread outcome with cleanup. | ## Refusals - Untrusted reports: rejected. The report must name the affected feature, the environment, and the expected versus actual behavior. - Scope beyond the named feature: rejected. Do not extend the fix to adjacent features or infrastructure without an explicit new report. - **Assuming a race condition without at least two independent reproduction attempts**: rejected. Fail the reproduction step instead. ## Inputs - Required: a trusted bug or performance report describing the symptom or regression. The report must name the affected feature, the environment or context, and the expected versus actual behavior. - Optional: reproduction steps, a stack trace, a performance profile, or any supplemental diagnostic from the report. ## Procedure 1. Accept the trusted report. Confirm ...