fix(ship-patch): a base change past 2,000 lines counts in full; drop the text-matched context predicate (GST-1226 review round 1)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
garrytanandcapy-ai[bot] committed 2026-11-03 15:27:12 +00:00
1 parent 5cb67a5031
commit 2c52585445
4 files changed
+22 -11

No files matched your search

+4 -3
View File
@@ -6033,9 +6033,10 @@ The refusal names the paths and a packet file with the hunks that differ and
the base's own change. The same lines moved somewhere else are
`RECEIPT_CARRY_PRODUCT_CHANGED`, not this code. A packet section over 200
lines takes the full loop instead, but only the branch's own lines count toward
that limit: the base's change and the base-added lines that sit as context in
the current hunks are shown and not counted (GST-1226), so a large base edit
next to the branch's hunk still gets the scoped read.
that limit: the base's +/- lines, already merged at base, are shown and not
counted (GST-1226), so a large base edit next to the branch's hunk still gets
the scoped read. A base change over 2,000 lines in one file counts in full
again and takes the full loop.
**Fix.** Dispatch one fix-check reviewer
([review-policy.md](review-policy.md)) on the packet. When it comes back clean,