StateFrame 0.4.33

StateFrame 0.4.33: safer concurrent access to the call-coverage index.

Fixes

• When several threads worked on the same run, a request could pick up a call-coverage index that another thread had not finished connecting to the run's journal. The index is now fully connected before anything else can see it, and reconnecting an index that is already connected costs no extra work.
• A coverage snapshot now gives one consistent view of all its fields; code that needs several fields to agree should read the snapshot.

Measured replay time is unchanged within noise (+1.3% on a 3-minute replay). Requests sent to the model are unchanged.

Known issues (fixes planned)

• In-place runs and exported patches can change the line endings or byte-order mark of untouched text files in the edit scope (see KNOWN_LIMITATIONS). A fix is being tested now.
• Linux: checks that run Go or Node programs fail under StateFrame's check memory limit. macOS is not affected.
• The first request of a run can differ between runs in one optional orientation section, depending on local cache state.
• On endpoints without an exact tokenizer, very dense content can be underestimated and push a request past the context limit.