potiuk opened a new pull request, #409:
URL: https://github.com/apache/airflow-steward/pull/409
## Summary
Profiling a 12-tracker bulk sync surfaced that Gmail \`get_thread\` calls
were responsible for ~170 KB of in-context spillover (single largest: 440 KB).
Most call sites only needed the chronologically-last message ID, label state,
or thread-exists check — all of which \`MINIMAL\` satisfies at ~5K tokens vs
~60-100K for \`FULL_CONTENT\` on a typical reporter conversation.
## Changes
### \`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:
- \`security-issue-import\` Step 3 (classification by body scanning)
- \`security-issue-sync\` Step 1e (reviewer-comment body parsing)
- Draft-composition steps that quote the reporter's prior message
- Credit-form extraction from inbound report bodies
- **Fix a longstanding terminology error** — the doc said \`METADATA\` but
the MCP enum is \`MINIMAL\`.
- **Privacy-LLM contract scoping** — \`MINIMAL\` calls are exempt from the
redact-after-fetch protocol (headers only, no free-form body content).
### \`security-issue-sync\` Step 1e
Make the \`FULL_CONTENT\` requirement explicit — reviewer comment bodies ARE
the actionable signal here. Reinforce the contrast with the rest of the skill,
which defaults to \`MINIMAL\`.
## Estimated savings
~80% of Gmail-related tokens on typical bulk runs (60-100K → ~5K per call).
Compounds on every bulk-sync invocation.
## Test plan
- [x] Doc-only change; no Python code touched; \`skill-and-tool-validate\`
passes
- [ ] Next bulk sync run on \`airflow-s/airflow-s\` confirms typical
\`get_thread\` calls land at \`MINIMAL\` size
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
