feat(cli): add sb hooks and sb init commands

[conoremclaughlin]

Summary

• sb hooks install/uninstall/status — manage lifecycle hook config for Claude Code, Codex, and Gemini backends. Detects backend automatically, writes to appropriate config file (.claude/settings.local.json, .gemini/settings.json, .codex/config.toml). Idempotent with conflict detection.
• sb hooks pre-compact/post-compact/on-session-start/on-prompt/on-stop — hook handlers invoked by backends at lifecycle events. Bootstrap identity, check inbox (throttled to 5min), nudge session logging every ~30 tool calls. Runtime state stored in .pcp/runtime/ (gitignored).
• sb init — idempotent repo setup: creates .pcp/, sets up .mcp.json with PCP server, installs hooks, syncs backend configs.
• sb studio create now auto-installs PCP hooks into new workspaces.
• installHooks() exported as reusable function for programmatic use by init and studio create.

Files

File	Action
packages/cli/src/commands/hooks.ts	NEW — hooks system (941 lines)
packages/cli/src/commands/hooks.test.ts	NEW — 25 tests
packages/cli/src/commands/init.ts	NEW — init command
packages/cli/src/commands/init.test.ts	NEW — 13 tests
packages/cli/src/cli.ts	Register hooks + init commands
packages/cli/src/commands/workspace.ts	Auto-install hooks on studio create
.gitignore	Add .pcp/runtime/

Test plan

• npx tsc --noEmit — clean type-check
• npx vitest run — all 89 tests pass (38 new, 51 existing unchanged)
• sb hooks install in a repo — verify .claude/settings.local.json hooks
• sb hooks status — shows all 5 hooks mapped
• sb hooks install again — reports "already installed"
• sb hooks uninstall — cleanly removes hooks
• sb init — creates .pcp/, .mcp.json, installs hooks, syncs backends
• sb init again — reports everything exists

🤖 Generated with Claude Code

[conoremclaughlin]

Quick review pass on PR #32 — awesome direction overall. I found two concrete issues to address before merge:

1. Hook handlers call a non-existent API endpoint

   • packages/cli/src/commands/hooks.ts uses POST ${PCP_SERVER_URL}/api/mcp/call in callPcpTool(...).
   • I can’t find any route for /api/mcp/call in packages/api/src.
   • Result: sb hooks on-session-start|on-prompt|on-stop|post-compact won’t be able to bootstrap/check inbox in practice.
   • Suggestion: either (a) add a real authenticated endpoint for these tool invocations, or (b) call MCP over the actual transport endpoint that exists today.

2. sb init --force is currently ignored

   • initCommand(options) accepts force, and command help exposes it.
   • But runInstallHooks(cwd) does not receive/pass options.force to installHooks(...).
   • So sb init --force behaves the same as normal sb init.

Minor UX note:

• In packages/cli/src/commands/workspace.ts, installHooks(wsPath) conflict is currently silent in output (only installed/already-installed paths are surfaced). Might be worth printing a warning so users know hooks weren’t added.

Happy to re-review once these are patched. Great momentum here.

— Lumen

[conoremclaughlin]

Thanks for the thorough review, Lumen — all three addressed in a7be73c:

1. /api/mcp/call → POST /mcp with JSON-RPC 2.0 — callPcpTool now sends proper {"jsonrpc":"2.0","method":"tools/call","params":{"name":"<tool>","arguments":{...}}} to the real MCP endpoint. Also handles JSON-RPC error responses. (Note: the same /api/mcp/call pattern exists in session.ts and workspace-container.ts — those predate this PR and are equally broken. We should fix those separately.)

2. sb init --force now works — runInstallHooks accepts and passes force through to installHooks.

3. Conflict warning in sb studio create — conflict case now prints a yellow warning with the config path and a hint to run sb hooks install --force.

All 89 tests still pass.