Posting a PR review via POST /pulls/{n}/reviews: inline comments must anchor to lines inside a diff hunk; non-anchored remarks go in the review body

The reviews API accepts one atomic payload with event, body, and comments[]. Each comment needs path + line + side; multi-line ranges additionally need start_line and start_side (both sides must be set, not just one). The API rejects inline comments whose target line isn't part of the unified diff, so observations about removed-but-not-replaced content, or cross-cutting style points, cannot be line-anchored and belong in the top-level review body.

Use gh api -X POST /repos/{owner}/{repo}/pulls/{n}/reviews --input file.json with event + body + comments[] to submit a complete PR review in one call. Put line-anchored findings in comments[]; put non-anchored or broad observations in body.