Rule: MUST use whenever the scope matches this purpose: Apply the route workflow whenever Flutter routing files are edited.
Edits under flutter-app/lib/**/routes/** must follow the Route Workflow:
foundation_documentation/policies/scope_subscope_governance.md before defining ownership.EnvironmentType, main scope, subscope when applicable).screens/tenant_app.md, route sections) accordingly.app_router.gr.dart) for required non-URL args and classify each as URL-Hydratable or Internal-Only with explicit fallback behavior.Cold Entry vs Warm Entry) and ensure predecessor-preserving warm flows commit real router history before any interruption/boundary logic resolves.success, cancel/dismiss, and no-history outcomes. Visible back and system/device back must converge semantically.Routing governs navigation and domain hydration. The workflow preserves RouteModelResolver discipline and documentation parity.
Workflow reference: delphi-ai/workflows/flutter/create-route-method.md. If a route starts elsewhere (e.g., doc-first updates), the glob serves as a safety net for code edits.