2 Commits

Include renames

Author	SHA1	Message	Date
HomerandClaude Opus 5.5	4ca6af12b1	Harness spec: stubs per request, the compaction table from the reads it covers ... context.md and loop.json `context`, spec 3.0.0-draft: - A stub names only a result in the request being built. A chat on the server sends no earlier reply's tool results, so a read in the next reply is answered in full there; the CLI, which resends every result, keeps stubbing across steps. Said for reads and for repeated listings alike. - The compaction table is drawn from the reads the summary covers: the full reads since the previous compaction in turns still in the history, whether or not the request still carries them. A turn taken back takes its reads with it. The CLI's dedupe table is exactly that set; a chat finds it in what it stored. - Ids are the result's number in the session, in hex, at least 4 digits (#0001); the examples and the prompt block now use such ids. - A bracket names the path as the call gave it; what identifies a file is its absolute path. Conformance `context`: a `reply` step (a request carrying none of the results so far) and a case for both rules. The CLI's runner keeps the history apart from the request; compactionTable takes the reads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-28 01:20:28 +00:00
HomerandClaude Opus 5.5	9f536d8345	Harness spec 3.0.0-draft: prompts, the link, and the changelog ... blocks/context.md tells the model about stubs and recall; blocks/workspace.md tells a chat's model its view. blocks/library.md and blocks/prototypes.md are the CLI's alone. acp.md: `instance` on session/new, a client-opened session runs on the chat's model and no other (the own-model notice is gone), capability `show` with `_lembas/show`, memory through the instance. README: the new fields and the 3.0.0 section. VERSION 3.0.0-draft. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-27 18:52:24 +00:00