- Expose normalized AstrBot capability discovery through Rust-owned IPC.
- Expose model/provider configuration options as a slot-scoped selector; keep the server default when discovery is unavailable.
- Add a bounded 16 MiB multipart upload boundary at /api/v1/file; React receives only normalized attachment metadata.
- Carry optional configId and attachment metadata through the send request without exposing credentials or raw HTTP clients.
- Keep attachment wire mapping isolated in the AstrBot adapter so the internal chat runtime remains transport-neutral.
Acceptance: the chat panel can discover model options, stage uploaded files, and submit a normalized message request; real server response-shape compatibility remains verified by the supplied AstrBot containers before claiming end-to-end multimodal support.
## 2026-07-21: implementation status for the 13-item roadmap
The roadmap items are implemented locally as follows:
1. Startup auto-connect: done in src-tauri/src/networking/commands.rs and src-tauri/src/lib.rs.
2. Credential rotation and JWT: done in src-tauri/src/credentials, src-tauri/src/auth.rs, and CredentialEnrollmentCard.tsx.
3. Server identity protection: done through expected_server_instance_id validation in the Rust clients.
4. Quick chat: done in src-tauri/src/quick_window.rs and the Tauri window controller.
5. Tray and status bubble: done in src-tauri/src/lib.rs and src/features/chat/StatusBubble.tsx.
6. Pet state and assets: done in src/features/pet/DesktopPetView.tsx and src/features/pet/assets.
7. Multi-monitor/game policy: done in src-tauri/src/pet.rs and src-tauri/src/windows.
8. Voice interaction: done as a Web Speech MVP in src/features/chat/ChatPanel.tsx.
9. Proactive messages: done through normalized runtime events and unread persistence.
10. Chat reliability: done with session-scoped history merge and duplicate regression coverage.
11. Diagnostics and log redaction: done in src-tauri/src/diagnostics and src-tauri/src/logging.rs.
12. Release executable and installer: done for unsigned local artifacts under target/release.
13. Final acceptance: local gate is ready; external release acceptance is pending the prerequisites below.
The following are deliberately not marked complete: HTTPS certificate pinning, signed updater delivery, and real dual-server soak. They require external infrastructure or release secrets and must not be faked in local development.