From b2aeaf6caea2c2ba7d27012e5f4f3999ff7c81e0 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sat, 11 Jul 2026 02:14:11 -0500 Subject: chore: file processed inbox handoffs and add two backlog tasks --- ...26-07-08-1124-from-work-proposal-triage-intake-personal-gmail.org | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 inbox/PROCESSED-2026-07-08-1124-from-work-proposal-triage-intake-personal-gmail.org (limited to 'inbox/PROCESSED-2026-07-08-1124-from-work-proposal-triage-intake-personal-gmail.org') diff --git a/inbox/PROCESSED-2026-07-08-1124-from-work-proposal-triage-intake-personal-gmail.org b/inbox/PROCESSED-2026-07-08-1124-from-work-proposal-triage-intake-personal-gmail.org new file mode 100644 index 0000000..6fb315b --- /dev/null +++ b/inbox/PROCESSED-2026-07-08-1124-from-work-proposal-triage-intake-personal-gmail.org @@ -0,0 +1,5 @@ +#+TITLE: Proposal: triage-intake.personal-gmail.org edit (copy sent a +#+SOURCE: from work +#+DATE: 2026-07-08 11:24:19 -0500 + +Proposal: triage-intake.personal-gmail.org edit (copy sent alongside this note). Two additions to the Scan section, both from a 2026-07-08 work-session investigation: (1) a warning that the Gmail MCP listMessages tool caps at maxResults=100 and exposes no pageToken parameter, so >100 unread piles silently truncate — with the date-slice walk (before:, dedupe by id) as the recipe, and a note that resultSizeEstimate is unreliable (stuck at 201 while the real union exceeded 300); (2) a mandatory cheap backlog-residue probe each sweep (q="is:unread in:inbox before:" maxResults=5) that loudly surfaces any pre-anchor unread instead of letting anchored sweeps claim 'no changes' over a window they never saw. Root cause this fixes: ~300 unread accumulated invisibly Jun 4 - Jul 4 because anchored scans never look behind the anchor and the 7/4 catch-up hit the 100 cap. Companion: the work project's project-owned triage-intake.deepsat-gmail.org got the same two additions directly (work tool names); no other plugins in the gmail family. The engine file needs no change. -- cgit v1.2.3