rule-flutter-flutter-documentation-contracts-always-on

To enforce documentation updates for Flutter changes before code merges, this rule checks that foundation_documentation files, including screens and domain_entities, are updated alongside the PR. It prevents documentation drift by verifying DTO references and system roadmaps reflect the new scope.

Documentation drift between code and mocks occurs when Flutter changes merge without synchronized updates to foundation_documentation. This rule prevents drift by requiring up-to-date screen, domain entity, and DTO reference docs before code merges, ensuring alignment on contracts and UI flows.

When modifying Flutter screens, foundation documentation files requiring updates include foundation_documentation/screens/*.md for UI flows, foundation_documentation/domain_entities.md for prototype data, module docs for DTO references, and foundation_documentation/system_roadmap.md for scope tracking.

This documentation governance rule is specifically designed for Flutter projects requiring synchronization between code, mocks, and documentation. It applies to foundation_documentation structures, screen flows, and DTO references unique to Flutter development workflows.

To verify foundation documentation for a Flutter change PR, review the PR to confirm corresponding foundation_documentation updates exist across screens, domain_entities, module docs, and system_roadmap. Update any missing documentation before proceeding with the code merge.

You need to update domain_entities.md and system_roadmap.md in Flutter projects whenever prototype data, domain vocabulary, or project scope changes occur. This rule ensures these foundation documentation files reflect new scope prior to code implementation to avoid integration surprises.