salvage 2026-11-06: uncommitted work from src/mosaic-stack-rocko-129-r2 (disk cleanup #824)
This commit is contained in:
1 parent
d2df4d934a
commit
5d89e5e233
15 files changed
+1065
-15
No files matched your search
@@ -665,3 +665,29 @@ safe integer range are decimal strings in JSON. Settings has the same
|
||||
read-only Token usage section. Counts are a best reading, not proof: the
|
||||
session can edit its own transcript. This command changes no setting and
|
||||
performs no token-limit enforcement.
|
||||
|
||||
### Console Chat (row 129, #1623)
|
||||
|
||||
The Console's **Chat** section uses `#/chat`, `#/chat/projects/UUID` and
|
||||
`#/chat/threads/UUID`. Create and name a project and its threads, then send a
|
||||
message in that thread's conversation. Names are creation-only. The project
|
||||
catalog is business-wide; thread lists and histories belong to the current
|
||||
human. This is separate from the Board's seat reply route.
|
||||
|
||||
`GET/POST /api/chat/projects` lists/creates projects; `GET/POST /api/chat/threads`
|
||||
lists/creates threads (`project=UUID` optionally filters the GET).
|
||||
`GET /api/chat/threads/UUID/messages?limit=100&after=UUID` pages history forward;
|
||||
`POST` on that messages route sends `{body}` as a REQUEST.
|
||||
`POST /api/chat/threads/UUID/open` takes `{}` and explicitly resumes the assistant.
|
||||
GET never writes, opens a thread or marks messages delivered/read. No browser
|
||||
owner, tenant, proof or arbitrary bus verb is accepted. A same-business thread
|
||||
owned by someone else is 403 `thread-not-owned`; foreign/missing ids are 404.
|
||||
|
||||
The four chat POSTs use the existing signed-in `--send` boundary: named Host,
|
||||
one exact proxy user header, exact HTTPS Origin, same-origin Fetch Metadata,
|
||||
strict JSON and 16 KiB. Read-only mode disables them. Bodies are inert text;
|
||||
drafts are memory-only per thread and cleared on sign-out. History starts
|
||||
oldest-first in pages of 100, with a 200-message display window. Sending does
|
||||
not claim an assistant answer; an uncertain receipt is never retried. Read the
|
||||
current list/history before trying again. Activation still needs Mos's separate
|
||||
window; changing these files does not authorize a live Console action.
|
||||
Reference in new issue
Block a user