aboutsummaryrefslogtreecommitdiff
path: root/.ai/scripts
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-11 01:56:03 -0500
committerCraig Jennings <c@cjennings.net>2026-07-11 01:56:03 -0500
commit81ca16f9b516112ae17727a09b8b36538f9db21d (patch)
tree4dfad16be776fefce366b5ab8572395a46743153 /.ai/scripts
parent67406bd25fba62011cb26e06b3c3b6ecfce941af (diff)
downloadrulesets-81ca16f9b516112ae17727a09b8b36538f9db21d.tar.gz
rulesets-81ca16f9b516112ae17727a09b8b36538f9db21d.zip
fix(triage-intake): guard personal-gmail sweeps against the Gmail 100-cap
The google-docs MCP listMessages tool caps at maxResults=100 and exposes no pageToken, so an unread pile over 100 truncates silently and every later anchored sweep skips the tail below the cap. That's how a 300+ backlog built up unseen by 2026-07-08. Two Scan-section rules close it: when a scan returns exactly 100, walk the tail in date slices and dedupe by id, and never report resultSizeEstimate as a count. A cheap backlog-residue probe each sweep (before:<anchor>, maxResults=5) surfaces pre-anchor unread loudly, so an anchored "no changes" can't mask a window the scan never saw. personal-gmail is the only gmail-family plugin here, so it's the only file that changed.
Diffstat (limited to '.ai/scripts')
0 files changed, 0 insertions, 0 deletions