ark-upgradelisted

# /ark-upgrade — managed ArkGate upgrade **Contener · Guiar · Ordenar.** In plain words: contain the write, guide the next step, order leftover mess. This door is **Contener**: keep the pin current. Skills never enforce — CLI / hooks / CI do. **When:** bump the published `arkgate` package and refresh managed gates. **Not when:** session 0 (`/ark-adopt`) or leftover design (`/ark-explore`). ## When / not when | Use `/ark-upgrade` when… | Do **not** use it when… | |--------------------------|-------------------------| | Bump the pin and refresh managed gates | Session 0 / path missing → `/ark-adopt` | | Preview then `--apply` in this turn | Leftover design / map → `/ark-explore`; apply Shape → `/ark-autopilot` | ## Steps 1. Preview: `arkgate upgrade` (no writes). Default is **hosts keep** — do not retire other hosts’ skills. 2. Apply in this turn: `arkgate upgrade --apply` (installs the bumped package unless `--no-install`). Needs `--plan-digest` when applying managed files. 3. Re-run `arkgate-check --doctor`. Customized files stay unless you pass `--accept-conflicts` / `--refresh-skills`. ## Checklist - Preview unions `--tools` with hosts already in the repo. Multi-agent trees keep every host. - Apply must run the package install of the new pin. Do not skip `npm install` unless `--no-install` is explicit. - Refresh AGENTS.md **and** CLAUDE.md (same projection schema). - Prefer project `.agents/skills`. Do not duplicate the catalog into `~/.codex/skills`. The preview i