Google Drive Migration — Handoff (for the session that runs AFTER the move)

Written 2026-05-24. Sam wants to move the 2. Hook Street workspace from OneDrive to Google Drive so cloud tools can reach his files. This doc tells the next Claude Code session (opened in the new location) what to check + re-point.

FIRST — is this even urgent? (honest answer: no)

The Telegram bot reads your Google Sheets via API (already in the cloud) — it does NOT read this repo's files. So moving the repo to Google Drive does not change how the bot works today. The migration's value is future cloud access to the repo's docs, plus one clean cloud home. It is not a blocker for anything live. Do it deliberately, not rushed.

THE ONE REAL GOTCHA — read before moving

Claude Code keys its project memory + history to the working-directory PATH, and that memory lives in your USER PROFILE, not in the workspace folder:
C:\Users\ztrei\.claude\projects\C--Users-ztrei-OneDrive-2--Hook-Street-05--2026-BH\

If the workspace moves to a Google Drive path, Claude Code will treat the new location as a brand-new project with empty memory — all the MEMORY.md context (~86 files) won't auto-load. The .claude folder does NOT move with the files.

Options (pick before moving):
- A (safest): keep running Claude Code from the OneDrive copy (memory intact) and let only the cloud tools read the Google Drive copy. Two copies, OneDrive = the Claude-Code home.
- B: move, then manually copy the memory folder to the new project key (the next session can do this — it's a folder copy under .claude\projects\<new-path-slug>\).
- Don't discover this mid-move.

How to move (when you do)

1. COPY, don't move — keep OneDrive as backup until Drive is verified for ~1 week.
2. Google Drive for Desktop = Mirror mode, NOT Stream (Sam already knows this — "memory not stream"). Stream breaks Claude Code + git (files not physically on disk).
3. Copy 2. Hook Street → the Google Drive Mirror folder.

Verify-after-move checklist (next session runs this)

• [ ] git -C <newpath> status — clean, repo intact (the .git folder copies with the workspace ✓).
• [ ] git -C <newpath> remote -v — still points at zee78900/hookstreet-workspace ✓; do a test git fetch.
• [ ] clasp: .clasp.json uses rootDir: "." (relative) → portable. From command-inbox in the new path: clasp push -f works once clasp login is valid. Same for MIS/, HookStreet-Business-OS/sheets/.
• [ ] Memory: confirm MEMORY.md loads (the gotcha above). If empty, apply Option A or B.
• [ ] command-inbox/.claude-notify.json — copies with the workspace ✓ (it's inside it).
• [ ] Grep for any HARDCODED absolute paths (C:\Users\ztrei\OneDrive\2. Hook Street) in scripts/tools (e.g. tools/, scripts/tg.ps1, the portal build_index.py) → re-point to the new path.
• [ ] Update CLAUDE.md "Working dir" + the .claude path references.
• [ ] The bot is UNAFFECTED (reads Sheets via API) — verify it still answers as a sanity check.

Goal hierarchy (Sam's words)

Hook Street as the parent folder, corporate hierarchy underneath. Taxes + personal deferred. Start with the business folder only.