Skip to content

Say when transcript drops and block appends run on a copy - #2203

Merged
fazxes merged 1 commit into
mainfrom
fazxes/fix-transcript-copy-comments
Nov 22, 2026
Merged

fazxes merged 1 commit into
mainfrom
fazxes/fix-transcript-copy-comments

Conversation

@fazxes

@fazxes fazxes commented Nov 22, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • The doc comments on dropEntriesAtomic, dropEntries, appendAssistantBlockInPlace, and appendAssistantBlockAtomic now say that the copy-and-commit path applies to a runtime with a transcript_commit_state, which is the only path today's callers take. Comments only; no behavior changes.

Follow-up to #2171 and #2187, from their ship-gate notes.

The factory check reports transcript_paint and frozen_prefix as reached, because store.zig changed. Each passed one short round (python3 -m scripts.fuzz_nightly run --target <name> --budget-seconds 60) on this head with no crash, failed law, or hang.

- The doc comments on the transcript drop and the table, code-block, and rule appends now say that the copy-and-commit path applies to a runtime with a `transcript_commit_state`. No behavior changes.
@fazxes fazxes added the type: maintenance Changes internal tooling, dependencies, CI, or implementation structure label Nov 22, 2026
@fazxes
fazxes marked this pull request as ready for review November 22, 2026 20:06
@fazxes
fazxes merged commit e95a479 into main Nov 22, 2026
54 of 61 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: maintenance Changes internal tooling, dependencies, CI, or implementation structure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant