4 Commits

Include renames

Author	SHA1	Message	Date
HomerandClaude Opus 5.5	ecae6247fd	Harness spec 3.1.0-draft: the prefix stays still ... Measured on 2026-11-05 against a local model's prompt cache: a harness that rebuilds its system prompt for every request re-reads the whole session whenever any part changes (a date at midnight: 16,912 tokens, 99 % -> 0 % cached, 139 s). context.md §10: the system prompt is made once per session and resent; no clock in it; mid-session changes go as a <session-note> on the next user message (loop.json context.note); the tool list is fixed for the session, a requires that comes and goes answers unavailable instead (plan_submit gains requires: plan); §7: the compaction summary is the next turn of the same conversation, not a separate request with a pasted transcript; cached tokens are recorded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-05 12:37:25 +00:00
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	e7300b26d5	Harness spec 3.0.0-draft: context ids in the cases are hex; several files in one patch ... conformance/context.json named results #g001…#k001, which are not the lowercase hex context.md requires (an implementation that finds a result's id at the head of the result by that rule cannot see them); they are #1001…#5001 now, with the same answers. Its `about` names the CLI's module, session/results.ts. context.md §5 says what it left open: a deleted file's bracket, and an apply_patch over several files — the id alone, then each file in its own bracket with its change, in the patch's order; a tool's note after the diff. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-27 20:09:22 +00:00
HomerandClaude Opus 5.5	6ca43b6908	Harness spec 3.0.0-draft: context hygiene, at insert time only ... context.md and loop.json `context`: every result has an id, a read carries its lines and content hash, an unchanged re-read (or a range inside one) is a stub, large output keeps head and tail with the elided line, recall shows any stored result, edits answer with their diff, a repeated listing or search with the same result is a stub, and compaction adds a table of reads and empties the dedupe table. Nothing already sent is ever rewritten. Conformance area context. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-27 18:52:24 +00:00