doccraft-updatelisted

# doccraft — update skills and openspec instructions ## When to use - Periodically to keep doccraft skills and openspec instructions current. - After a teammate updates doccraft in a shared repo (check the version stamp in `doccraft.json` against the latest npm release). - When `doccraft-config` or other skills mention features that do not seem to work — you may be running an older skill body. ## Configuration Read `doccraft.json` at invocation. The `version` field is this skill's primary input — it determines which migration entries apply. If the file is missing, treat the local version as **unknown**, warn the user, and proceed. Relevant keys: - `version` — the currently installed doccraft version. Used to filter the migration manifest. Default: none (required; treat as unknown if absent). - `docsDir` — root folder for all docs. Default: `docs`. Used post-update for context when checking extension fragments in installed skills. ## Workflow ### 1. Read the local version Read `"version"` from `doccraft.json` at the project root. If the file does not exist, treat the local version as **unknown** and warn the user — then proceed. ### 2. Fetch the manifest Run exactly once: ``` npx doccraft@latest llm ``` Parse the JSON output. The relevant fields are: - `version` — the latest doccraft version. - `migrations` — array of `{ from, to, summary, steps[] }` entries. If the invocation fails (no network, npx error), report the error and stop. NEVER guess at migrat