feat/p02-dual-connections #3

已合并
YokiiroBW 已将来自 feat/p02-dual-connections 的 31 提交合并入 main 2026-07-21 14:40:19 +08:00
共有 2 个文件被更改,包括 35 次插入 和 0 次删除
仅显示提交 4c238dd4eb 的更改 - 显示所有提交

查看文件

@ -129,3 +129,10 @@ Still not claimed complete: automatic startup activation, real Tauri multi-windo
- Extended chat send requests with optional configId and attachments; the existing dual-slot isolation remains the authority.
- Updated ChatPanel with model selection, attachment staging, upload state, and clean WebChat-style text labels.
- Validation: Rust workspace tests 60 passed; Vitest 6/6 passed; TypeScript, ESLint, cargo check, and Vite build passed.
## 2026-07-20: live chat extensibility probe
- Both supplied containers returned status=ok for chat sessions and config discovery.
- Container 1 accepted a minimal multipart upload and returned attachment_id, filename, and type.
- No chat message or configuration mutation was performed. Full multimodal rendering remains reserved for an explicit send-message acceptance test.

查看文件

@ -0,0 +1,28 @@
# AstrBot chat extensibility probe
Date: 2026-07-20
## Scope
Non-destructive connectivity and response-shape verification for the two supplied AstrBot test containers. API keys and complete response bodies are intentionally omitted. No chat message was sent and no configuration was changed.
## Results
| Target | Sessions | Configs | File upload |
| --- | --- | --- | --- |
| Container 1 (:26285) | status=ok; existing webchat session returned | status=ok; one default config | POST /api/v1/file returned status=ok and an attachment_id |
| Container 2 (:26385) | status=ok; no sessions for the probe username | status=ok; config list returned | not uploaded during this probe |
## Upload response shape
The first container returned an envelope with these data keys:
- attachment_id
- filename
- type
The adapter already accepts attachment_id and preserves the client-side filename, MIME type, and byte size in normalized attachment metadata.
## Implementation consequence
The current capability and upload IPC contract matches the observed response shape. Model selection is represented by AstrBot config IDs; the first container exposes the default config and the second exposes a named workflow config. End-to-end image rendering and model behavior still require a real chat send with a user-approved test message.