kit-upgradelisted

Reconcile an installed Fieldbook copy against a NEWER kit zip. Reads .agent-docs/.kit-manifest.json, 3-way diffs ONLY kit-owned files (skills/hooks/rules/templates/schema — never the colleague's content dirs), and uses sha256-vs-manifest so a file the colleague edited is treated as "theirs" (shows a diff, never overwrites). Bumps the recorded kit-version. Reconciles the obligations-ledger form (ADR-0012) against re-detected comms posture — promoting a handoff `## Obligations` section into a standalone now/obligations.md, or retiring an empty file back to a section, content-preserving and manifest-recorded. When the manifest is MISSING but the tree is kit-lineage-shaped (hand-seeded / pre-kit port), emits a retro-adoption plan and backfills the manifest instead of stopping. Use when the author sends a newer Fieldbook zip, when a new kit's kit-version.txt is ahead of the installed one, or when upgrading/repairing an existing install. Consent-gated; shows a plan before writing.
armenr/modelmux · ★ 1 · AI & Automation · score 73

Install: claude install-skill armenr/modelmux

# /kit-upgrade — reconcile an install against a newer kit A later Fieldbook zip should merge into an existing install, never clobber it. This skill does a **3-way reconcile** keyed on the install manifest: for each file the kit owns, it knows what the kit last wrote (the manifest `sha256`), what is on disk now (possibly the colleague's edit), and what the new kit ships — and it only ever fast-forwards files the colleague hasn't touched. Everything else it shows as a diff and lets the human decide. It mutates nothing without an explicit yes. **Foreground in the main agent** — it needs to read the live tree and present diffs interactively. ## When to invoke - The author handed over a **newer zip** and the colleague unzipped it somewhere. - A new kit's `kit-version.txt` is ahead of the `kit-version` recorded in the install manifest. - Upgrading a profile in place, or repairing an install where a kit-owned file drifted. - A kit-lineage repo has **no manifest** (hand-seeded, or ported before the kit existed) and needs adopting into manifest-backed management — the §Retro-adoption branch below. ## When NOT to invoke - To ADD a module or bump Minimal→Standard→Full on the SAME kit version — that is a scaffold add-module run (`concierge/scaffold-plan.md`), not a version upgrade. - To UNINSTALL — that is `concierge/uninstall.md`. - With no newer kit present — there is nothing to reconcile against; run `/kit-doctor` instead. ## Steps ### 1. Read the install manifest (the bas