v1.1.0

Adds project-boost:reconcile — a guided takeover that captures laravel/boost-seeded agent guidance before a sync would overwrite it. Additive; no migration.

Added

• project-boost:reconcile — a diff-first guided takeover for the laravel/boost coexistence seam. boost:install seeds its guidelines directly into your agent files (CLAUDE.md / AGENTS.md / GEMINI.md / …) inside a <laravel-boost-guidelines> marker; a markerless boost-core sync regenerates those files wholesale, so hand-authored content outside the marker is lost. reconcile detects foreign-seeded files by that marker (the same signal vendor/bin/boost doctor uses), backs each up verbatim to .boost-reconcile/, captures the hand-authored residual into .ai/guidelines/reconciled.md (append-with-dedup — it never clobbers edits you have made there), then runs project-boost:sync so the captured content is re-composed into every agent file. Options: --dry-run, --force, --no-sync.
• project-boost:sync now warns when a sync would overwrite laravel/boost-seeded guidance, pointing at project-boost:reconcile first (warn-and-continue, matching boost-core's default).
• A post-boost:install nudge toward project-boost:reconcile, fired only after a bare boost:install that actually seeds guidance — silent after boost:install --mcp (which keeps laravel/boost's writers dormant, so nothing is seeded) and while project-boost:install is driving its own sequence.

Docs

• New docs/laravel-coexistence.md: the canonical command sequence (boost:install once → project-boost:reconcile once → project-boost:sync ongoing), the division of labor with laravel/boost, and why a bare vendor/bin/boost sync on a wrapper project loses content. The README and PUBLIC_API.md (which adds project-boost:reconcile to the frozen CLI surface) link to it.

The new command is part of the 1.x @api/CLI surface from this release. Requires boost-core ^1.0; validated across the CI matrix.

Full Changelog: 1.0.0...1.1.0