Releases: tiramitree/benchhandoff
Release list
BenchHandoff v0.5.0
BenchHandoff v0.5.0 is a GitHub-only early release of the fail-closed,
resumable experiment-recovery CLI and its optional source-only Kubernetes
AgentRun controller.
Highlights:
- Windows recovery now uses extended-length paths for deterministic quarantine
destinations beyond the legacyMAX_PATHboundary. - The reference controller uses exactly two manager replicas and one
pre-created namespaced Lease. Its separate leader-election Role is restricted
togetandupdateon that exact Lease. - Deterministic fake-client fault injection covers create success,
AlreadyExists, committed-response loss, and status-conflict convergence. - The pinned single-node kind gate separately covers one live-
starttakeover
and one terminal-resume/pending-status takeover. It requires the same
measured Job and Pod identities, the pre-existing passive manager acquiring
exactly the next Lease transition without a restart, restored business RBAC,
and one final Job and Pod for each ofstart,resume, andverify.
Exact public evidence:
- Release commit:
c9837dc78ef199a52c23df101285c1e4d27c01e3 - Main CI: https://github.com/tiramitree/benchhandoff/actions/runs/30472827326
- Main real-kind gate:
https://github.com/tiramitree/benchhandoff/actions/runs/30472840631 - Annotated-tag CI:
https://github.com/tiramitree/benchhandoff/actions/runs/30473618474 - Annotated-tag real-kind gate:
https://github.com/tiramitree/benchhandoff/actions/runs/30473617993
The wheel, source distribution, and distribution checksum are the unchanged
bytes built and tested by the annotated-tag CI. The schema-2 takeover record
and its distinct checksum are the privacy-gated bytes from the annotated-tag
real-kind run. No controller image, Helm chart, package-registry publication,
production support, independent review, external use, or adoption is claimed.
This remains a maintainer-controlled, synthetic, fixed single-node experiment
with the API server and storage available. It does not establish strict
fencing, network-partition safety, arbitrary Pod recovery, multi-node or
multi-cluster behavior, exactly-once execution, production high availability,
performance, external adoption, or recruiting outcomes.
Development and documentation were AI-assisted. The claims above are limited
to the linked source revision, automated checks, released artifacts, and stated
boundaries.
BenchHandoff v0.4.0
BenchHandoff v0.4.0 introduces an experimental Kubernetes AgentRun control plane.
Highlights:
control.benchhandoff.dev/v1alpha1AgentRunCRD- immutable execution specifications and write-once resume approval
- a Go controller binding start, resume, and verify Jobs to registered identities
- a bounded, path-free termination-message protocol
- a distinct fresh verification Job before success
- hardened non-root runner Job defaults
- pinned disposable kind coverage for failure, approval, resume, verification, restart/adoption, drift, duplicate-Pod, and race cases
The controller remains experimental. It does not provide high availability, leader election, storage fencing, exactly-once execution, a production operator, or a supported deployment package.
Rebuilt release provenance
The wheel, sdist, and SHA256SUMS attached here were downloaded without rebuilding from the successful workflow_dispatch CI run executed at the privacy-rewritten v0.4.0 tag.
- Distribution CI run: https://github.com/tiramitree/benchhandoff/actions/runs/30452348357
- AgentRun kind E2E run: https://github.com/tiramitree/benchhandoff/actions/runs/30452351753
- Wheel SHA-256:
3ab2c208d60d535bf4e21bbfc8fa950a8ce0f5e2db09232787cf6cb3454c72a1 - sdist SHA-256:
3c488eb7b26acbb29828e75e52b1eef7f0374443cbc493dd50291553ca3af628 SHA256SUMSSHA-256:1bc5c87b5f6e56f61faca50f83a28f17d7858e98801f5fdc0c87f38defc9ff5a
Evidence boundary
All validation, including the single-node kind exercise, is maintainer-operated synthetic evidence. It is not production validation, independent reproduction, third-party review, performance evidence, external adoption, or a support commitment. There are 0 accepted external-evidence records. This GitHub Release is not a PyPI publication.
BenchHandoff v0.3.0
BenchHandoff v0.3.0 adds bounded closed-world workspace integrity checks while retaining version 1 and version 2 compatibility.
Highlights:
- suite and evidence schema version 3
- one dedicated
workspace.rootand a separately reviewed manifest snapshot-workspaceandinspect-workspace- bounded, double-scanned topology and ordinary-file byte observations
- before, after, and recovered workspace bindings
- workspace-root writer locking
- atomic no-replace quarantine moves on supported platforms
Workspace checks occur only at registered protocol boundaries. They are not continuous monitoring, a sandbox, or a hostile-writer guarantee.
Rebuilt release provenance
The wheel, sdist, and SHA256SUMS attached here were downloaded without rebuilding from the successful workflow_dispatch CI run executed at the privacy-rewritten v0.3.0 tag.
- CI run: https://github.com/tiramitree/benchhandoff/actions/runs/30452344356
- Wheel SHA-256:
09dad748259c7889f9c232e6cf204c09113ca81ddc7e6acc9647df109c9b96b2 - sdist SHA-256:
5d79b880e92ba579baa913626167089c034d3059de50b5f509a46b42d4f426a3 SHA256SUMSSHA-256:11a005e5737e1a4f2df9da76762d864003732cad266958f99f8a265eb0fe7b31
Evidence boundary
All validation is maintainer-operated synthetic evidence. It is not production validation, independent reproduction, third-party review, hostile-writer safety, external adoption, or a support commitment. There are 0 accepted external-evidence records. This GitHub Release is not a PyPI publication.
BenchHandoff v0.2.0
BenchHandoff v0.2.0 adds stricter execution-context and process-lifecycle controls while retaining version 1 compatibility.
Highlights:
- suite and evidence schema version 2
- byte-verified execution-context descriptors declared as seed inputs
- executable-content and normalized-path identity binding
- a minimal, non-inheriting launch environment
- Windows Job Object and Linux process-group lifecycle controls
- synthetic child-to-grandchild cleanup and residual-process checks
These controls are not a sandbox, VM snapshot, package inventory, or remote-attestation mechanism.
Rebuilt release provenance
The wheel, sdist, and SHA256SUMS attached here were downloaded without rebuilding from the successful workflow_dispatch CI run executed at the privacy-rewritten v0.2.0 tag.
- CI run: https://github.com/tiramitree/benchhandoff/actions/runs/30452340566
- Wheel SHA-256:
e4f84b97b7b34e78d0f43687f4ff70245bdb929faa2fbd4dfa74912791590ebc - sdist SHA-256:
92553a90ba4297e7a2ac4531d721b93bc8701c10b56ce1b52632cca2c2377d36 SHA256SUMSSHA-256:3a581eb22132682e0e28e9174e2200a17d6fc1128472b569f45c70dd39120c7f
Evidence boundary
All validation is maintainer-operated synthetic evidence. It is not production reliability, independent reproduction, external use, third-party review, or a support commitment. There are 0 accepted external-evidence records. This GitHub Release is not a PyPI publication.
BenchHandoff v0.1.0
BenchHandoff v0.1.0 introduces a local, fail-closed harness for sequential task suites.
Highlights:
start,resume,inspect, andverifyCLI workflows- versioned plans, state, event chains, and final evidence bundles
- partial-output quarantine and suffix-only recovery
- evidence-bound resume decisions and cooperative local writer locking
- canonical synthetic recovery examples and machine-readable evidence
- Apache-2.0 licensed Python package
Rebuilt release provenance
The wheel, sdist, and SHA256SUMS attached here were downloaded without rebuilding from the successful workflow_dispatch CI run executed at the privacy-rewritten v0.1.0 tag.
- CI run: https://github.com/tiramitree/benchhandoff/actions/runs/30452336351
- Wheel SHA-256:
ca52a5dca1ecc7d05e7fbd3b540f7988f152295dafbd796d1c68771d0bb6ed1f - sdist SHA-256:
8657f063c3e5fc75cdfc255b70b5fcb2518720019053145d9b03ef6785fdaae4 SHA256SUMSSHA-256:53070194960b39b00a41e0159eb976998dcca77a5700a3db205039721af94e3b
Evidence boundary
All validation is maintainer-operated synthetic evidence. It is not production validation, independent reproduction, third-party review, external adoption, or a support commitment. There are 0 accepted external-evidence records. This GitHub Release is not a PyPI publication.