diff --git a/docs/progress.md b/docs/progress.md index 80491a3..f95d615 100644 --- a/docs/progress.md +++ b/docs/progress.md @@ -136,3 +136,10 @@ Still not claimed complete: automatic startup activation, real Tauri multi-windo - 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. + + +## 2026-07-20: live end-to-end chat acceptance + +- First test container accepted text plus config selection and streamed a complete response with no error frame. +- The same session accepted text plus config selection plus the uploaded attachment and streamed a complete response with no error frame. +- This validates the current model/config and attachment request contract against a real AstrBot instance. diff --git a/docs/reports/astrbot-chat-extensibility-probe-2026-07-20.md b/docs/reports/astrbot-chat-extensibility-probe-2026-07-20.md index 2c490a9..999d9c9 100644 --- a/docs/reports/astrbot-chat-extensibility-probe-2026-07-20.md +++ b/docs/reports/astrbot-chat-extensibility-probe-2026-07-20.md @@ -26,3 +26,13 @@ The adapter already accepts attachment_id and preserves the client-side filename ## 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. + + +## End-to-end send test + +Using the first container and the default config ID, two request-scoped SSE sends were completed: + +- Text plus config selection: HTTP 200; session_id, user_message_saved, 4 plain frames, complete; no error frame. +- Text plus config selection plus the previously uploaded attachment: HTTP 200; session_id, user_message_saved, 5 plain frames, complete; no error frame. + +This confirms the current configId and attachment request shape is accepted by the tested AstrBot instance. The test messages were intentionally limited to interface confirmation and did not request tools or configuration changes.