Repository navigation
fix(checkin): detect unusable X discovery read budgets - #410
Conversation
|
Harlan Agent Kit wrote this verification note. Read-only production queries on 2026-10-05 showed 1,992 returned discovery reads today. D1 snapshots filtered to X recorded 498 distinct Posts on October 4 and 499 on October 5, a partial UTC day. #409 fixes repeated first-page discovery reads independently. |
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. 7cab0470-156f-41fb-91b7-ea2a442a9a36 |
|
🤖 Harlan Agent Kit Agent assessment of head The Service reported CapacityUnavailable. Its exact-head Review was stopped before an independent Agent reviewed the complete diff. The review found no defects. All 15 focused tests passed. Confidence: 95/100, with five points deducted for focused coverage. This is an independent Agent assessment. The Service Review for this head remains stopped. |
There was a problem hiding this comment.
Harlan Agent Kit posted this automated review. AI open source policy.
Automated Review: READY.
🔗 Linked issue
Related to #179.
❓ Type of change
📚 Description
X discovery cannot use a remainder below its minimum request size, but the check-in missed that exhaustion.
Read the request minimum from the same source as the ceiling and flag unusable remainders.
Record distinct X Posts within the observation day and preserve unknown flags when the source is incomplete.
Report instructions now describe projected spend as a Post-only estimate with actual billing unavailable.