v0.9.0

Adopts the boost-core 0.22 line and moves every sync-driving and wrapper code path onto boost-core's frozen @api surface, ahead of boost-core's 1.0 freeze. Also fixes the console commands for the canonical .config/boost.php config layout.

Breaking

• Requires boost-core ^0.22 (was ^0.16). The boost stack moves together — sandermuller/package-boost-laravel ^0.14 (the Laravel umbrella that ships the emit(): iterable FileEmitter contract and floors package-boost-php ^0.18.1) and sandermuller/boost-skills ^2.0.6. Running against boost-core < 0.22 no longer resolves.

  Most apps only need to bump this package — boost-core comes through transitively:

  composer require "sandermuller/project-boost-laravel:^0.9"

  If you pin any boost package directly, move them to the 0.22 line together: sandermuller/boost-core ^0.22, sandermuller/package-boost-laravel ^0.14, sandermuller/boost-skills ^2.0.6.

Fixed

• project-boost:sync, project-boost:sync --dry-run, project-boost:where, and the non-interactive project-boost:install now resolve the boost config from both the legacy root boost.php and the canonical .config/boost.php layout (boost-core ≥ 0.17). They previously hard-coded a root boost.php check and aborted with No boost.php found for projects already on the .config/ layout, before the sync ever ran.

Internal

• Re-pointed the package onto boost-core's @api surface: sync now drives the BoostSync facade, agent targets resolve via Agent::target(), config reads via BoostConfig::load(), skill emit paths via AgentTarget::skillRelativePathForName(), and frontmatter via the now-@api FrontmatterParser. Every boost-core symbol the package imports is @api, so it stays stable under boost-core's 1.0 semver guarantee — no longer relying on engine internals.

Full Changelog: 0.8.2...0.9.0