openpress-upgradelisted

# OpenPress Upgrade `openpress-upgrade` owns framework package upgrades and workspace migrations. Use `openpress` for command/source-boundary routing, then use this skill for the upgrade and migration workflow. ## Responsibilities - Detect installed and target OpenPress versions. - Refresh framework packages and installed OpenPress skills after confirmation. - Select applicable migration docs from the OpenPress repo. - Scan workspace source before editing. - Generate and implement migration plans from the docs. - Run migration QA checkpoints in a loop until all pass or a blocker needs user input. ## Source Boundaries Use the source/generated boundary from `openpress`. During migration, edit only: - `press/` - root `package.json`, especially the `"openpress"` field - local skill files in `.agents/skills/` or `.claude/skills/` - project config explicitly named by a migration doc Do not hand-edit `node_modules/`, `public/openpress/`, `dist-react/`, `.deploy/`, `.openpress/`, or `.turbo/cache/`. ## Workflow ### 0. Resolve The CLI Command Use the workspace's local OpenPress CLI. Do not use `npx open-press`; `open-press` is a binary name, not the npm package name. Use one of these forms: ```bash open-press <command> . npm run openpress:skills node node_modules/@open-press/core/engine/cli.mjs <command> . ``` Prefer the core CLI path in workspaces that only install `@open-press/core`. Use the `open-press` binary only when `@open-press/cli` is installed and `node_modules/