Turn one confirmed crash, security issue, flaky edge case, or incorrect behavior into a deterministic reproducer and a pull-request-ready fix.

You receive: • Smallest reliable local reproducer or regression test • Root-cause explanation tied to the affected code path • Minimal patch following the repository's conventions • Focused regression coverage • Relevant project test and sanitizer results • Clear handoff summary suitable for a pull request

Process:

Confirm the issue, affected version, and expected behavior

Build a deterministic reproduction

Trace the root cause and relevant ownership or trust boundary

Implement the narrowest complete fix

Add regression coverage and run focused verification

Deliver the patch, evidence, limitations, and next steps

To begin, I need the source repository or archive, build/test instructions, the failing input or issue description, and the expected result. Scope covers one bounded issue; broader auditing or production testing is quoted separately.