perf(runtime): append ordinary run facts incrementally - #168
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
FileRunStore.append()callssyncplus atomic rename path for critical commits so a failed durability barrier cannot publish an unacknowledged FactVerification
npx vitest run --project coremind-runtime— 800 passed, 2 skippedpython -X utf8 -m unittest discover -s python/tests -p "test_node_parity.py"— 6 passednpm run check— lint, all workspace typechecks, module contracts, docs pairing, and 466-file Markdown audit passedCritical commits intentionally retain copy-on-write publication because in-place append cannot preserve the existing guarantee that a failed sync leaves an unacknowledged Fact unpublished without adding a WAL or changing the persistence format.
Closes #161