Repository navigation
Preserve existing report outputs and release the fix as v0.2.3 - #33
Merged
Merged
Conversation
dev-belly
marked this pull request as ready for review
November 4, 2026 15:11
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.
Repeating a scalar or rolling report command at the same output silently replaced five existing evidence/report files and its manifest. Require a new or empty report destination, reject nonempty/file/link targets before writing, and create every member exclusively so a file arriving after preflight is preserved. Existing empty-directory use remains supported; an I/O interruption can leave partial output, so retries use a fresh directory.
Ship the fix in v0.2.3. The clean-wheel gate runs all six demo/JSON/CSV routes against an existing report, a directory containing review notes and an ordinary file: all 18 calls must exit 2 without success JSON or changed bytes. Release preparation/verification require this evidence, including regressions that rehash false claims. Current installation/replay docs use the new version, the scalar CI report gets its own subdirectory, and the twelve saved scalar/rolling files remain byte-identical. Temporal algorithms, input contracts, bundle engine IDs and optional downstream pins do not change.
Validation: 159 local tests pass, including six new destination regressions and the release-gate regression. Targeted lint, whitespace checks, library/notebook examples, 71 browser-core comparisons and 68 exported-case replays pass. A regular wheel built from the sdist passes the complete clean-environment checker and all 18 preservation cases. Both six-file saved bundles replay exactly. All ten Linux/Windows/pandas/Chrome PR CI jobs pass. Publication uses the exact successful main-run artifacts.