Svet Crnil Pomoc 2.0.5 / 20005

Active support: a bounded, non-waking screen lock works while Settings or another
app is foreground. Requires fresh (maximum 45 seconds) authenticated active/online
paid+fiscal status, local connection consent, an authorized connected native client
and running capture. Releases on disconnect, cancellation, terminal status,
network failure, capture stop, service destruction and Activity finish. Does not
change Android screen timeout or bypass the lock screen. The existing WAKE_LOCK
permission is used; no new permissions or fabricated input events are added.
SCREEN_BRIGHT_WAKE_LOCK is deprecated but necessary here because an Activity
window flag cannot retain the screen while assisting in another app. Manual power
off is respected. Actual OEM power-management behavior requires device testing.

Authorized incoming Android chat selects the sender and opens the Chat tab after
inserting the message, without focusing the keyboard. If backgrounded, a high
importance notification opens the existing Activity; Android notification
permission/channel preferences are respected. No forced background Activity launch.

Active controller polling: one authenticated heartbeat/status response rather
than status plus heartbeat; poll period 5 seconds instead of 15. Resume and payment
flows retain their checks. Worker action-begin/checkpoint/fence gates unchanged.
No measured claim about AI response speed or end-to-end remote latency.

Regression surface versus 2.0.4:
- svetcrnil_commercial_api.dart: fresh-status screen lease and active poll path.
- svetcrnil_commercial_page.dart: bridge lease on support/native state and dispose;
  explain active screen/chat behavior to customer.
- home_page.dart + chat_model.dart: incoming authorized Android chat visibility.
- MainActivity.kt: lifecycle visibility and two feature-specific bridge handlers.
- MainService.kt: release screen lock at capture stop/service destruction.
- New SvetCrnilSessionExperience.kt: bounded lock + chat notification.
- commercial_contract_test.dart: regression coverage; packaging version metadata.
Desktop, payment routes, server settings, Rust native libraries, stored identity,
release signing identity and Android permission dialogs are unchanged.

Verification: contract tests, Flutter analysis of changed Dart files, signed APK
build and certificate/package/native-library checks. End-to-end screen timeout,
background chat, disconnect and manual lock still need a test on the Xiaomi.
