I shipped Filament Studio 1.3.0, and it is the first version that feels AI-ready

I have been building Filament Studio as a dynamic data model manager for Filament v5 and Laravel 12 . The original value prop was runtime-defined collections and fields on top of an EAV model, so you can build flexible admin/data systems without creating a new migration for every content type. That part worked. But while working on the project, I kept coming back to a different question: If this data layer is dynamic, how should an AI agent interact with it? My answer in v1.3.0 was to add the MC