| Ticket Hash: | 21dfd164d65a9b3ad394be4f50a0a243b3b41ae8 | ||
| Title: | JSON management API over /ext/ for remote clients (threads, posts, tickets, diffs, search, session-status) | ||
| Status: | Active | Type: | feature |
| Severity: | Normal | Priority: | medium |
| Subsystem: | api | Resolution: | |
| Last Modified: |
2026-09-20 14:42:39 51.7 days ago |
Created: |
2026-07-07 04:12:21 127.2 days ago |
| Version Found In: | |||
| Description: | ||||
| Prerequisite for the Stone remote-client (Stone repo: docs/design/ollama-codex-client.md; Stone EPIC db0e9e21d0). A good remote client should act on STRUCTURED data, not scraped HTML. Provide a JSON management API over the existing /ext/ surface: forum threads + posts, tickets, diffs/file contents, semantic/lexical search results, and session status. Reads should be derivable from the repo DB (the client also holds a full Fossil clone, so this is a management/status layer, not the primary read path — native DB + HTTP sync stay primary). Auth = the logged-in Fossil user (capability-gated). Relates to the portable-agent-toolset direction (beb51d8). Acceptance: a client can enumerate sessions/threads/posts/tickets and read a diff + search results as JSON, authenticated by a normal user login. | ||||
| User Comments: | ||||
added on 2026-08-16 19:12:15:
SCOPE ADDITION (Stone design, 2026-08-16 — see stone wiki 'Stone Remote Operations and Speech Design'): the management API must include POST /ext/gpcr/speak {utterance, file, gen} -> parses the closed grammar SERVER-side, applies with validity+parse gates, returns applied-op confirmation or the rejection hint verbatim; plus the block-index endpoint (gpcr ops index output) that Stone uses to refresh its speech-recognition vocabulary bias list. Stone is the first consumer of this API; sequencing on the stone wiki page puts this ticket + 0b016fe2b3 + d1b4145554 as the server half preceding all Stone client work.
| ||||