v0.1.0-beta.19

Public testing release for explicit artifact inventories.

• Full, initial and scoped checks omit the untracked contents of registered artifact directories from Git inventory output. Large SDK and state directories no longer consume that observation bound.
• Registration rechecks, project execution and migration decoding use the same literal exclusions as worktree checks. Ignored undeclared paths, literal or case neighbors, tracked changes and a file or symlink replacing a declared directory remain checked.
• Bound inventories override the four Git pathspec-mode variables explicitly and retain actual process environments and original output bytes. Raw complete-inventory APIs remain available.

Source: f8f28119096e9b50b2456024b473b252ea5f7cdd; tree: 0c51ad5c88c04a3e78be5f4edb1ed4b4f3c63e13. The source tree matches merged PR #96 and includes the implementation from PR #95. Native release run: https://github.com/ChronoAIProject/chrono-harness/actions/runs/36674223982

Native validation: 606 macOS arm64 tests and 601 Linux x86_64 tests across all 15 dedicated test projects. Each original build report retains 36 successful processes, 30 staged consumer destinations and 34 matching identity observations. The five-test difference consists of existing macOS filesystem-alias cases. Both platforms' original process hashes and all 30 binary hashes/sizes were verified.

Includes 30 binaries, the combined manifest, and each platform's original build report and manifest (35 assets). Combined manifest SHA-256: 857caddfba0ebfe0ec5780c7a31217b30ef0c65bff1b2b6152c8587bf439c731 (6252 bytes).

This is a prerelease. Complete effective-input closure, full host activation, deterministic local/CI parity and autonomous delivery remain unfinished. Installing binaries does not opt a host into new profiles.

v0.1.0-beta.18

Public testing release for explicitly registered, independent CI units.

• Scoped v3 collection accepts host-configured manifest/report byte limits and rejects invalid or legacy-profile settings. Omission preserves the existing 64 MiB per-file limit.
• Scoped v3 uses compact JSON while retaining original process bytes and report bindings, avoiding pretty-print expansion of large Git-facts evidence. Legacy profiles retain their serialization.
• Reports remain bound to the original candidate and configuration; changing a limit does not authorize reuse of old reports.

Source: b9665d1fa5b465d57ab84d5042712f30b297e882; tree: a9a53f85ea79797ef25a36e617bf7b44c3e20942. The source tree matches merged PR #91. Native release run: https://github.com/ChronoAIProject/chrono-harness/actions/runs/36666465494

Native validation: 601 macOS arm64 tests and 596 Linux x86_64 tests across all 15 dedicated test projects. Each original build report retains 36 successful processes, 30 staged consumer destinations and 34 matching identity observations. The five-test difference consists of existing macOS filesystem-alias cases. Both platforms' original process hashes and all 30 binary hashes/sizes were verified.

Includes 30 binaries, the combined manifest, and each platform's original build report and manifest (35 assets). Combined manifest SHA-256: 5a59cb11fe857a31bbde87dde46828ecae072527b3cae3ed254b8fdc607ae74c (6252 bytes).

This is a prerelease. Complete effective-input closure, full native governance activation, deterministic local/CI parity and autonomous delivery remain unfinished. Installing binaries does not opt a host into new profiles.

chrono-harness v0.1.0-beta.17

Public test release adding explicit native-platform selection for Git facts policies.

A scoped check or provider-v3 facts_config can name a chrono-git-configs/v1 selector with explicit macOS arm64 and Linux x86_64 entries. The reader binds the selector and selected policy to the candidate and checks their original bytes around every Git call. Missing platforms, nested selectors and substituted selection observations fail; direct-policy behavior is preserved. Hosts explicitly register the policies and dependencies while retaining the same canonical check command.

Source: 47a18da. Native build: https://github.com/ChronoAIProject/chrono-harness/actions/runs/36661720249

All fifteen dedicated test projects passed: 596 tests on macOS arm64 and 591 on Linux x86_64. Each original build report retains 36 successful processes, 30 consumer destinations and 34 matching identity observations. This release contains fifteen tools per platform, the combined manifest, and both original build reports and platform manifests.

Manifest SHA-256: 34e7286111e2d38e4254c40683310ff915292ff1be0a0ac2193ab9c0dfea5034.

This does not select the full runner root/initial host configuration or establish complete Git/OS/delegated/compiler/SDK input closure, full host activation, local/CI parity, autonomous delivery orchestration or model-to-Rust refinement. Different platform policies remain different inputs. Installing binaries does not adopt the new host policy.

chrono-harness v0.1.0-beta.16

Public test release of the registered-input and report-comparison increments since beta.15.

• Git fact acquisition can check explicitly registered files or absence before the version probe and before/after each Git call through the bound Reader. Drift fails while preserving any original subprocess result.
• Config v3 supports explicit consumer/input bindings and optional versioned input-domain coverage. The Cargo adapter supports v5 inventories for selected compiler, sysroot, backend, linker, SDK and build-script inputs.
• The report-parity command rejects incomplete effective inputs and compares the verdict-bearing fields of completed reports. Generated unit workflow adoption and the full judge chain with an empty DELTA have additional real consumers.
• The native release recipe explicitly selects all fifteen dedicated test projects and stages all fifteen tools into thirty declared consumer destinations.

Source: 5428183. Native build: https://github.com/ChronoAIProject/chrono-harness/actions/runs/36655069168

Native verification passed 588 tests on macOS arm64 and 583 on Linux x86_64 across all fifteen dedicated test projects. The difference is five existing macOS filesystem-alias tests. Each original build report retains 36 successful processes, thirty consumer destinations and 34 matching identity observations. The release includes both original build reports and per-platform manifests.

This test release does not establish complete Git/OS/delegated/compiler/SDK input closure, full host activation, universal or full-host local/CI parity, autonomous delivery orchestration, or model-to-Rust refinement. Existing schemas retain their declared meanings; hosts explicitly adopt new configuration contracts.

chrono-harness v0.1.0-beta.15

chrono-harness v0.1.0-beta.15

This public prerelease adds retained-intent continuation for interrupted or failed metadata rebinds.

• Adds chrono-worktree resume-rebind with an explicit continuation plan.
• Preserves the original intent, plan, result, visible work and backup identities.
• Resumes only an explicitly bound original allocation; completed results, identity drift, foreign ownership, locks and ambiguous partial state fail closed before effects.
• Covers real interruption at each governed Git phase and interruption of the continuation itself.
• Ships native macOS arm64 and Linux x86_64 binaries.

The continuation entry does not infer a lost index, reconcile unknown temporary files or locks, prove that the prior process stopped, or provide concurrent-writer/power-loss atomicity. It is released as a source and binary extension; host adoption remains explicit.

chrono-harness v0.1.0-beta.14

Public native prerelease for macOS arm64 and Linux x86_64. Hosts pin checksums and install selected tools under .chrono-harness/; installation requires no tracked binaries or Rust toolchain.

• Workflow v2/v3 historical profiles can explicitly declare method_replacements. Each row binds exact old/current owner, operation, tool and arguments, retains the operation ID and requires a declared owner mapping when ownership changes. Missing, stale, duplicate, unchanged, unused and ambiguous replacements fail. Omitting the field retains the previous strict standalone contract; older binaries reject the new field.
• Original historical definitions and complete test obligations remain intact. The real historical consumer verifies the current independently generated workflows, detects projection drift and verifies repair. A replacement declaration does not certify semantic equivalence or successful execution.
• Independent units each have their own workflow, status and retry. The product repository now adopts sixteen explicit complete-plan units plus a collector; this is host configuration, with no fixed unit count in the generator. The collector executes no business operations. Shared operations and all dependencies remain explicit.
• Includes beta.13 customization-preserving CI migration, host-owned bootstrap/SDK/runner settings and source-preserving initialization. A binary upgrade does not rewrite a host's CI sources, instructions or business files.

Source: c195ccedfccd78ddba8d41ac4038cd8443b7fe64. Native build passed 412 preserved tests across ten dedicated test projects on each platform. Version-plan local/integration/PR/dev checks passed 27 selected tests; all 555 previous identities remain preserved. The release contains 35 assets: fifteen tools per platform, the merged manifest, original build reports and package manifests.

Manifest SHA-256: 6c4d6d766b07b306f6b9e55813bd9c429519659db465b894013fe8e42312cfb3.

Projection migration is not a multi-file transaction. Automatic collection covers push/PR events; manual combinations use explicit collection manifests. Full input closure, full host activation, deterministic local/CI parity, interrupted metadata-rebind continuation, autonomous product PR/merge orchestration and Rust/model refinement remain unfinished. Single-agent verification; no independent review.

chrono-harness v0.1.0-beta.13

Public native prerelease for macOS arm64 and Linux x86_64. Hosts pin checksums and install selected tools under .chrono-harness/; installation requires no tracked binaries or Rust toolchain.

• chrono-ci migrate consumes explicit previous and next CI providers, verifies all prior generated files and target collisions before mutation, preserves the next host source byte for byte and retires obsolete owned workflows. It supports scoped v1/units to units and same-path updates with an explicit previous-source snapshot.
• Custom runner, bootstrap arguments, bounds and unit paths remain host-owned configuration. init preserves existing host sources; normal updates regenerate from those sources. Host-edited old projections and occupied new targets fail before any write. Unrelated workflows remain intact.
• Initial-inventory, full-governance and release-provider transitions require separate migration contracts. No host layout, language, SDK or test ownership is inferred; FILEMAP changes and actual canonical checks stay explicit. I/O failures report completed changes; migration is not a multi-file transaction.
• Includes beta.12's independently generated workflows, scoped unit execution, original-report collection and registered artifact cleanup.

Source: d49f48f0fa419254b700e4c1790e50f03d1dbfc6. Native build passed 412 preserved tests across ten dedicated test projects on each platform. Version-plan local/integration/PR/dev checks passed 27 selected tests; all 555 prior identities remain preserved. The release contains 35 assets: 15 tools per platform, the merged manifest, and original platform build reports and package manifests.

Manifest SHA-256: 6dd8803d8bc203bcda7c0dc563071e9256c22257483458ddf7dbf3f2e6c60843.

The beta.12 generated workflows were separately adopted and verified in Go, TypeScript and mixed hosts, including cancellation and selective retry. This release’s installed migration consumers and host binary upgrades remain separate delivery steps. Automatic gathering does not support manual dispatch combinations; they use explicit local collection manifests. Explicit executable pins do not certify build provenance or input closure. Full input closure, full host activation, deterministic local/CI parity, interrupted metadata-rebind continuation, autonomous product PR/merge orchestration and Rust/model refinement remain unfinished. Single-worker verification; no independent review.

chrono-harness v0.1.0-beta.12

Public native prerelease for macOS arm64 and Linux x86_64. Hosts pin checksums and install selected tools under .chrono-harness/; installation requires no tracked binaries or Rust toolchain.

• chrono-ci-check/v3 explicitly assigns complete test plans to independent units. check --unit ID partitions the full two-endpoint DELTA after global validation; local and CI use the same command. Missing or ambiguous assignments and undeclared shared prerequisites fail before business execution.
• chrono-github-units/v1 generates one workflow per unit plus collection. Each unit has its own checkout, status, bootstrap, artifact and retry. Shared prerequisites repeat only where explicitly declared; cross-workflow build-artifact dependencies are not implemented.
• check --collect MANIFEST validates required unit completeness, fixed endpoints, profiles, explicit executable pins, operations and original process evidence without rerunning business tests. Bounded GitHub gathering supports push/PR events and pins exact run attempts and workflow bytes. Unit failure does not cancel other unit workflows; retry collection after retrying a unit.
• Registered worktree cleanup verifies artifact disposal before removing the owned clean checkout and branch.

Source: f919e950ed2bb3fe97bc73147fa9f37f139718f5. Native build passed 409 preserved tests across ten dedicated test projects on each platform. Version-plan local/integration/PR/dev checks passed 27 selected tests; all 552 prior identities remain preserved. The release contains 35 assets: 15 tools per platform, the merged manifest, and original platform build reports and package manifests.

Manifest SHA-256: ec8039edc52a162d97126b9b2ace077776fbb7730437f067e937fbf31a38a3d4.

Native host adoption remains a separate verified delivery step. Automatic gathering does not support manual dispatch combinations; they use explicit local collection manifests. Explicit executable pins do not certify build provenance or input closure. Full input closure, full host activation, deterministic local/CI parity, interrupted metadata-rebind continuation, autonomous product PR/merge orchestration and Rust/model refinement remain unfinished. Single-worker verification; no independent review.

chrono-harness v0.1.0-beta.11

Public native prerelease for macOS arm64 and Linux x86_64. Hosts lock checksums and install selected tools under .chrono-harness/; no tracked product binaries or Rust toolchain are required for installation.

• chrono-worktree inspect-rebind and rebind repair missing or damaged linked-checkout metadata using an explicit branch, HEAD, chosen index tree, backup and donor. They preserve observed files and remaining original metadata, including when old operation receipts are missing. The old index and original outcome are never inferred.
• Full/initial/scoped checks and worktree creation, reconstruction, recovery and cleanup compare literal Git-tree/index/physical bytes, file types and owner executable bits. core.filemode=false, CRLF conversion, clean filters and symlink emulation cannot silently turn changed physical inputs into matching snapshot facts. Hosts must materialize the registered exact bytes.
• Unsupported tree entries retain the registration judge's structured rejection. The product's explicitly registered test plans compose without the former CI/workflow ordering cycle.

Source: a4af1a0ca7f3a69f7b3298abc5b187a74578b3f9. Native build passed 391 tests across ten dedicated test projects on each platform. Each original report retains 31 processes, 28 staged destinations and 24 matching identity observations. Local/integration/PR/dev version-plan checks passed 27 distribution tests and preserve all 534 prior identities. The release contains 35 assets: 15 tools per platform, the merged manifest, and both original build reports and package manifests.

Manifest SHA-256: 93c6d9b2a0da66a7bc555a4d475c6f300f6d705d0ee7c634c92c445c0e435330.

Full input closure, full host activation, deterministic parity and Rust/model refinement remain unfinished. Metadata rebind does not restore a lost historical index or provide interrupted continuation, concurrent-writer isolation or crash atomicity. Timestamps, ACLs, xattrs and hardlink topology are outside its preservation contract. These checks do not certify native generated-full-workflow adoption or autonomous product PR/merge orchestration. Single-worker verification; no independent review.

chrono-harness v0.1.0-beta.9

Native prerelease for macOS arm64 and Linux x86_64. Hosts install explicitly selected tools from the pinned manifest; Rust is not required on the consuming host.

• Full config v3 binds Git fact acquisition to a registered candidate tool and input, retaining actual process bytes, hashes and failures.
• CI provider v3 and scoped profile v2 explicitly select that same Git binding. Existing provider/profile versions retain their previous behavior.
• The native release recipe stages exact release binaries into registered consumer paths and checks their identities around every verification and packaging step. Original child failures remain available in uploaded evidence.
• Shared consumer fixtures retain interpreter file bytes through the existing blob representation, while preserving the explicit inline comparison and all test identities.

The release contains 15 tools for each platform, including chrono-worktree and chrono-distribution. The complete native evidence, source identity and asset hashes are included with the packages. New Git-binding profiles require explicit host adoption; upgrading binaries does not activate them automatically. Complete Git/Cargo/SDK input closure, full native host governance, deterministic parity and generated release workflows remain unfinished.

Validation: native run 36447808917 passed 352 named tests on each platform, retaining all prior identities. Each platform recorded 31 processes, 28 staged consumer destinations and 24 matching identity observations. Original process bytes, child exits and packaged asset hashes were verified against source c817a9043d9b9596547a3916d6eed84752ded2e5. Single-agent preparation and checks; no independent review is claimed.