workspace-initlisted

# Workspace Init — One Boundary Around A Whole System Most real systems are several repositories. Opening one of them means everything else is invisible: the API contract lives next door, the deploy config lives somewhere else, and the agent guesses at both. The fix is a **parent directory** holding the repos as siblings, plus the folders no single repo can own. Open the session at the parent, and one context sees the whole system. ``` <workspace>/ ├── CLAUDE.md ← the map. What exists, where, on which port ├── <repo-a>/ ← real git repos, each with its own remote ├── <repo-b>/ ├── <repo-c>/ ├── server-info/ ← how to reach the machines (GITIGNORED) ├── plans/ ← /architect output, dated handoffs ├── project-knowledge/ ← durable knowledge, not session narrative └── docs/ ← runbooks, audits, decisions ``` The parent is usually **not** a git repo. If you make it one, `server-info/`, `.env`, and anything with a credential must be ignored before the first commit — history is forever. --- ## MODEL ROUTING | Role | Used here for | Effort | |---|---|---| | **bulk** | reading each repo's manifest, entrypoint, and scripts | `low` | | **orchestrator** | writing the map, deciding what earns a line | `high` | *Mapping as of 2026-07-25 — re-check on every model release:* bulk `claude-haiku-4-5`, orchestrator `claude-opus-5`. Reconnaissance across N repos is the one genuinely parallel step here — one cheap