Contribution and extension
Contribution and extension
Section titled “Contribution and extension”Start with the architecture map, identify the canonical schema/type and its downstream consumers, and add tests at both the owning package and integration boundary.
Choose a guide
Section titled “Choose a guide”Review checklist
Section titled “Review checklist”- Does the change belong in backend-core, backend-laravel, shared contracts, frontend-core, frontend-react, or a consumer?
- Are defaults and invalid-input behavior explicit?
- Are generated and consumer-owned paths still distinct?
- Do examples, templates, generated docs, and CI checks reflect the new behavior?
- Are package unit tests and cross-package consumer validation sufficient?
Use the repository’s existing Composer/PHP and npm/Vitest workflows. Do not run migration or destructive integration tests against a developer’s configured pilot database.