AstrBot-Desktop/src-tauri
YokiiroBW 7aead6fa48
一些检测仍在等待运行
ci / Portable quality checks (push) Waiting to run
ci / Windows Tauri build (push) Waiting to run
feat(policy): gate screen reading behind consent, a rate limit, and a switch
implementation-queue.md:129 requires an authorization prompt, a frequency
limit, and a privacy switch to exist before screenshots or window
summaries are wired to anything. None of the three existed anywhere in
the repository, so this is them, plus ADR-0008 recording what the
authoritative documents actually permit.

The ADR corrects a mis-reading that would have decided the feature the
wrong way. 01_Architecture_Design.md:250-261 is titled 「不应放在前端的
能力」, so the 「原始截图捕获」 at :259 forbids screenshot capture in
React — it is not a product-level ban, which is how an earlier audit read
it before concluding screen reading was out of scope. The product
affirmatively permits 「用户授权的单次窗口截图」 (:739) and, for phase 7,
「手动和低频截图」 (:1424). What it does exclude is 「实时全双工语音」,
「唤醒词」 and 「高频视频分析」 (:1349-1351).

The module owns all three gates so none of them depends on the frontend
being correct. Reading takes a closure, so the window handle never leaves
the module and there is no accessor that skips the switch, the session,
the expiry check, or the budget. The switch defaults to off and clearing
it drops live sessions, so flipping it mid-capture stops the next read
rather than only preventing new authorizations. `now` is a parameter to
the budget rather than read inside it, which is what makes the interval
testable without sleeping.

Two decisions worth naming. The pixel interval defaults to two seconds
with a 500ms floor no caller can lower — three orders of magnitude away
from a video frame rate, because high-frequency video analysis is out of
scope and what phase 7 asks for is manual, low-frequency capture. And a
session cannot be bound to the operations slot at all, refused at
creation rather than at each read, because :1077 says the operations slot
does not automatically receive game screenshots, window state, or game
events — and a session is exactly that automatic delivery. The slot rule
is a free function so it is asserted directly rather than through a live
window.

Also recorded, not worked around: capture.rs uses PrintWindow over GDI,
which does not capture a hardware-accelerated game surface. Game
companionship needs Windows.Graphics.Capture before it works on the case
it exists for, and a black frame delivered to the model would be worse
than an error.

Rust tests 101 -> 110.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 06:22:15 +08:00
..
capabilities fix(tauri): grant the window controls the permissions they call 2026-07-27 01:19:42 +08:00
icons feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
src feat(policy): gate screen reading behind consent, a rate limit, and a switch 2026-07-27 06:22:15 +08:00
tests fix(tauri): grant the window controls the permissions they call 2026-07-27 01:19:42 +08:00
build.rs feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
Cargo.toml feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
tauri.conf.json feat(chat): carry voice and other non-image attachments end to end 2026-07-27 06:16:55 +08:00