rule-flutter-flutter-route-workflow-glob

To enforce a consistent Flutter routing workflow, apply a formal route-workflow check whenever files under flutter-app/lib/**/routes/** are edited. This ensures governance, ownership references, and documentation parity across large navigation updates.

Route workflow governance in Flutter is a formal validation process for navigation edits that ensures route ownership, AutoRoute integration, and documentation parity. You need it when managing complex routing changes to maintain architectural consistency.

Yes, the Flutter route workflow check validates AutoRoute integration and regenerates contracts and documentation via the prescribed workflow. It ensures ownership references and module wiring are aligned during routing edits.

The best way to audit Flutter route ownership and boundary semantics is to run the route-method analyzer on edited routing files. It provides auditable outcomes, including route-entry mode and back semantics, and triggers evidence requirements for architectural changes.

The Flutter route workflow check requires evidence collection for architectural changes to ensure auditable outcomes and maintain documentation parity. This governance step validates that complex navigation modifications align with ownership and module wiring rules.