v0.10.3

A follow-up to 0.10.2. The v2 CLI consolidated its command surface right after that release, so the switch described in the update skill named commands that no longer exist. Everything else in 0.10.2 stands: this is still the final vendored line, it keeps working, and this repository stays where it is.

Highlights

Fixed

• The CLI switch named retired commands. Converting an archived v1 project is now intelligence init — --preview stages and verifies without writing, --apply converts — instead of a separate migrate. doctor became status --check, and upgrade folded into a single intelligence update that covers the CLI, the project's schema and its package ranges in one plan. Step 7 of intelligence-update still used the old names and would have failed at the first command. Harmless in practice, since that step refuses to run while the CLI is a prerelease — but wrong.
• The availability check reads both npm dist-tags. A stable latest proceeds. A prerelease-only channel stops and says so, unless the user explicitly asks for the release candidate in that conversation — in which case it is named as a release candidate every time it is mentioned. The skill never puts a prerelease on a project on its own initiative.

No schema change: the stamp advances to 0.10.3 on update.

Full changelog: v0.10.2...v0.10.3

Install

Paste this to your AI agent:

Update intelligence-sync: fetch the latest engine from https://github.com/ainova-systems/intelligence-sync and run its update flow to migrate this project to the newest version. Leave my rules, agents, and project skills untouched. If it fails, read the CHANGELOG "### Breaking" entries between my version and the latest, base your fix plan on them, make sure you are running the latest scripts, and retry; ask me only if it still fails.

New projects: start with the CLI instead — npm install -g @ainova-systems/intelligence@next, then intelligence init.