Enforce stricter checks on certain constants

[0xMushow]

Issue Addressed

Which issue # does this PR address?
None

Proposed Changes

All of these are performing a check, and adding a batch, or creating a new lookup, or a new query, etc..
Hence all of these limits would be off by one.

Example:

// BACKFILL_BATCH_BUFFER_SIZE = 5
  if self.batches.iter().filter(...).count() >= BACKFILL_BATCH_BUFFER_SIZE {
      return None;  // ← REJECT
  }
  // ... later adds batch via Entry::Vacant(entry).insert(...)

Without the > being changed to a >= , we would allow 6. The same idea applies to all changes proposed.

Additional Info

Please provide any additional information. For example, future considerations
or information useful for reviewers.

[cla-assistant]

All committers have signed the CLA.

[jimmygchen]

This is a valid cleanup, however note that changing > to >= reduces the effective runtime limits by 1 (e.g., batch buffers go from 6 to 5, retries from 4 to 3). Impact should be negligible but it is a subtle change in production behavior, not just a cleanup.

[jimmygchen]

@mergify queue

[mergify]

Merge Queue Status

🛑 Queue command has been cancelled

[mergify]

Merge Queue Status

Rule: default

---

• ✅ Entered queue — 2026-02-23 01:29 UTC
• ✅ Checks passed · on draft merge queue: embarking unstable (9452d51) and #8500 together #8883
• ✅ Merged — 2026-02-23 02:02 UTC · at 340b0037be38c902efc80519a4cd4652f7f7cfdd

This pull request spent 33 minutes 12 seconds in the queue, including 30 minutes 5 seconds running CI.

Required conditions to merge

• check-success=local-testnet-success
• check-success=test-suite-success