arcodange-email-ingest V8.1: filter calendar invites + newsletter senders #10
Reference in New Issue
Block a user
Delete Branch "claude/arcodange-email-ingest-v81"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
V8.1 filters out the noise that V8.0's
--candidates-onlylet through: calendar invites (Google CalendarInvitation:/Updated invitation:etc. — all carry an.icsattachment so the hasAttachment heuristic over-matches) and newsletter blast traffic (senderupdates.<domain>,news@,newsletter@).Effect on baseline
--all-folders --candidates-onlytotalstaying-ahead.ainewsletters--mark-ingesteddeferred to V8.2Originally V8.1 was meant to ship this too. The Zoho flag-set endpoint (
PUT /api/accounts/{aid}/updatemessage) requires the OAuth scopeZohoMail.messages.UPDATE, which the current refresh_token doesn't have (READ-only scopes). The fix is for the user to regenerate the refresh_token via the Zoho Self-Client with the extra scope, then a one-line--mark-ingestedflag onemail-inspect.sh+ aflagid == flag_infofilter inis_candidate()becomes V8.2. Documented in SKILL.md.Test plan
bin/arcodange email list --candidates-only→ still shows 3 candidates in/Inbox/booksbin/arcodange email list --all-folders --candidates-only --limit 50→ ~12 entries, noInvitation:subjects, noupdates.staying-ahead.aisendersbin/arcodange email inspect 1775141901205014300→ still works unchangedgit diff --cached | grep -F <ZOHO_REFRESH_TOKEN>empty (verified pre-commit)