docs(wip): track google workspace and n8n plan

memory/2026-03-12.md

@@ -99,3 +99,9 @@
   - updated `resolve-approval-with-gog.py` to auto-load that file when present
   - verified non-interactive headless Gmail access works using the stored env (successful `gog gmail search ... --json --no-input`)
   - verified the bridge itself auto-loads the env file by resolving a fresh `email_draft` approval item in `--dry-run` mode and attaching execution metadata successfully without manually exporting `GOG_ACCOUNT` / `GOG_KEYRING_PASSWORD`
+- Real direct Google sanity checks succeeded after that:
+  - created a Gmail draft to `william.valentin.info@gmail.com` with subject `Test draft from zap`
+  - deleted the same draft successfully and verified removal via follow-up `404 notFound`
+- 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.

memory/tasks.json

@@ -59,11 +59,12 @@
     "title": "Add calendar access/backend for proactive scheduling help",
     "owner": "zap",
     "priority": "medium",
-    "status": "open",
+    "status": "in-progress",
     "details": "Set up or connect a calendar backend so zap can provide stronger calendar-aware assistance, daily briefs, and schedule checks.",
     "notes": [
       "Added from LAN-services gap review on 2026-03-11.",
-      "Biggest functional gap identified at the time."
+      "Biggest functional gap identified at the time.",
+      "Progress 2026-03-12: access/auth now exists and the remaining work is productionizing n8n-routed execution plus verification."
     ]
   },
   {
@@ -72,10 +73,11 @@
     "title": "Add email/inbox access for triage and briefing",
     "owner": "zap",
     "priority": "medium",
-    "status": "open",
+    "status": "in-progress",
     "details": "Set up access to a mail/inbox workflow so zap can help with triage, summaries, and urgent-message detection.",
     "notes": [
-      "Added from LAN-services gap review on 2026-03-11."
+      "Added from LAN-services gap review on 2026-03-11.",
+      "Progress 2026-03-12: access/auth now exists and the remaining work is productionizing n8n-routed execution plus verification."
     ]
   },
   {
@@ -121,11 +123,15 @@
     "title": "Add Google Workspace access (Calendar/Drive/Docs/Gmail as appropriate)",
     "owner": "zap",
     "priority": "medium",
-    "status": "open",
+    "status": "in-progress",
     "details": "Connect Google Workspace services where useful so zap can work with calendar, docs, drive, and/or gmail more directly.",
     "notes": [
       "Added from tool wishlist on 2026-03-11.",
-      "Some overlap with calendar/email tasks; this is the broader suite-level follow-up."
+      "Some overlap with calendar/email tasks; this is the broader suite-level follow-up.",
+      "Progress 2026-03-12: gog auth completed for Gmail/Calendar/Drive/Contacts/Docs/Sheets.",
+      "Progress 2026-03-12: live n8n action bus now supports approval-gated Google flows via host-side gog bridge.",
+      "Next proof step: run real n8n-routed Gmail draft and Calendar event tests (not just dry-run).",
+      "State file: WIP.md tracks the current full plan and checkpoints."
     ]
   },
   {