fix(claude): stop project SessionStart hook from firing at user scope

[dijonkitchen]

Problem

dotfiles/.claude/settings.json did double duty: it was both the dotfiles repo's project settings and, via link-agents.sh, the user/global settings symlinked to ~/.claude/settings.json.

Because the user-scope copy carried a SessionStart hook pointing at the project-relative $CLAUDE_PROJECT_DIR/.claude/hooks/session-start.sh, that hook fired in every project and errored in any repo that doesn't ship the script:

/Users/.../dp_customer_data_exchange/.claude/hooks/session-start.sh: No such file or directory

Fix

Split the two roles:

• .claude/settings.global.json (new) — universal user-scope prefs (permissions, statusLine, editorMode, worktree, verbose), no project-relative paths. link-agents.sh now links this into ~/.claude/settings.json.
• .claude/settings.json — trimmed to just the SessionStart bootstrap hook; read only as the dotfiles repo's project settings.

Web bootstrap is unchanged: opening the repo still fires the project hook, which runs link-agents.sh.

Result across contexts

• Local — prefs apply everywhere via user scope; the project hook no-ops locally (CLAUDE_CODE_REMOTE != true). No more error in other repos.
• Global — ~/.claude/settings.json is purely universal prefs, zero project paths.
• Claude Code web — unchanged; project hook fires and materializes globals into ~/.claude.

Tests

• bats tests/link-agents.bats → 6/6 pass, including a new test asserting the global link resolves to settings.global.json and that global has no CLAUDE_PROJECT_DIR while project keeps the hook.
• shellcheck clean.
• Pre-existing bootstrap.bats failures (mise ... not trusted in the sandbox) are unrelated — confirmed identical on a clean tree.

🤖 Generated with Claude Code