The GitHub Actions job "prek" on airflow-steward.git/feat-gmail-thread-minimal-default has succeeded. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 2ec450f7f16a2bf51c86b0f5340f8163db5e94b9 / Jarek Potiuk <[email protected]> docs(gmail): default get_thread to MINIMAL; escalate to FULL_CONTENT only on body-parse Profiling a 12-tracker bulk sync surfaced that Gmail get_thread calls were responsible for ~170 KB of in-context spillover (top single spillover file was 440 KB) — a FULL_CONTENT call on a long reporter conversation routinely lands 60-100K tokens. Most call sites only needed the chronologically-last message ID for anchoring, the SENT/ DRAFT label state, or the thread-exists check — all of which MINIMAL satisfies at ~5K tokens. Changes: 1. tools/gmail/operations.md — flip the default example from FULL_CONTENT to MINIMAL. Document a clear escalation rule: default to MINIMAL; escalate to FULL_CONTENT only when the call site actually processes the message body (Step 3 classification in security-issue-import, Step 1e reviewer-comment parsing in security-issue-sync, draft-composition that quotes the reporter's prior message, credit-form extraction). Also fix a longstanding terminology error: the doc said 'METADATA' but the MCP enum is 'MINIMAL'. 2. security-issue-sync Step 1e — make the FULL_CONTENT requirement explicit (reviewer comment bodies ARE the actionable signal). Reinforce the contrast with the rest of the skill, which defaults to MINIMAL. The privacy-LLM contract block was updated accordingly — the redact-after-fetch protocol applies to FULL_CONTENT calls; MINIMAL calls are exempt (they carry headers only, no free-form body content). Estimated savings: ~80% of Gmail-related tokens on typical bulk runs (60-100K → ~5K per call). Compounds on every bulk-sync invocation. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> Report URL: https://github.com/apache/airflow-steward/actions/runs/26709822549 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
