Fixtures ai-doc — transcribed, not recorded
These files were not recorded by this package from a live server. They are the JSON examples printed in the AI
workstream's contract (docs/next/API-NEXT-AI.md of the backend, branch next-ai, examples dated 2026-11-19), copied
verbatim (byte for byte, extracted by script) so that the Swift models of the AI routes decode at least what that
document shows. The foundation scratch server used for the other groups does not have these routes (see the recorded
404 answers in ../ai/), and no model call was ever made to produce a fixture.
- One file per example;
_index.jsonhas the same format as the recorded groups, plussource(the section of the document),sse: truewhen the file is the payload of onedata:line of an event stream, andshortenedStrings: truewhen the document's author abbreviated a string value with…(chat-page-done,chat-none-meta,chat-none-done): the JSON structure is complete, some ids / excerpts are not real values. - Examples whose JSON was cut with
…in the document (not parseable as printed) were skipped: theclaude-haiku-5-5model row, thescope: "selection"meta / done events, thedoneevent of a Markdown action, the top-level answer ofGET /api/ai/models(itsprovidersarray and the first twocreatorsare kept asmodels-providers.jsonandmodels-creators-first-two.json). - A model verified only against these files is not verified against a server. Re-record them for real
(
Scripts/recorders/ai.py) once a scratch server with the AI workstream is available.