Activity

Why

Get on the latest before building MCP OAuth — in particular laravel/mcp 0.8.0, so the OAuth work targets the current API rather than 0.7's (which would risk rework).

Correction worth noting

We were already on Laravel 13 — composer.lock was pinned to 13.14 (prod deploys from the lock, so prod's been on 13 since #160). The local vendor/ was just stale and reported 12.61. So this is a routine "update to latest," not a 12→13 major migration.

Changes (composer.json + composer.lock only)

• laravel/framework 13.14 → 13.15
• laravel/mcp 0.7.2 → 0.8.0 (constraint ^0.7 → ^0.8)
• laravel/boost 2.4.9 → 2.4.10, laravel/passkeys 0.2.1
• Symfony 8.0 → 8.1 across the board

Verification

• 139 tests pass on Postgres (incl. all MCP tool tests — mcp 0.8 didn't break our Server/$tools/Mcp::web usage).
• Pre-existing pint --test style drift in untouched files is out of scope (pre-commit only runs --dirty).

Note on laravel/ai

The official Laravel AI SDK exists, but it's deliberately not added — there's no AI/LLM usage in the stripped-down lookup archive. It's the right tool if/when the deferred derived layer (embeddings + hype-vs-substance extraction) is revived.

Next

With this merged, MCP OAuth (Passport + laravel/mcp OAuth, on your existing stu@ account) gets built on the latest base.