Multi-tenant Claude Code workspaces — design review and stress test

Initial design session completed. Design doc at ~/Claude/planning/multi-tenant-workspaces.md. Pattern: root=private, team/=shared nested git repo, hooks handle sync. Next: Claude Code expert review, then stress test against RC team.

14 design decisions captured in ~/Claude/planning/multi-tenant-workspaces/decisions.md. Key choices: root=private/team=shared, nested git repos (no submodules), git sync via hooks (pull on start + 30min staleness, push per commit), symlinked skills, per-person MCP, personal td + shared decision files, default-private routing, no VM for v1.

Expert review completed. Confirmed: nested repos work, skill symlinks work, @imports in CLAUDE.md work, SessionStart hook exists. Changed: use SessionStart for pull+skill-link (not UserPromptSubmit), use @team/TEAM.md import (not 'read this file' instruction), push via CLAUDE.md instruction (not PostToolUse hook — too fragile), absolute paths in hooks via $CLAUDE_PROJECT_DIR, SessionStart also injects team repo git status.

RC stress test completed. Core pattern holds with two adaptations: (1) team-scoped folders within team/ (org/, moments/, referral/, affiliate/) for three-level access, (2) product-toolkit stays independent per PM. Strain points: autonomous ops need VM agent identity (deferred), submodules inside nested repo adds complexity, state/current.md needs splitting per team. Doc at ~/Claude/planning/multi-tenant-workspaces/rc-stress-test.md

RC stress test conclusion: pattern validated but no urgent need. RC is single-user today. Implement when 2nd PM joins. Refinements: eliminated company-context folder, excluded signals/voc/incidents/priorities/actions from team/, state stays private (HoP dashboard), goals in rc-context not separate folder, HoP uses same pattern as PMs. JB is the immediate target.

Drafted all JB implementation files. Templates at ~/Claude/planning/multi-tenant-workspaces/jb-templates/: TEAM.md, CLAUDE-hazel.md, CLAUDE-ivan.md, settings.json, 3 hook scripts, setup.sh. Migration plan at jb-migration.md with step-by-step instructions and rollback plan.