Repository navigation
PITBridge v0.2.3
Scalar and rolling report writers now preserve existing evidence. Previously,
repeating a successful report command at the same --out could replace five
existing data/report files and the manifest. Report commands now require a new
or empty directory and reject nonempty directories, ordinary-file destinations
and directory symlinks with exit 2 and no success JSON.
python -m pip install "https://github.com/dev-belly/PITBridge/releases/download/v0.2.3/pitbridge-0.2.3-py3-none-any.whl"
python -m pitbridge demo --out outputs/scalar-first
python -m pitbridge verify --out outputs/scalar-first
# A repeat at outputs/scalar-first is rejected; use another directory:
python -m pitbridge demo --out outputs/scalar-second
python -m pitbridge verify --out outputs/scalar-secondUse Python 3.11+ in a virtual environment. The rule applies to demo, build,
rolling-demo and aggregate, for both JSON and CSV inputs, as well as the
two library writers. Existing empty directories remain supported. A member
file appearing after preflight is created exclusively and therefore preserved
on collision. After an I/O interruption, inspect any partial files and retry
with a fresh output directory.
The checked-wheel gate runs all six demo/JSON/CSV routes against existing
reports, unrelated directories and ordinary files outside the source tree.
All 18 rejections must leave destination bytes unchanged. Release preparation
and verification require this evidence, alongside the existing input-starter,
timestamp, independent-replay and benchmark checks. A rehashed false protection
claim still fails validation.
Temporal algorithms, numeric and input contracts, synthetic demonstration
data, saved scalar/rolling formats and existing report bytes are unchanged.
The package version does not relabel legacy bundle engine IDs. v0.2.2 and its
original assets remain available. Installation needs network access; report
generation and independent replay then run offline without runtime dependencies.