1.2.1 - Align developer tooling versions and update documentation links

Added

• Documented CI-style quality and build commands, including:
  • php vendor/bin/maintainer quality:check --no-interaction
  • npm run build
• Added guidance on what the quality checks cover (PHP tests/format/static analysis/frontend tests and TypeScript) and what the frontend build produces (ESM client, IIFE bundle, and type declarations in dist/).
• Added contributor guidance in AGENTS.md around documentation quality, root-cause fix expectations, synchronization of legacy/Vue docs, and fully specified working example prerequisites and steps.

Changed

• Updated contributor development requirements to match CI:
  • PHP 8.5
  • Node.js 24.11+ (Node 24 series)
• Clarified the recommended local install order from the repository root:
  1. run Composer install
  2. run npm ci after composer install
• Updated tooling and dependency alignment requirements in CHANGELOG.md (including keeping Vite+/Vitest versions aligned across bundled and override dependencies).
• Updated security contact information in .github/SECURITY.md:
  • changed email from allan@wss.group to contact@atb.dev.br (documentation-only).

Updated (Tooling / Dependencies)

• composer.json
  • bumped artisan-toolbox/maintainer to ^1.11.0
  • bumped artisan-toolbox/core to ^1.1.0
  • updated author email to contact@atb.dev.br
• package.json
  • updated vite-plus to 1.5.0
  • updated vite-plugin-dts to ^5.1.2
  • adjusted overrides:
    • vite uses @voidzero-dev/vite-plus-core@1.5.0
    • vitest pinned to 5.1.0
  • added allowScripts for fsevents@2.3.3: true
  • kept engines.node >=20 and packageManager: npm@11.17.0

Documentation / Branding

• Updated documentation and metadata links to https://atb.dev.br across:
  • README badges and resource links
  • TODO.md guide URLs
  • resources/boost/.../SKILL.md dependency URLs
• Updated test-only badge expectations in tests/Unit/MosaicastMetadataTest.php to use https://atb.dev.br.

Compatibility & Migration Notes

• No public API/runtime behavior changes are implied.
• Developer environment compatibility may change due to updated documented requirements (PHP 8.5 and Node.js 24.11+).
• Tooling/version alignment changes (Vite+/Vitest and related type generation/build outputs) may affect build/test results if your local dependency set is not aligned.
• Link/domain changes may require updating external bookmarks or references to the previous documentation domain.

1.2.0 - Harden and standardize Inertia event delivery

Added

• Release README automation support: Added/updated a maintainer-generated README head used during releases to standardize the README header content for future release builds.

Changed

• Inertia event delivery improvements: Improved the safety of Mosaicast event delivery integrated with Inertia navigation.

  • Same-page reload hardening: The delivery logic now skips stale/invalid partial/history props.
  • Payload validation and normalization:
    • Validates and normalizes incoming event payloads.
    • Converts empty payload arrays to empty objects.
    • Ignores malformed event payloads without dropping other valid sibling events.
  • Dispatcher API alignment: Updated the delivery surface to use the Mosaicast dispatcher API where applicable, aligning event emission with the dispatcher-driven architecture.

• Documentation badge consistency: Standardized README badge/logo presentation for release and compatibility signaling to reduce ambiguity about version/support requirements.

Fixed

• More reliable event delivery under Inertia navigation: Inertia navigation should now more reliably deliver only valid Mosaicast events, avoiding cases where stale/invalid partial/history props could lead to incorrect event delivery.

Testing

• Updated Inertia flash/routing assertions: Refactored Inertia-related tests to better reflect Mosaicast’s event/flash lifecycle, including updated assertions for same-page reloads and navigation flows.

Compatibility / Migration

• If you rely on older dispatcher wiring or previously tolerated/serialized event payload shapes, ensure your emitted/serialized Mosaicast event payloads conform to stricter validation:
  • Events must have a valid non-empty name.
  • Payloads must match the expected structure.
  • Malformed/invalid event items are now skipped rather than propagated, so events with invalid shape may no longer reach the client even if other sibling events are valid.

1.1.1 - Update development tooling dependencies and CI configuration

Changed

• Updated artisan-toolbox/maintainer to 1.8.0 (dev dependency) to keep the project aligned with the latest maintainer tooling.
• Adjusted artisan-toolbox/maintainer version constraints during the upgrade path:
  • From ^1.6.0 to ^1.7.0
  • Finalized at 1.8.0
• Added phpstan/phpstan as a new development dependency (^2.2.8) to expand static analysis coverage during development/CI.
• Updated GitHub Actions PHP setup action: shivammathur/setup-php upgraded from 2.37.2 to 2.40.0.
• Changed CI test workflow branch targeting to push against the 1.x branch instead of main, aligning CI triggers with the project’s active maintenance branch strategy.

Added

• npm lockfile support was added and lock handling was adjusted to reduce duplicate lockfile noise.

Internal Maintenance

• Repository/workflow cleanup for dependency lockfiles:
  • Added ignore rules to prevent duplicate composer lock handling.
  • Ignored package-lock.json and adjusted Rector configuration accordingly.
• Improved maintainer tooling configuration related to the maintainer setup and automation.

Merged

• Merged origin/1.x into 1.x, incorporating upstream branch history into the current maintenance branch.

Notes on impact

• These changes are development and CI-focused. No production/runtime code, public API, or user-facing behavior changes were described.
• Adding PHPStan may cause new static analysis findings or require compatibility with the project’s existing PHPStan configuration/rules during CI runs.

1.1.0 - Add mosaicast helper and update development tooling

Added

• mosaicast() global helper: Introduces a new PHP helper function mosaicast(string|object|null $event = null, array $payload = []): Mosaicast (guarded with function_exists to prevent redeclaration).
  • Resolves the Mosaicast service from the container via resolve(Mosaicast::class).
  • If an $event is provided, it dispatches via $mosaicast->dispatch($event, $payload).
  • Always returns the Mosaicast instance to support fluent usage (e.g., mosaicast()->toSession($identifier)->...).

Changed

• Development dependency update: Adds artisan-toolbox/maintainer to composer.json require-dev.

  • Impact: Contributors/CI may need this additional dev dependency during local setup or development installs.
  • Runtime/API: No user-facing API or runtime behavior changes.

• README badge URL update: Updates the GitHub Actions test badge URL in README.md to the newer actions/workflows/.../badge.svg format.

  • Impact: Documentation-only; no code behavior changes.

1.0.0 - Integrate Inertia session broadcasting with Vue and improve CI/tooling

Added

• Inertia session broadcasting and Vue client integration: Added functionality to broadcast Inertia sessions and integrated the Vue client so front-end state/session updates can propagate via Inertia.

Changed

• CI quality checks now require artisan-toolbox/maintainer at ^1.5: Updated CI to use the intended maintainer tooling version to keep lint/quality results consistent.
• CI workflow order updated to install/require maintainer before quality checks: Quality checks now run only after the maintainer tool is available, making CI behavior more deterministic.
• Streamlined CI workflows and enhanced quality checks: Refactored CI configuration and improved quality-check coverage; this may cause new/previously later-failing checks to surface earlier in PR feedback.

Refactored / Internal Maintenance

• Tooling and codebase tooling refinements: Refactored command attributes, added/updated maintainer configuration, integrated Rector setup, refined PHPStan configuration, and updated tests to match.
• Documentation maintenance: Updated the documented PHP requirement and clarified engineering checklist items for contributors/maintainers.
• Changelog workflow and documentation structure: Removed the changelog workflow and reorganized documentation structure; changelog/release management now follows the updated release configuration.

Fixed

• Documentation PHP requirement + engineering checklist clarification: Corrected the PHP requirement in docs and clarified engineering checklist items to reduce onboarding/CI friction caused by incorrect environment assumptions.

Removed

• Changelog workflow: Removed the previous automated changelog workflow used by the repository.