will/swarm-zap
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(state): record gmail pass completion evidence

Browse Source
This commit is contained in:
zap
2026-03-12 20:58:09 +00:00
parent 111dda91b8
commit d06679f967
3 changed files with 87 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
HANDOFF.md
View File

@@ -4,7 +4,7 @@
Immediate baton-pass for the next fresh implementation session.
## Current objective
Advance the Google Workspace action bus beyond create-only proofs now that real approval-routed Gmail draft + Calendar event tests have been re-verified in a fresh session.
Run calendar pass (2/3): extend the action bus beyond create-only calendar support now that Gmail pass 1 is complete.
## Use these state files first
1. `WIP.md` — full standing plan and checkpoints
@@ -32,14 +32,26 @@ Advance the Google Workspace action bus beyond create-only proofs now that real
- verified via `gog calendar get primary <eventId>`
- cleaned via `gog calendar delete primary <eventId> --force`
## Gmail pass 1 completed in this handoff cycle
- Added workflow actions:
- `list_email_drafts`
- `delete_email_draft`
- `send_gmail_draft` (alias: `send_approved_email`)
- Added host bridge executors:
- `email_list_drafts` (`gog gmail drafts list`)
- `email_draft_delete` (`gog gmail drafts delete`)
- `email_draft_send` (`gog gmail drafts send`)
- Added explicit approval metadata in workflow responses (`approval.policy`, `approval.required`, `approval.mutation_level`).
- Updated docs/test payloads/validator to match the expanded Gmail contract.
## Highest-priority next actions
1. Add `list_email_drafts` and `delete_email_draft` actions to the workflow contract and host executor path.
2. Add `list_upcoming_events`, `update_calendar_event`, and `delete_calendar_event` actions.
3. Keep approval policy explicit per action (default-gated for mutating operations).
4. Add one compact operator test playbook for recurring verification (queue → approve → verify → cleanup).
1. Add `list_upcoming_events`, `update_calendar_event`, and `delete_calendar_event` actions.
2. Keep approval policy explicit per action (default-gated for mutating operations).
3. Add one compact operator test playbook for recurring verification (queue → approve → verify → cleanup).
## Success criteria for the next session
- At least one new Gmail action and one new Calendar action implemented and validated end-to-end.
- Calendar action coverage expanded (`list_upcoming_events`, `update_calendar_event`, `delete_calendar_event`) with workflow + bridge + docs alignment.
- Approval policy remains explicit/safe for mutating calendar actions.
- `WIP.md` and memory updated with concrete IDs/evidence.
- Meaningful commit(s) captured.