feat(spawn): add Treehouse worktree setup hook

[michael-sb]

Intent

Add per-project worktree setup via treehouse post_create hook. A single global hook script (bin/fm-treehouse-post-create.sh) is wired in ~/.config/treehouse/config.toml and fires when treehouse provisions or resets a worktree. It locates firstmate's data/ from its own location and runs data/-setup.sh if it exists. Non-fatal on failure, logs to state/treehouse-setup-.log. Replaces earlier fm-spawn-based approach with treehouse-native lifecycle hook.

What Changed

• Adds a Treehouse post_create hook script that runs optional per-project setup scripts from firstmate data and records non-fatal setup output under state logs.
• Extends bootstrap to detect, validate, and install the global Treehouse hook configuration with hardened command parsing and quoting.
• Updates spawn behavior, documentation, and tests for Treehouse-native worktree setup and hook environment handling.

Risk Assessment

✅ Low: Captain, the change is bounded to Treehouse hook wiring/spawn context plus focused tests, and I did not find substantiated merge-blocking or follow-up issues.

Testing

Inspected the targeted diff, ran the focused hook/bootstrap/spawn shell tests, captured reviewer-visible CLI evidence for hook wiring and setup execution/logging, and confirmed the worktree remained clean.

Evidence: treehouse-post-create-e2e-transcript

Treehouse post_create hook e2e verification
repo=/Users/michael/.no-mistakes/worktrees/458d9fed4d70/01KVSZTTNA0BR1Y3D5XK12THFM
commit=539e5297f842a684de95513470b186397e030a5a

$ FM_HOME=/var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e/fm-home XDG_CONFIG_HOME=/var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e/fm-home/xdg bin/fm-bootstrap.sh install treehouse-post-create-hook
installing treehouse-post-create-hook: /Users/michael/.no-mistakes/worktrees/458d9fed4d70/01KVSZTTNA0BR1Y3D5XK12THFM/bin/fm-bootstrap.sh install treehouse-post-create-hook

$ sed -n 1,20p /var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e/fm-home/xdg/treehouse/config.toml
[hooks]
post_create = ["'/Users/michael/.no-mistakes/worktrees/458d9fed4d70/01KVSZTTNA0BR1Y3D5XK12THFM/bin/fm-treehouse-post-create.sh'"]

$ (cd /var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e/worktrees/app && FM_HOME=/var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e/fm-home /Users/michael/.no-mistakes/worktrees/458d9fed4d70/01KVSZTTNA0BR1Y3D5XK12THFM/bin/fm-treehouse-post-create.sh)

$ cat /var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e/worktrees/app/setup-marker.txt
READY_FROM_SETUP

$ cat /var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e/fm-home/state/treehouse-setup-app.log
setup ran in /var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e/worktrees/app

$ test -f /var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e/fm-home/state/treehouse-setup-app.log && test "$(cat /var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e/worktrees/app/setup-marker.txt)" = READY_FROM_SETUP
verified: bootstrap wrote the hook config, the hook selected data/app-setup.sh for the matching project worktree, setup output was logged, and the worktree was modified by setup.

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

🔧 **Review** - 1 issue found → auto-fixed ✅

• ⚠️ bin/fm-bootstrap.sh:130 - treehouse_hook_command_usable accepts an executable hook path anywhere in the shell command, so a post_create entry like echo /abs/bin/fm-treehouse-post-create.sh is treated as configured even though Treehouse would never execute the hook. Bootstrap would then stay silent while per-project setup never runs; restrict the match to the executable command word, allowing only known-safe prefixes such as environment assignments.

🔧 Fix: Captain, tighten treehouse hook detection
✅ Re-checked - no issues remain.

✅ **Test** - passed

✅ No issues found.

• git status --short --branch
• git diff --stat 2a2fe0566e63b883ec53dc3e34dc14306689f989..539e5297f842a684de95513470b186397e030a5a
• git diff --name-only 2a2fe0566e63b883ec53dc3e34dc14306689f989..539e5297f842a684de95513470b186397e030a5a
• tests/fm-treehouse-post-create.test.sh
• tests/fm-bootstrap.test.sh
• tests/fm-spawn-treehouse-env.test.sh
• Created an isolated firstmate home and git worktree under /var/folders/t0/dws_m6l52lj97dkt9f4hd_sh0000gn/T/no-mistakes-evidence/01KVSZTTNA0BR1Y3D5XK12THFM/treehouse-post-create-e2e, ran bin/fm-bootstrap.sh install treehouse-post-create-hook with local FM_HOME/XDG_CONFIG_HOME, then invoked bin/fm-treehouse-post-create.sh from the matching worktree and verified the setup marker plus state/treehouse-setup-app.log.
• git status --short

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

[michael-sb]

Sorry - my firstmate got a bit carried away - he can be quite proactive :D

[ki-za]

Scout plan (huddle-app second mate, 2026-08-29)

Proposed Options / Plan / Blocking / Lead decisions for this ticket, from the ha-app-plan scout report.

Current state

• AppMenu.svelte:36-117 implements a top-right menu containing font, one coupled sent-reply layout, a read-only waiting list, and Open in Browser. It lacks shortcuts, theme, replyAlignment, and replyMarker settings.
• App.svelte:291-317 keeps bright intent, Accept, and menu in one top row. Ticket feat(spawn): add Treehouse worktree setup hook #47 instead rules a faint secondary-text intent at top left, an unbordered menu button at top right, Accept in a bottom row, and queue information always visible at bottom left. The ticket body wins over the v3 image.
• The menu button has a border at rest (app.css:128-131). Queue information exists only inside the menu (AppMenu.svelte:84-107). Keycaps always render. Font and reply layout each write their own localStorage key from App.svelte:32-40,144-153; there is no shared settings model.
• app.css:103-110,170-176,204-209,387-399,454-455,482-489,560-565,623-643 rounds buttons, selects, labels, preview fills, and composer fills. The feat(spawn): add Treehouse worktree setup hook #47/fix: persist watcher wakes across supervision gaps #29 ruling permits rounded corners only for the windowBorder, panels, replyFrames, and the menu pop-up.
• lume.css:4-17 exposes palette-shaped --lume-* names directly to components. Issue fix(supervision): opencode-aware composer-idle detection + exclude supervisor pane from stale scan #49 requires components to consume only background, surface, divider, tier, and signal role tokens.

Options

• One settings model — all menu controls read and write one validated presentation state; matches feat(spawn): add Treehouse worktree setup hook #47 and feat: add crash and reboot resilience for firstmate #51 and supports a held-out setting.
• Per-control localStorage — extends the current code quickly, but creates precedence, migration, and extension conflicts and violates the one-settings-model ruling.

The body ruling leaves no live placement alternative: the in-app menu remains available in the browser and Hammerspoon host, while the ruled direct intent, queue information, and Accept remain outside it.

Recommended Plan

Modules: Restructure App.svelte into a top intent/menu row, scrollable contribution region, and bottom queue/Accept row inside the windowBorder; extend AppMenu.svelte with queue list, font, shortcuts, theme, replyAlignment, replyMarker, and Open in Browser; add one shared app/src/lib/settings.ts; add an always-visible queue summary component; map theme choices through #49 role tokens in theme/; update app.css; extend settings reducer, persistence, menu focus, and migration tests.

Seams: The replay-derived queue supplies a count/status summary outside the menu and an ordered read-only list inside it; neither surface switches Huddles. Accept stays a direct button and retains server authority. Menu commands call existing Huddle app actions. Every setting uses one model and persistence path; hiding keycaps leaves shortcut handlers enabled. Theme selection changes role-token resolution only. replyAlignment and replyMarker change presentation only. Menu open/close restores focus and preserves native button/select behavior.

Validation criteria: Intent remains one faint secondary-text line at top left; the menu button rests at top right with no border or background; queue information remains visible at bottom left for zero and several waiting Huddles; Accept stays inside the bottom windowBorder row; the queue list remains ordered, read-only, and menu-only; keycaps hide while every shortcut still works; both leadReply settings change no message data; only the menu pop-up uses rounded corners outside the three ruled borders; components contain no palette swatch or hex names; a held-out setting uses the same settings model. Run bun run check. Capture closed-menu and open-menu pictures at 30rem and narrow widths, each with keycaps shown and hidden, then run a keyboard-only menu/Accept smoke.

Blocking?

blocked by #25, #45, #49, and #51 — the complete menu consumes the shortcut contract, split leadReply settings, role-token theme, and the one Huddle app settings model. The top/bottom shell move can land separately, but that partial change does not complete this ticket.

Lead decisions

None. The 2026-08-29 ruling fixes placement, direct information, menu contents, keycap optionality, and token use. #44/#51 own the remaining settings persistence decision.