Kiro Crew worktree development

This skill applies ONLY to the Kiro Crew source repository or a worktree of it. Ignore it for other projects. One feature uses one dedicated worktree containing both src/kiro_crew/ and website/, including backend-only changes. Never edit the live checkout or start/stop the live gateway from a feature session.

Worktree and environment

# From the main clone; skip creation when already in the assigned worktree.
git fetch origin main
git worktree add ../kirocrew-wt-<name> -b feat/<name> origin/main
cd ../kirocrew-wt-<name>
python3 -m venv .venv
.venv/bin/pip install -e ".[voice]" --group dev
cd website && npm ci && cd ..
git worktree list

To bring the main clone itself current (the first path git worktree list prints), fast-forward it and nothing else:

git -C <main clone> symbolic-ref --short HEAD   # must print main
git -C <main clone> fetch origin main
git -C <main clone> merge --ff-only --no-autostash --no-overwrite-ignore origin/main

It refuses, changing nothing, when local main has diverged or a local change would be overwritten; then stop and report, because that state belongs to whoever left it. Before any rebase, checkout, switch, merge, pull or reset in a clone, run python3 <this skill>/scripts/live_checkout_guard.py <clone>. Exit 30 (or 2): a running gateway runs from it, so make a worktree; the operator's dashboard Update syncs that clone. Never overlay a whole tree with git checkout <ref> -- . or git restore --source <ref> .: neither moves HEAD, both overwrite local edits without asking, and the checkout form keeps every file upstream deleted. Never git stash: every worktree shares one stash list, so a pop can apply another session's work.