[httpsphl]

D5 of Desktop Use (spec 24.8, 24.10, 24.12).

What changes

• Every desktop grant (see or use) has a While you are away switch, off from the start. Turning it on opens a risks screen: the bot sees everything open in the app, it can make mistakes, text in an app can trick it, nobody watches live, and what is never granted. Turn on stays disabled until I understand the risks is checked. Turning it off is immediate.
• desktop.setOptions {grantId, unattended, acceptedRisks}. The daemon refuses to turn it on without acceptedRisks: true and saves accepted_risks_at.
• Presence rule (5 minutes idle, or the app closed) now runs after the window is known. With the owner away, a window passes only when a grant with the option covers it at the needed level. Nobody is asked while the owner is away. desktop_windows shows only those grants' titles, and refuses if there are none.
• Return notice: each use while away is kept in memory, one line per bot and app (DesktopAwayUse), and sent as desktop.away. The app shows "Scout used Excel while you were away" above the main pane. See in the chat opens the chat at the item where it began. Got it calls desktop.dismissAway.
• With the screen locked, the real mouse and keyboard already refuse (D4). UI Automation goes on if Windows allows it.

Tests

• Store: the option keeps accepted_risks_at.
• Daemon unit test for the away list.
• Integration test tests/desktop_away.rs with the real test window. With the owner away an hour: refused without the option; setOptions refused without accepted risks; with them, windows and look work; desktop.away arrives; acting still needs a use grant and nobody is asked; the owner dismisses the notice.
• App: the risks dialog gating, the notice and its link, and pt-BR words.

Manual, with real Claude / Windows

• Lock the screen (Win+L) with a bot running a routine on an app granted with the option on. Check that desktop_look and an accessibility click still work. Check that desktop_press says the screen is locked. Record the result in spec 19.
• Come back and see the notice above the chat; See in the chat lands where the bot started.