Email Agent — capability completion tracker (live status vs. spec)

[itomek]

Living status board for every capability defined in the Email Agent Capability & API Spec. One row per spec capability, with its real implementation/test state and the issue that owns the remaining work. Update the status cell as items land — this is the single place to answer "what's done?"

As of now: 15 of 17 numbered capabilities and 3 of 5 personalization features are implemented and testable. Status verified against hub/agents/python/email/ tools + the repo tests/ tree (not just the spec badges, which lag on personalization).

Legend — Status: ✅ implemented + testable · 🟡 partial · ⬜ planned / not started
📸 Verification evidence (live): #1691 (comment)

Legend — Per spec: ✅ built as specified · 🟡 gap vs spec (planned/partial — see remaining work)
Legend — Verified: ✅ real-world verified this pass (harness + Agent UI on Mac, photo on file) · 🟡 partial · ⬜ not yet verified this pass

Capabilities (17)

#	Capability	Status	Verified	Per spec	Owner / remaining work
1	4-way triage (→ 5-bucket in schema 2.0)	✅	✅	✅	#1266 · taxonomy change tracked in #1615 · live Gmail triage via harness (Mac) 2026-06-16 · spec: Validated
2	Per-email summary	✅	✅	✅	#1267 · per-email summary rendered live in harness 2026-06-16 · spec: Validated
3	Draft reply	✅	✅	✅	#1269 · full draft via gaia email CLI (evidence) · spec: Validated
4	Phishing detection	✅	✅	✅	#1271 · ⚠ flagged on spoofed-bank sample (evidence) · spec: Validated
5	Inbox pre-scan	✅	✅	✅	#1265 · whole-inbox scan (evidence) · spec: Wired
6	Full-thread comprehension	✅	✅	✅	#1268 · spec: Wired · exercise 2026-06-17: full-thread summary verified live; multi-mailbox provenance bug
7	Send a reply via agent (confirm + token)	✅	✅	✅	#1264 · live send Gmail+Outlook + 403 token gate (evidence) · spec: Wired
8	Batch archive	✅	✅	✅	#1270 · tool path exercised; no promotional mail present to archive this pass · spec: Wired · exercise 2026-06-17: archive action verified; agent autonomous use hit multi-mailbox bug (triage-timeout was a 2k-mirror artifact) · revalidated 2026-06-18: multi-mailbox archive_message_batch routes by recorded provenance (succeeded 2/0, no "cannot determine") after #1707; ⚠ archive-undo for Outlook still broken → #1738
9	Quarantine + undo	✅	✅	✅	shipped (soft-delete / action log) · spec: Wired · exercise 2026-06-17: trash/untrash verified · revalidated 2026-06-18: undo now re-adds INBOX (#1709 merged)
10	Calendar — detect meeting request	✅	✅	✅	#1272 · agent scanned inbox; no datable invite present this pass · spec: Wired · exercise 2026-06-17: detect_meeting_request true-positive verified
11	Calendar — conflict detection	✅	✅	✅	#1273 · spec: Wired · exercise 2026-06-17: conflict logic verified vs Outlook calendar · revalidated 2026-06-18: conflict detection uses the Outlook calendar (#1708 merged)
12	Calendar — create event	✅	✅	✅	#1274 · Outlook Calendar scope connected; create unblocked once a dated invite exists · spec: Wired · exercise 2026-06-17: create verified via Outlook tool · revalidated 2026-06-18: create_event_from_email routes to the Outlook calendar (#1708 merged)
13	Search past email	🟡	🟡	🟡	#1604 · agent CLI search returned 5 live matches (tool works; still not on REST/MCP) · spec: Planned
14	Task extraction → task list	✅	🟡	🟡	#1605 · email-side producer in PR #1917: REST triage persists action items to a local email_tasks store, linked to message_id + de-duped on re-triage; unified cross-agent store still #1521 · spec: Wired
15	Follow-up tracking	⬜	⬜	🟡	#1606 · spec: Planned
16	Proactive daily briefing	✅	🟡	🟡	#1608 · scheduler + delivery in PR #1918: sidecar daily timer (env-configured, off by default) reuses pre_scan_inbox and serves the latest run on GET /v1/email/briefing; push delivery + calendar/tasks sections still on autonomy #555 · spec: Wired
17	Scheduled send + snooze	✅	⬜	🟡	#1609 · implemented in PR #1919 (email-scoped one-shot scheduler + cancel handles; unit tests cover fire-once/at-after/cancel) · not yet exercised live · seam ready for #1371 dispatch (autonomy #555) · spec: Planned
---	---	---	---	---	---

Personalization & memory (5)

#	Feature	Status	Verified	Owner / remaining work
P1	Behavioral sender prioritization	✅	🟡	#1290 · needs multi-turn; faiss-cpu absent in test venv (vector memory off)
P2	Inbox profiling from memory	✅	🟡	#1289 · same memory caveat
P3	Persistent preferences via memory	✅	🟡	#1288 / #1114 · same memory caveat
P4	Attachment handling	✅	⬜	#1542 · schema 2.2 (PR #1921): read/triage exposes metadata; draft/send accept files, token-bound
P5	Voice / style-matched drafting	⬜	⬜	#1607

Schema 2.0 (proposed · breaking)

Change	Status	Verified	Owner
5-bucket taxonomy + suggested_action	✅	✅	#1615 (merged #1690) · 5 buckets + suggested_action verified live 2026-06-16
context on request	✅	✅	#1541 · draft PR #1696 · context biases summary (verified live)
usage on response	✅	✅	#1540 · draft PR #1696 · tokens+TPS shown per card (verified)
ActionItem.type (text/link)	✅	✅	#1538 · draft PR #1696 · typed link item (evidence)

---

• Spec is the source of truth for behaviour/tiers; this issue is the source of truth for completion state.
• Sequencing & rationale live in the execution-order tracker docs(email): Milestone 40 (v0.22.0) execution-order spec (sequencing + rationale) #1319 (complementary, not duplicate).
• Spec personalization badges (P1–P4 "In flight") are stale — P1–P3 are actually done; worth a one-line spec fix.
• Verified column (added 2026-06-16): real-world verification pass on Mac via the test harness + Agent UI, one capability at a time, each with a captured screenshot. Filled as each is proven.

[itomek]

Email agent — real-world verification (Mac, live Gmail + Outlook)

Last updated 2026-06-18. Verified locally on macOS via Lemonade / Gemma-4-E4B, against the harness synthetic sample inbox (screenshots below) and the live Gmail (tomasz.iniewicz@gmail.com) + Outlook (visits-sesame0v) mailboxes.

Every capability that has shipped code is verified. The four originally-partial "Wired" caps (8 archive, 9 quarantine+undo, 11 conflict, 12 create) are now ✅ after #1707 / #1708 / #1709 merged and were re-verified live on 2026-06-18. Two follow-up bugs remain open → #1738 and #1739 (both Milestone 40).

Capability status

Cap	Status	How verified
1 — 4-way / 5-bucket triage	✅	sample + live Gmail & Outlook (screenshot)
2 — per-email summary	✅	sample + live (screenshot)
3 — draft reply	✅	live gaia email CLI
4 — phishing detection	✅	spoofed-bank sample (screenshot)
5 — inbox pre-scan	✅	sample + live (screenshot)
6 — full-thread comprehension	✅	live (2026-06-17)
7 — send reply (confirm + token)	✅	live Gmail + Outlook; 403 on missing/invalid token
8 — batch archive	✅	live mixed-mailbox archive_message_batch, routes by provenance — #1707
9 — quarantine + undo	✅	live Gmail trash → restore re-adds INBOX — #1709
10 — meeting detection	✅	confirmed and slot-proposal emails — #1709
11 — calendar conflict	✅	live Outlook calendar — #1708
12 — calendar create	✅	live Outlook calendar, planted title read back — #1708
13 — search past email	🟡	live CLI works; not yet on REST/MCP — #1604

Caps 14–17 and personalization P1–P5 are planned/partial — see the issue-body matrix.

Bugs

• Fixed & re-verified live (2026-06-18): bug(email): multi-mailbox tool actions lose message provenance and fail when 2 mailboxes are connected #1707 → fix(email): route multi-mailbox message actions by recorded provenance (#1707) #1735 (multi-mailbox provenance) · bug(email): calendar tools select Google backend even when only Outlook calendar is connected/scoped #1708 → fix(email): select calendar backend by connected+scoped provider, not a Google default (#1708) #1736 (calendar backend selection) · bug(email): meeting-request detector misses slot proposals; quarantine-undo doesn't restore to INBOX #1709 → fix(email): detect slot-proposal meetings; restore INBOX on quarantine-undo (#1709) #1737 (slot-proposal detection + untrash restores INBOX).
• Open → Milestone 40: bug(email): archive-undo fails for Outlook messages — folder-move changes the id (#1707 follow-up) #1738 — archive undo fails for Outlook (folder-move changes the message id) · bug(email): agent's available-mailbox/calendar set derives from connections, not per-agent grants (#1707 open question) #1739 — the agent's available-mailbox/calendar set derives from connections, not the per-agent grant (bug(email): multi-mailbox tool actions lose message provenance and fail when 2 mailboxes are connected #1707's unresolved open question).

Screenshots — synthetic sample inbox (safe to share)

Triage taxonomy (5 buckets + suggested_action):

Per-email summary (typed link item #1538 + usage #1540 visible):

Phishing — spoofed-bank sample flagged ⚠:

Whole-inbox pre-scan:

The images are the synthetic sample inbox — they prove triage/summary/phishing/pre-scan through the real agent, not against real mail. Live-mailbox runs are quoted as text (real-mail content withheld for privacy).

Re-validation evidence — captured tool output (2026-06-18, caps 8/9/11/12)

Driven through the agent's real tools/backends against the live mailboxes + Outlook calendar, in a per-worktree editable venv pinned to main. Planted unguessable facts; reversible mutations cleaned up after.

Environment + #1708 calendar-backend selection — Google holds no calendar scope, only Outlook does, so resolution must pick Outlook:

=== connected mailbox providers ===
['google', 'microsoft']
  google: account=default
     scopes=['https://www.googleapis.com/auth/gmail.modify', 'https://www.googleapis.com/auth/gmail.send']
  microsoft: account=visits-sesame0v@icloud.com
     scopes=['https://graph.microsoft.com/Mail.ReadWrite', 'https://graph.microsoft.com/Mail.Send', 'https://graph.microsoft.com/Calendars.ReadWrite']

=== #1708 PROOF: which calendar backend does resolution pick? ===
calendar backend -> LiveOutlookCalendarBackend

Caps 11 + 12 + slot-proposal detection (#1709) — live Outlook calendar:

CALENDAR BACKEND: LiveOutlookCalendarBackend

===== CAP 12 — create_event_from_email (Outlook) =====
create result: {
  "ok": true,
  "data": {
    "event_id": "AQMkADAwATNiZmYAZS1iMmYzLWU0ZDMtMDACLTAwCgBGAAAD35e8N3ehvEqDtqs9MSWdDwcAy8hzRea5K0ynnFVlYr6uqAAAAgENAAAAy8hzRea5K0ynnFVlYr6uqAAAAAkaPuQAAAA=",
    "summary": "GAIA-REVALIDATE-1691 violet-otter-92 sync"
  }
}
read-back: 1 events in window; planted-token match: 1
   FOUND: GAIA-REVALIDATE-1691 violet-otter-92 sync | id= AQMkADAwATNiZmYAZS

===== CAP 11 — detect_calendar_conflicts (Outlook) =====
seeded conflict event id: AQMkADAwATNiZmYAZS
OVERLAP window 10:30-11:30 -> has_conflict: True | conflicts: ['GAIA-REVALIDATE-1691 conflict-seed amber-lynx-7']
DISJOINT window 16:00-16:30 -> has_conflict: False | conflicts: []

===== #1709 pt1 — detect_meeting_request (slot proposals) =====
  [slot-proposal] is_meeting_request=True confident=True
  [confirmed] is_meeting_request=True confident=True
  [non-meeting] is_meeting_request=False confident=True

===== CLEANUP — delete created test events via Graph =====
  deleted AQMkADAwATNiZmYAZS... -> HTTP 204
  deleted AQMkADAwATNiZmYAZS... -> HTTP 204
created_ids: ['AQMkADAwATNiZmYAZS', 'AQMkADAwATNiZmYAZS']

Cap 9 — quarantine (trash) → undo restores INBOX (#1709):

===== CAP 9 — quarantine(trash)→undo restores INBOX (#1709 pt2) =====
target ''  labels: INBOX=True TRASH=False
after trash:   INBOX=False TRASH=True action_id=452f794b658045708e689d0e5a9258b8
after restore: INBOX=True TRASH=False  (restore ok=True)
>>> CAP 9 PASS = True  (undo re-added INBOX)

Cap 8 — multi-mailbox batch archive routing (#1707) (same run surfaced bug #1738):

=== DEFINITIVE REPRO: undo_archive_batch on Gmail vs Outlook (provenance recorded via list_inbox) ===
google target:    'GAIA M40 P2 live-send test 125902'
microsoft target: 'CRITICAL: Ryzen AI Partner Churn Risk – TCK-2'

archive_message_batch (mixed): succeeded=2 failed=0
undo_archive_batch (t+1.0s): ok=False
  error: CONNECTOR_ERROR: Microsoft Graph GET /me/messages/AQMkADAwATNiZmYAZS1iMmYzLWU0ZDMtMDACLTAwCgBGAAAD35e8N3ehvEqDtqs9MSWdDw
  store: google    undone=True
  store: microsoft undone=False
  google msg INBOX now = True  (Gmail undo)
  microsoft msg in INBOX=False in ARCHIVE=True  (Outlook undo)

>>> Gmail archive-undo works = True
>>> Outlook archive-undo works = False  (BUG if False)
  [cleanup] restored 'CRITICAL: Ryzen AI Partner Churn Ri' to inbox

Unit: 132 passed — test_multimailbox_provenance, test_backend_selection, test_meeting_detection, test_gmail_client, test_summarize_tools; touched files lint-clean.

How this was tested + earlier live evidence (2026-06-16/17)

Three paths: (A) harness "Sample inbox" — 5 synthetic emails through the real agent/LLM (the screenshots); (B) harness live triage — real Gmail + Outlook via forwarded connectors; (C) gaia email agent CLI against the real mailboxes.

Harness fix that unblocked live mail: forwards were tagged builtin:email, but the hub-migrated agent's id is installed:email — corrected, so both mailboxes connect and triage live.

Cap 3 — draft reply (live, Dana Boss sign-off), verbatim agent output:

✅ Final Answer:
  Subject: Re: Launch Sign-Off Approval
  Hi Dana,
  Please consider this my official GO approval for the launch sign-off. We are
  ready to proceed with [Project Name] as planned.
  Best regards, [Your Name]

Cap 13 — search past email (live CLI): gaia email -q "...mentioning Zephyr" → 5 matching real messages with senders/dates/message-ids.

Cap 7 — send reply (live, both providers): draft → confirmation_token → send verified on real Gmail and Outlook; never-auto-send gate returns 403 on a missing/invalid token.

Schema 2.0 (draft PR #1696): ActionItem.type (#1538), usage (#1540), context (#1541) verified on sample + live.