Change schemas, compilers, or generators

Change schemas, compilers, or generators

Schema and compiler change

1. Update the canonical JSON Schema under packages/backend-laravel/src/DSL/schemas/ or the shared contract schema under packages/contracts/schemas/.
2. Update backend-core compiler/IR/metadata handling when the parsed value affects semantics.
3. Update Laravel generator readers and output when the property changes generated behavior.
4. Update the UI contract producer and frontend runtime when the change crosses the backend/frontend boundary.
5. Update examples/templates and validate the consumer fixtures.

Generator extension

Add Laravel code generation to backend-laravel, using its existing generator interfaces, base classes, stubs, and registrar patterns. Keep framework dependencies out of backend-core. Check generation target selection and incremental output cleanup, not only the rendering of a new file.

Verification

Run the narrowest relevant Composer test suite first. For a change that crosses package boundaries, also run:

composer test:packages
php packages/backend-laravel/bin/mettada mettada:lint AlterationManagerExample

Run mettada:sync only in a disposable or intentionally selected consumer; inspect generated diffs and migrations before applying them. Follow the consumer’s isolated test instructions for database-backed suites.