docs(mobile-client): add information about automatic status re-checks

- Include details about AppStatusService and its background configuration fetching
- Explain the behavior of silent checks and status page transitions
- Highlight the near real-time reaction to server-side changes

Author: fulleni

src/content/docs/mobile-client/architecture/routing.mdx

@@ -40,6 +40,12 @@ This flow handles users who already have an active session.
 
 This two-path system correctly prioritizes authentication and then uses that session to securely fetch critical app configuration.
 
+<Aside title="Automatic Status Re-checks" icon="sync">
+The application includes an `AppStatusService` that automatically re-fetches the remote configuration in the background. This service triggers a check when the app is resumed from the background or at a periodic interval (e.g., every 15 minutes).
+
+These background fetches are "silent" (`isBackgroundCheck: true`), meaning they do not show a loading screen. If the new configuration indicates a critical status (like maintenance mode), the app will immediately transition to the appropriate status page. This ensures the app can react to server-side changes in near real-time without disrupting the user unless absolutely necessary.
+</Aside>
+
 ## GoRouter Implementation Details
 
 Once the startup flow is complete and the router is active, `go_router` manages all in-app navigation.