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

docs(context): require fresh implementation sessions

Browse Source
This commit is contained in:
zap
2026-03-12 19:43:17 +00:00
parent 06fa5821a5
commit 0fe5cd52d9
5 changed files with 125 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
memory/2026-03-12.md
View File

@@ -105,3 +105,20 @@
- Created top-level state file `WIP.md` to track the current Google Workspace + n8n integration plan, status, completed work, and next steps.
- Updated `memory/tasks.json` so the overlapping Google Workspace / calendar / email tasks moved from `open` to `in-progress` and now point at the current WIP file.
- Will explicitly noted a durable capability reminder: zap also has access to Will's own Gitea repo on the LAN and can use it when repo-backed tracking/sync is useful.
- Real end-to-end Google execution via n8n approval + gog bridge was completed (non-dry-run) for both target flows:
- Gmail draft flow (`send_email_draft`): queued, approved through `resolve-approval-with-gog.py`, verified with `gog gmail drafts get`, and deleted with `gog gmail drafts delete --force`.
- approval id: `approval-mmnvjcak-qcuhbzqd`
- draft id: `r348335896293726096`
- subject: `[zap n8n e2e] Gmail draft test 20260312T194153Z`
- Calendar event flow (`create_calendar_event`): queued, approved through the same bridge, verified with `gog calendar get primary <eventId>`, and deleted with `gog calendar delete primary <eventId> --force`.
- approval id: `approval-mmnvjyo5-uezhcw84`
- event id: `il3ojkfnsnq3uhlepvrmaklpq4`
- title: `[zap n8n e2e] Calendar test 20260312T194222Z`
- Important command-shape notes captured from the live run:
- `gog calendar get` and `gog calendar delete` expect `<calendarId> <eventId>` argument order.
- `gog gmail drafts delete` required `--force` for non-interactive cleanup.
- Will also set a new operating preference for context use: for non-trivial implementation work, prepare file-based state/handoff (`WIP.md`, `HANDOFF.md` as needed), then start a fresh isolated implementation session/run instead of continuing inside a bloated main-session context window.
- Implemented that preference locally by:
- adding a `Fresh-session implementation discipline` section to `AGENTS.md`
- creating `HANDOFF.md` as the immediate baton-pass file for the next clean implementation session
- updating `WIP.md` with a `Next-session handoff` section