complete-partial-pr

To evaluate a pull request against the full integration contract, map related codepaths like parsing, streaming, tools, and metadata to identify missing work beyond the initial patch. This ensures the PR satisfies complete user workflows rather than just fixing one failing test.

Partial PR scope validation in code review is the process of checking whether a patch covers the full behavior expected by users, not just the first visible symptom. It involves mapping adjacent surfaces like sync and async flows to guarantee complete spec compliance.

To complete a partial Pydantic AI patch, apply conservative implementation aligned with project history and specs, then add focused regression tests. This validates that sync and async flows, roundtrip behavior, and adjacent workflow variants function correctly.

Fixing one provider edge case often requires updates to streaming and parsing paths because integration contracts demand consistent behavior across surfaces. You must check historical decisions and map related routes to ensure sync, async, and roundtrip behaviors are fully covered.

You should not use a narrow patch fix during integration testing when adjacent paths like request and response handling, tools, metadata, or docs remain incomplete. If the patch fails to satisfy the full integration contract, conservative implementation and broader regression tests are required.