ainova-systems Upgrade Intelligence and packages
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
Run
intelligence update --preview(orintelligence update $ARGUMENTS --previewfor one named package). Use its CLI, project, and package sections as the complete plan; do not re-resolve versions independently.If the CLI or project engine version would change, read the authoritative
CHANGELOG.mdathttps://github.com/ainova-systems/intelligencefor every release incurrent < release <= target. If it is unavailable, stop before changing versions. Turn every crossed### Breakingitem into a post-condition to verify.Show the plan and breaking checklist to the user. The command without a mode also shows the plan and prompts; after approval, use
--applyfor an unambiguous non-interactive execution.If the plan reports a newer global CLI, run
intelligence upgrade --applyafter approval — it installs exactly the version the plan showed — then rerunintelligence update --previewwith the new executable. When the project section reports a schema stamped ahead of the stable line, the CLI that stamped it was a prerelease: useintelligence upgrade --next --apply. Ifupgraderefuses because npm did not make this installation, run the command its message names instead. Apply the resulting plan withintelligence update --apply, orintelligence update $ARGUMENTS --applywhen one package was requested.An applied update that renders must finish with
IS_STATUS=ok; preserve and stop on any other status. Then runintelligence status --check. Do not run a duplicate sync afterupdate --apply. Verify every crossed breaking post-condition directly and report any item that cannot be machine-verified.
Report versions before and after, the applied plan, post-condition results, and any remaining action. On a refusal, preserve the full error and stop instead of invoking hidden lifecycle operations.