Skip to content

v0.10.2

Choose a tag to compare

View all tags
@dzykovic dzykovic released this 26 Aug 16:31
· 3 commits to main since this release
v0.10.2
9d08f88

The final release of the vendored engine. It keeps working, this repository stays at the URL your update.sh already clones, and nothing changes on its own — a project can stand still here indefinitely. Development continues in the intelligence CLI (ainova-systems/intelligence), and from this release the update flow can walk you across, one way, on an explicit yes.

The CLI is still in prerelease, so the switch below stays dormant until it is generally available: the skill checks, says so, and leaves the project on the vendored setup.

Highlights

Added

  • intelligence-update can perform the switch to the CLI — new step 7, only on an explicit yes. After a normal update leaves the project healthy it checks that the CLI is generally available (a published version with no prerelease suffix — otherwise it says so and stops), describes exactly what would change, requires a clean worktree, previews with intelligence migrate --dry-run, confirms a second time, then runs intelligence migrate and verifies with doctor + sync. The --yes flag covers the update diff only and never this decision.
  • Two runs therefore get a project across: the first brings the engine to this final version, the second offers the move — which is also the order migrate requires, since it accepts only a project already at the final vendored schema.

Changed

  • sync.sh and update.sh print one stderr line naming this the final vendored line and pointing at the update skill (IS_SUPPRESS_CLI_NOTE=1 silences it). stdout and the IS_STATUS contract are untouched.
  • The release-npm workflow is removed — publishing the CLI belongs to its own repository.

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

Full changelog: v0.10.1...v0.10.2

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 i -g @ainova-systems/intelligence, then intelligence init.

Assets 2
Loading