rule-flutter-flutter-repository-workflow-glob

To prevent raw payload map leakage in Flutter repository workflows, enforce strict DTO to Domain mapping boundaries. Repositories must not parse or build raw payload maps directly; instead, raw transport payload ownership must remain strictly within DAO or DTO boundaries.

Flutter repositories parse raw payload maps when DTO to Domain mapping discipline is missing. Applying a repository workflow enforces typed request DTO and command payload builders at the DAO boundary, including multipart assembly, to stop inline map payload construction.

To enforce DTO to Domain boundaries in flutter-app infrastructure repositories, apply glob scoped repository workflow rules to the lib/infrastructure/repositories path. This maintains typed DTO and command usage at DAO boundaries and prevents raw payload leakage.

Yes, you need to update mock DTO data and documentation before merging Flutter repository changes. The repository workflow requires mock data and DTO documentation to be fully synchronized prior to merge to maintain consistent domain boundaries.

The best way to document pagination contracts in Flutter repository workflows is to enforce repository glob rules that require explicit documentation of pagination and filtering contracts, aligning them with Laravel roadmap entries when APIs are implied.

Yes, you can use repository workflow glob rules for Flutter multipart request assembly. The workflow enforces typed request DTO and command payload builders at the DAO boundary, ensuring correct multipart assembly without raw payload map construction.