I am aiming to have ten solid, well-documented pull requests merged into a public Python repository that I will point you to once we start. Each PR must tackle a genuine bug—no cosmetic or dummy changes—so the maintainers see real value and are willing to approve quickly. Scope and expectations • Review open issues or identify hidden edge-case failures, then supply concise, tested fixes. • Keep every change set focused: one bug, one PR. • Follow the repo’s existing style guide, lint rules, and CI workflow so each PR passes automated checks on the first try. • Write or update unit tests where relevant and include clear commit messages plus a brief PR description that references the related issue. • All ten PRs must be merged (not merely opened) within 7 calendar days of project start. Deliverables (must-have) 1. 10 merged GitHub pull requests, each linked back to its resolved bug. 2. Updated test cases or new tests proving the fix. 3. A short final report listing PR URLs, the bug addressed, and any follow-up notes from maintainers. Acceptance criteria • CI green across all supported Python versions in the repo. • No new linting errors; coverage must not decrease. • Maintainers confirm merge—“closed via merge” status visible on every linked issue. If you are comfortable hunting down bugs in Python codebases and can work fast inside Git, branches, and GitHub’s review flow, let’s get started right away.