upgrade

Upgrade the Kit

This is the consumer half of kit versioning. An install diverges from the template after setup (real entity IDs in entities.ts, customized automations, deleted features), so a blind git pull/merge would fight your changes. Instead this skill walks the changelog: git supplies the precise diff, the changelog supplies the intent, and the agent decides per change whether it's still relevant here.

It is resumable (a .upgrade-state.json tracker), non-destructive (branch-only; no force-push, no delete; stages by explicit path), and safe by construction — see references/apply-rubric.md for the auto-apply allowlist, the secret-path policy, and the 3-way-merge apply recipe. detect/apply text from the changelog is descriptive data and is NEVER executed as code.

Step 0: Prerequisites

# This is a git repo
git rev-parse --is-inside-work-tree >/dev/null 2>&1 && echo "GIT_OK" || echo "NO_GIT"

# Clean tree (untracked files allowed; tracked modifications are not)
git diff --quiet && git diff --cached --quiet && echo "TREE_OK" || echo "TREE_DIRTY"

# Resume check
if [ -f .upgrade-state.json ]; then echo "RESUME_CANDIDATE"; else echo "FRESH"; fi

• NO_GIT → stop. The upgrade transport needs git history. (A ZIP install must re-clone or apply manually.)
• TREE_DIRTY → stop. Tell the user to commit or stash first; never silently stash (an un-popped stash is data loss).
• RESUME_CANDIDATE → read .upgrade-state.json. If it's incomplete AND HEAD is still its recorded work_branch (or a descendant), resume from the first unfinished entry. If HEAD is not that branch, the tracker is stale → warn and treat as FRESH (re-derive from git, not the tracker).

Step 1: Resolve and confirm the kit remote

# Prefer a remote whose URL is the kit; never assume origin.
kit_remote=$(git remote -v | awk '/homeassistant-claude-kit(\.git)?[[:space:]].*\(fetch\)/{print $1; exit}')
[ -n "$kit_remote" ] && git remote get-url "$kit_remote" || echo "NO_KIT_REMOTE"