Fixing a Patrol issue

A checklist for turning a Patrol bug report into a verified, review-ready PR. This skill is orchestration + repo-specific knowledge. For canonical rules that may change, read CONTRIBUTING.md — do not duplicate it from memory.

Work through the phases in order. Don't skip reproduction: a fix you can't reproduce failing first is a fix you can't prove works.

1. Understand the issue

1. Read the issue (gh issue view <n> --repo leancodepl/patrol, including comments). Extract: exact command/API, config used, versions, and the expected vs actual behaviour.
2. Don't change the Flutter/Dart SDK version to reproduce unless the issue is specifically about a version. Reproduce on the versions the reporter used.
3. Map the bug to the right package under packages/ before touching code: