v0.9.1

A patch hardening the upgrade path, from real-world adoption feedback across several consumer apps.

Fixed

• A pre-0.20 variadic withTags(...) in your boost config no longer aborts composer update. boost-core 0.20 made withTags(Tag::Php, ...) into withTags([...]), and the project-boost:sync composer hook requires your config — so an un-migrated variadic call threw a TypeError that aborted the whole update with a raw stack trace. project-boost:sync, project-boost:where, and project-boost:install now catch a config-load failure and print a clean, actionable migration hint with a non-zero exit instead. (A missing config likewise gets a friendly "create one" hint rather than an uncaught exception.)
• The README minimal example used the pre-0.20 variadic withTags(Tag::Laravel, Tag::Php) — which would TypeError if copy-pasted under boost-core ^0.22. Corrected to the array form.

Internal

• Added an @api-closure conformance test: it scans every boost-core import under src/ and asserts each symbol is part of boost-core's frozen @api surface, so the package can only depend on the 1.0-stable contract.

Docs

• UPGRADING.md: hand-edit withTags(...) → withTags([...]) before bumping (the post-update sync hook loads your config before any auto-migration can run).
• README.md: clarified that boost-core config resolves from .config/boost.php or a legacy root boost.php, while laravel/boost's boost.json stays at the project root (laravel/boost owns it).

Full Changelog: 0.9.0...0.9.1