docs: close Drive/Docs/Sheets evaluation and complete Google Workspace tasks

This commit is contained in:
zap
2026-03-12 22:42:55 +00:00
parent e6b9844097
commit 6cfb1da179
3 changed files with 87 additions and 76 deletions

View File

@@ -249,3 +249,19 @@
- bridge helper proof: `gmail.drafts.create` sample result produced `draft_id = r-proof-draft-123`
- bridge helper proof: `calendar.create` sample result produced `event_id = evt-proof-456`, `calendar = primary`
- workflow asset string checks confirmed presence of `pending_compact`, `history_compact`, `summary_line`, `result_refs`, `default_mode`, and `approval.family`
## Drive/Docs/Sheets evaluation (main session)
- Hit GPT-5.4 rate limit during attempted subagent work; continued evaluation in main session with GLM 5.
- Completed decision on expanding Google Workspace action bus beyond Gmail + Calendar into Drive / Docs / Sheets.
- **Decision: NO for all three surfaces — defer for now.**
- Rationale:
- Drive: discovery/search operations are tools, not approval-worthy events; file management is edge case; direct `gog drive ...` usage is simpler.
- Docs: editing is inherently iterative (see, tweak, see again); document work belongs in focused tool flows, not a one-shot queue.
- Sheets: strongest candidate (structured writes map well to approval), but without a concrete use case, this is premature optimization.
- Preserved principle: the action bus works best for discrete, approval-worthy, low-iteration operations (like send draft, create event).
- Updated `WIP.drive-docs-sheets.md` with closed status and revisit criteria per surface.
- Updated `memory/tasks.json` to close:
- `task-20260311-1908-calendar-access` → done
- `task-20260311-1908-email-access` → done
- `task-20260311-1914-google-workspace-access` → done
- Google Workspace + n8n integration WIP (WIP.md) is now complete with evidence recorded in memory.