intelligence-updatelisted

# Update intelligence The CLI owns planning and application. This skill interprets the plan, reads the changelog across an engine-version gap, obtains approval, and verifies the result. ## Steps 1. Run `intelligence update --preview` (or `intelligence update $ARGUMENTS --preview` for one named package). Use its CLI, project, and package sections as the complete plan; do not re-resolve versions independently. 2. If the CLI or project engine version would change, read the authoritative `CHANGELOG.md` at `https://github.com/ainova-systems/intelligence` for every release in **`current < release <= target`**. If it is unavailable, stop before changing versions. Turn every crossed `### Breaking` item into a post-condition to verify. 3. Show the plan and breaking checklist to the user. The command without a mode also shows the plan and prompts; after approval, use `--apply` for an unambiguous non-interactive execution. 4. If the plan reports a newer global CLI, run `intelligence upgrade --apply` after approval — it installs exactly the version the plan showed — then rerun `intelligence update --preview` with the new executable. When the project section reports a schema stamped ahead of the stable line, the CLI that stamped it was a prerelease: use `intelligence upgrade --next --apply`. If `upgrade` refuses because npm did not make this installation, run the command its message names instead. Apply the resulting plan with `intelli