dxkit-updatelisted

# dxkit-update This skill drives the dxkit upgrade flow conversationally. It's the "I have something working — make it newer" surface (complement to `dxkit-onboard` for fresh installs and `dxkit-fix` for repairs). ## When to use this skill Use when: - "Is there a new dxkit version?" - "Update dxkit" - "Upgrade to latest" - "What changed in dxkit recently?" - "What's new in 2.5.5?" (or any other specific version) - "Should I upgrade?" Don't use when: - Customer has no `.vyuh-dxkit.json` (they need `dxkit-init`, not update) - Something is BROKEN — use `dxkit-fix` first; then maybe update after - Customer wants to roll back to an older version (downgrade — surface the risk + manual command, don't auto-execute) ## How the upgrade works (two stages) dxkit ships in two layers and an upgrade touches both: 1. **The binary** — `@vyuhlabs/dxkit` npm package. `npm update` or `npm install @vyuhlabs/dxkit@<version>` replaces the local binary. 2. **The scaffold** — files in the customer's repo (`.devcontainer/`, `.githooks/`, `.claude/skills/dxkit-*/`, `AGENTS.md`, `CLAUDE.md`, `.github/workflows/dxkit-*.yml`). `npx vyuh-dxkit update` refreshes these to match the new binary's templates. Both run for any non-trivial upgrade. The CLI subcommand `vyuh-dxkit upgrade` orchestrates them; this skill drives the customer through the orchestration with explanations and confirmations. ## The upgrade loop ``` [1] Read the plan → npx vyuh-dxkit upgrade --plan --json [2] Explain the d