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

docs(state): record calendar pass completion evidence

Browse Source
This commit is contained in:
zap
2026-03-12 21:11:28 +00:00
parent 4d89f02664
commit 2a46de2287
3 changed files with 89 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
HANDOFF.md
View File

@@ -4,7 +4,7 @@
Immediate baton-pass for the next fresh implementation session.
## Current objective
Run calendar pass (2/3): extend the action bus beyond create-only calendar support now that Gmail pass 1 is complete.
Run operator/polish pass (3/3): tighten operator docs, approval policy clarity, recurring verification flow, and low-noise execution reporting now that Gmail + Calendar passes are complete.
## Use these state files first
1. `WIP.md` — full standing plan and checkpoints
@@ -44,15 +44,30 @@ Run calendar pass (2/3): extend the action bus beyond create-only calendar suppo
- 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.
## Calendar pass 2 completed in this handoff cycle
- Added workflow actions:
- `list_upcoming_events`
- `update_calendar_event`
- `delete_calendar_event`
- Added host bridge executors:
- `calendar_list_events` (`gog calendar events`)
- `calendar_event_update` (`gog calendar update`)
- `calendar_event_delete` (`gog calendar delete`)
- Preserved explicit approval policy:
- read-only calendar listing stays `low`
- mutating calendar update/delete stay `high`
- Added docs/test payloads/validator coverage for the expanded calendar contract.
## Highest-priority next actions
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).
1. Add a compact operator command/reference section for common approval flows.
2. Add one or two canned recurring verification flows (queue → approve → verify → cleanup).
3. Decide/document approval defaults clearly per action family.
4. Improve low-noise execution/result reporting in approval history.
## Success criteria for the next session
- 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.
- Operator/polish pass completed with docs/playbook/history-reporting improvements.
- Approval defaults are explicit and easy to skim.
- `WIP.md` and memory updated with concrete evidence.
- Meaningful commit(s) captured.
## Relevant files