Repository navigation
·
266 commits
to main
since this release
- Wire format 7 and field list 14 are unchanged from 0.5.4 (
CAPTURE_VERSION35); the pool reads formats 3 to 7. oars pool deposit --send-allsends, in order and one batch at a time, every batch thatoars pool outboxprinted and that is unchanged (the covenant rule of--send; a batch never printed or changed is skipped and counted; not with--send). A failed batch stops the run with the sent, skipped, failed, and left counts and a non-zero exit, a 429 or a 5xx is tried up to three times, and running it again sends only whatsent.logdoes not hold.oars pool depositbuilds the outbox a hundred sessions at a time, andoars pool outboxand--send-allread one batch at a time, so a history of thousands of sessions builds and sends in a small heap (a 7,000-session build under a 160 MB setting; thesessions depositcapture still reads the whole store once at its end, andoars pool outbox --jsonstill builds one document, so it is not memory-bounded).oars pool joinis now the whole first deposit in one command: sign-in, the region question, an exclusion term file made for you to edit, the batch, what it holds, the covenant screen with the phrase you type yourself, and the first send. A second run continues at the first step not done,--harness-versionis optional (given, it fetches after the send), and--plan --jsonlists each step, its state, andneeds_personfor the covenant phrase and the raw prompt, and for the region question and the term file while unanswered, changing nothing. Each step leaves ajoin-steptelemetry event of closed words (docs/telemetry.md).oars card,oars club show,oars board, and the Friday line now point the ashore tooars pool join.oars pool invitemakes one vouch code (a founding or standing account, three open at most) and prints it once with the join line;oars pool join --invite <code>redeems it after sign-in;oars boardandoars club showprint a founding member's crew number beside the nickname, and the share card's depositor line addsfounding crew #Nonceinviteorjoinhas learned it.oars pool depositreads each chunk of sessions by the byte offsets its one scan of the log recorded, instead of streaming every log line once per chunk: the 7,000-session build ran in 219 s against 261 s, with the same batches. A row appended to the log during the run is never read through the scan, and if the log is replaced during the run (a compaction), the build reads it by streaming, as before, so nothing is skipped.- Internal, no behavior change:
oars sessions refresh(and the refresh a deposit ends with) now scans the log once, then reads and folds the store a hundred sessions at a time, so it no longer holds every tool call and prompt of the history: over 7,000 sessions it finishes in 28 s under a 256 MB heap setting (it ran out of memory at 160 MB), and every derived file is byte-identical at any run size. - Internal, no behavior change: the
refreshderivations (cells, increments, fit reads, consequences, and reversions) now fold run by run over a log scan that keeps each session's parents and capture versions, with arefreshpintest that pins every derived file's bytes;oars sessions refreshoutput is byte-identical. - The weekly
harness-readersworkflow now fails when a harness's latest npm release is past the version its fixture was modeled on (versions.json, default a different minor), and a localshape.mjstool lists the field names a real session file has that a fixture lacks, with no values. The Claude Code and Codex fixtures are refreshed to 2.1.322 and 0.167.0, including a Codex code-mode cell.