docs(android): record Slint upgrade_in_event_loop Android risk

[xodapi]

Source

User-provided research, verified against upstream issue:

• upgrade_in_event_loop not always processed slint-ui/slint#5699 upgrade_in_event_loop not always processed
• State: open
• Labels: a:platform-android, priority:low, upstream
• Summary: on Android, closures queued through upgrade_in_event_loop may occasionally not run until a later upgrade_in_event_loop call wakes the queue.

What to do

Document this Android-specific Slint upstream risk in vimit docs and test guidance.

Acceptance Criteria

• docs/android.md mentions upgrade_in_event_loop not always processed slint-ui/slint#5699 as a known Android UI update risk.
• Android smoke-test guidance explicitly says to test rapid repeated updates for notification permission callback, Vimichi/pulse updates, and live chart refresh.
• Guidance says not to misdiagnose rare missed UI updates as vimit logic bugs before checking this upstream limitation.
• Guidance mentions possible future mitigation: retry/coalesced UI update with a short timeout, but does not implement it in this docs task.
• No code changes.

Checks

rg -n "5699|upgrade_in_event_loop|retry|Vimichi" docs/android.md
rg -n "C:\\|Users|API_KEY|ghp_|gho_|\.env" docs/android.md

[xodapi]

🤖 Начинаю выполнение. Агент: Codex

[xodapi]

✅ PR готов: #185. Smoke-test #179 также дополнен сценарием проверки slint-ui/slint#5699.