Askr Laravel Laravel Package

Product Decisions This Supports

• Dependency/upgrade planning, not feature planning. v1.8.4 is a driver-sync release: the Laravel bindings are being brought into parity with Askr core 1.8.4. There is no new capability, no API surface described, and no breaking change signaled. Treat it as a maintenance delta.
• Build vs. buy at the integration layer. This package is thin glue (service provider + config + driver bindings) over an external core. Buying it is cheap and reversible; the real commitment is to Askr core, which this release does not describe.
• Version-parity policy. The release reinforces that driver versions track core versions. Any product plan that pins Askr should also pin the driver and define an upgrade window, because driver lag is the practical failure mode.
• Risk register entry for changelog opacity. The release body delegates all substance to an external CHANGELOG. That is a legitimate signal for a "verify before upgrading" gate rather than an "auto-bump" gate.
• Not a use case in itself. This package does not unlock a user-facing feature. It only matters if the product already depends on Askr core for whatever the core does (search/Q&A/prompt-style abstraction, per its own docs). Do not let this release enter a roadmap as if it were new functionality.

When to Consider This Package

Consider it when:

• Askr core is already in the stack and you need first-party Laravel bindings rather than hand-rolling container wiring.
• You want maintainer-aligned version parity with Askr 1.8.x and are comfortable tracking the core project's release cadence.
• You value a small, single-purpose adapter over a broader framework package.

Look elsewhere when:

• You do not use Askr core. This package has no standalone value.
• You need self-contained packages with changelogs, migration notes, and a published support matrix in-repo — this release provides none of those.
• You require an LTS/support commitment or a CI-tested Laravel/PHP version grid before adopting.
• The integration is genuinely thin. A service provider plus a config file is often a day of work; verify the driver does materially more than that before accepting a dependency and its upgrade obligations.

Adoption gate: confirm the actual driver delta in the core CHANGELOG, confirm the tested Laravel and PHP versions, and confirm that no core 1.8.x deprecations leak through the adapter.

How to Pitch It (Stakeholders)

Executives: A small, low-risk maintenance release from the existing maintainer that aligns the Laravel bindings with Askr 1.8.4. No new capability is claimed and no breaking change is signaled. It is a routine dependency update, not a strategic bet — and not a reason to adopt Askr on its own.

Engineering: Patch-level driver bump. The substantive change detail lives in the core CHANGELOG, so before we merge: pull the exact delta, confirm the Laravel/PHP version matrix, check whether any 1.8.x core deprecations surface in the adapter, and confirm the package's tests pass on our supported versions.

Recommendation: Approve as a routine upgrade if Askr is already in the stack. If Askr is not in the stack, no action — this release does not change the evaluation.