initlisted

<objective> Set up foundry on new machine: | Action | What happens | | --- | --- | | Detect Python 3.10+ (`python` / `py -3` / `python3`); install `~/.local/bin/python` shim if needed | ✓ | | Merge `statusLine`, `permissions.allow`, `enabledPlugins` → `~/.claude/settings.json` | ✓ | | `rules/*.md` → `~/.claude/rules/` | symlink | | `TEAM_PROTOCOL.md` → `~/.claude/` | symlink | | `skills/*` → `~/.claude/skills/` | symlink | | `hooks/hooks.json` | auto — plugin system | | Conflict review before overwriting existing user files | ✓ | **Why symlink rules and skills (not copy)?** Rules, TEAM_PROTOCOL.md, and skills load at session startup. Symlinks = every session gets plugin's current version — no stale copies, no re-run after upgrades. Broken symlink after upgrade = obvious error; stale copy silently serves old content. **Why symlink skills explicitly?** `claude plugin install` creates `~/.claude/skills/` symlinks on first install but does NOT update them on upgrade — old version directory stays in cache, symlinks go stale. Init's stale-version detection (same pattern as rules) replaces them silently on every re-run. **Why not symlink agents?** Agents must always use full plugin prefix (`foundry:sw-engineer`, not `sw-engineer`) for unambiguous dispatch. Plugin system exposes agents at `foundry:` namespace — no `~/.claude/agents/` symlinks needed. (Stale agent symlinks from prior installs are removed by init's Phase 1 cleanup.) **Why hooks need no action?** `hooks/hooks.json