From 74ce5980c247a2696720e4ecaf3bafb2346588b3 Mon Sep 17 00:00:00 2001 From: AuricStudio Date: Tue, 29 Sep 2026 22:45:23 +0800 Subject: [PATCH] Adopt beta.12 metadata-recovery and literal-checkout release --- .chrono-harness/ci/github.json | 2 +- .chrono-harness/ci/initial.json | 2 +- .chrono-harness/config.json | 2 +- .chrono-harness/distribution.json | 12 ++++++------ .chrono-harness/judges.json | 2 +- README.md | 20 +++++++++++--------- 6 files changed, 21 insertions(+), 19 deletions(-) diff --git a/.chrono-harness/ci/github.json b/.chrono-harness/ci/github.json index 52c83f0..801ab8b 100644 --- a/.chrono-harness/ci/github.json +++ b/.chrono-harness/ci/github.json @@ -41,7 +41,7 @@ { "id": "initial-registration", "executable": ".chrono-harness/bin/chrono-judge-registration", - "sha256": "79ab483ef3c16a9f9bf640dc54e4fb7450002c59255827cc15f8494f086c61c9", + "sha256": "2a067f8ae3727e5f87c88ec79fa99f6a6db6853fb6964afe4ac5563f491d1e51", "argv": [ "--protocol", "chrono-initial-judge/v1" diff --git a/.chrono-harness/ci/initial.json b/.chrono-harness/ci/initial.json index 4d65501..35ebdfc 100644 --- a/.chrono-harness/ci/initial.json +++ b/.chrono-harness/ci/initial.json @@ -6,7 +6,7 @@ "id": "initial-registration", "executable": ".chrono-harness/bin/chrono-judge-registration", "version": "0.1.0", - "sha256": "79ab483ef3c16a9f9bf640dc54e4fb7450002c59255827cc15f8494f086c61c9", + "sha256": "2a067f8ae3727e5f87c88ec79fa99f6a6db6853fb6964afe4ac5563f491d1e51", "argv": [ "--protocol", "chrono-initial-judge/v1" diff --git a/.chrono-harness/config.json b/.chrono-harness/config.json index 2aeb83f..cd5f399 100644 --- a/.chrono-harness/config.json +++ b/.chrono-harness/config.json @@ -5,7 +5,7 @@ "runner": { "path": ".chrono-harness/bin/chrono-harness", "version": "0.1.0", - "sha256": "25e94a55eeba6bb6b2c4818c8ee287204128da0841741e1c0e98c886872ff635" + "sha256": "b3933b773ed4a03a5d79d9fa0dd4e9de9b35f8ce13d8864fdf021d489aa2526c" }, "registries": { "judges": ".chrono-harness/judges.json", diff --git a/.chrono-harness/distribution.json b/.chrono-harness/distribution.json index 8fe3f4b..e408339 100644 --- a/.chrono-harness/distribution.json +++ b/.chrono-harness/distribution.json @@ -1,25 +1,25 @@ { "schema": "chrono-install/v1", - "version": "v0.1.0-beta.11", + "version": "v0.1.0-beta.12", "source": { "kind": "https", - "base_url": "https://github.com/ChronoAIProject/chrono-harness/releases/download/v0.1.0-beta.11", + "base_url": "https://github.com/ChronoAIProject/chrono-harness/releases/download/v0.1.0-beta.12", "curl": "/usr/bin/curl" }, "manifest": { "file": "release.json", - "sha256": "93c6d9b2a0da66a7bc555a4d475c6f300f6d705d0ee7c634c92c445c0e435330", + "sha256": "ec8039edc52a162d97126b9b2ace077776fbb7730437f067e937fbf31a38a3d4", "size": 6252 }, "installers": { "linux-x86_64": { "file": "chrono-distribution-linux-x86_64", - "sha256": "0c38f845f4147e38d297b288db1b2f0989b8cba825e467a78c1d99435fb4265d", - "size": 933704 + "sha256": "75752af5d933d046851737b613245bd3bc390c55b03a2422f8af960fe2f838a7", + "size": 936296 }, "macos-aarch64": { "file": "chrono-distribution-macos-aarch64", - "sha256": "c4454d54d0b163ccf0b06a9af1757124f2ab066c686d21c9998fa645b79b3dfa", + "sha256": "c51a8f7cba74c0cf6cfbaed61c4d5d31f0d7d22d80147fb47b9a6a63d4f1008d", "size": 786176 } }, diff --git a/.chrono-harness/judges.json b/.chrono-harness/judges.json index c967cda..1954471 100644 --- a/.chrono-harness/judges.json +++ b/.chrono-harness/judges.json @@ -5,7 +5,7 @@ { "id": "registration", "executable": ".chrono-harness/bin/chrono-judge-registration", - "sha256": "79ab483ef3c16a9f9bf640dc54e4fb7450002c59255827cc15f8494f086c61c9", + "sha256": "2a067f8ae3727e5f87c88ec79fa99f6a6db6853fb6964afe4ac5563f491d1e51", "argv": [ "--protocol", "chrono-judge/v1" diff --git a/README.md b/README.md index c1db8f3..011ea4b 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # chrono-harness initial-host example -A documentation-only host demonstrating the generated first-root inventory profile and subsequent DELTA checks with public chrono-harness v0.1.0-beta.11. There are no production or test projects. All tracked files are explicitly registered; no project structure or language is inferred. +A documentation-only host demonstrating the generated first-root inventory profile and subsequent DELTA checks with public chrono-harness v0.1.0-beta.12. There are no production or test projects. All tracked files are explicitly registered; no project structure or language is inferred. Install the pinned public release with `python3 .chrono-harness/install.py .`. For the parentless root commit, run `.chrono-harness/bin/chrono-harness check --config .chrono-harness/ci/initial.json --candidate ROOT_OID --initial`. @@ -27,14 +27,14 @@ registrations have one owner; directory names and languages do not select work. The destination must not exist. `reconstruct` uses the same arguments plus `--plan .chrono-harness/state/reconstruction.json`, with explicit fixed base and candidate OIDs and a complete carry/retire path list. See the -[worktree contract](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.11/docs/worktree.md). +[worktree contract](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.12/docs/worktree.md). Creation/reconstruction records actual Git results and preserves old work; reconstruction stages changes and requires a new commit and the canonical check. PR creation and merge remain caller-owned. Shared full-governance registries are proposed; worktree use does not activate them or establish full input closure, freshness certification or deterministic local/CI parity. -The historical parentless root keeps its own beta.5 lock and initial profile; reproduce it from that checkout. This beta.11 adoption uses ordinary DELTA checks and does not claim a new first-root inventory. +The historical parentless root keeps its own beta.5 lock and initial profile; reproduce it from that checkout. This beta.12 adoption uses ordinary DELTA checks and does not claim a new first-root inventory. ## Registered maintenance @@ -53,7 +53,7 @@ requires an explicit retained branch/commit and selected disposable artifacts. Fetch-ref cleanup requires its original failed receipt and a fixed local branch preserving the expected commit. Reports retain failures and distinguish verified removal from unverified partial effects. See the pinned -[maintenance contract](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.11/docs/worktree.md#registered-recovery-and-cleanup) +[maintenance contract](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.12/docs/worktree.md#registered-recovery-and-cleanup) for complete plan formats. Lost recovery identity, damaged Git metadata and PR/merge orchestration remain separate obligations. @@ -73,20 +73,22 @@ Checkout recovery also requires the reconciled HEAD/index tree. Fetch cleanup requires the expected current OID and a local branch retaining it; an already absent ref needs an explicit retry plan. Both preserve the original bytes and keep the original outcome unknown; terminal reports use ordinary maintenance. -See the pinned [interruption contracts](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.11/docs/worktree.md#interrupted-checkout-recovery). +See the pinned [interruption contracts](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.12/docs/worktree.md#interrupted-checkout-recovery). These commands do not reconstruct a lost index, make concurrent writers atomic, or certify full governance or deterministic parity. -The pinned release also provides optional explicitly bound Git readers. This host keeps its registered scoped profile; adopting new binaries does not implicitly change the Git-binding or governance policy. See the pinned [Git facts contract](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.11/docs/git-facts.md). +The pinned release also provides optional explicitly bound Git readers. This host keeps its registered scoped profile; adopting new binaries does not implicitly change the Git-binding or governance policy. See the pinned [Git facts contract](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.12/docs/git-facts.md). ## CI projections and remote retirement -The pinned beta.11 binaries also provide explicit release-workflow generation and full-context CI transport. This host retains its registered scoped profile; installing binaries does not activate full governance. See the pinned [release CI](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.11/docs/release-ci.md) and [full context CI](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.11/docs/full-ci.md) contracts. +The pinned beta.12 binaries also provide explicit release-workflow generation and full-context CI transport. This host retains its registered scoped profile; installing binaries does not activate full governance. See the pinned [release CI](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.12/docs/release-ci.md) and [full context CI](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.12/docs/full-ci.md) contracts. -`chrono-worktree cleanup-remote` consumes an explicit state plan with the expected remote URL, work-branch OID and retained target commit. It performs exact leased deletion, verifies absence and preserves original failures; this is not an atomic remote transaction or a PR/merge verdict. See [remote retirement](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.11/docs/worktree.md#remote-branch-retirement). +`chrono-worktree cleanup-remote` consumes an explicit state plan with the expected remote URL, work-branch OID and retained target commit. It performs exact leased deletion, verifies absence and preserves original failures; this is not an atomic remote transaction or a PR/merge verdict. See [remote retirement](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.12/docs/worktree.md#remote-branch-retirement). ## Literal checkout and metadata recovery The pinned binaries compare registered Git-tree/index identities with physical bytes, file types and owner executable bits. Git configuration cannot silently normalize changed inputs for this comparison; checkouts must materialize the registered exact bytes. -`chrono-worktree inspect-rebind` and `rebind` use an explicit branch, HEAD, chosen index tree, backup and donor to repair missing or damaged linked-checkout metadata while preserving observed work. They do not infer the lost historical index or original outcome, and interrupted rebind continuation remains outside this contract. See [metadata rebind](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.11/docs/worktree.md#explicit-metadata-rebind) and [literal identity](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.11/docs/git-facts.md#literal-checkout-identity). +`chrono-worktree inspect-rebind` and `rebind` use an explicit branch, HEAD, chosen index tree, backup and donor to repair missing or damaged linked-checkout metadata while preserving observed work. They do not infer the lost historical index or original outcome, and interrupted rebind continuation remains outside this contract. See [metadata rebind](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.12/docs/worktree.md#explicit-metadata-rebind) and [literal identity](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.12/docs/git-facts.md#literal-checkout-identity). + +This example retains its explicit initial-inventory contract and has no execution plans or scripts. The public binary upgrade does not create empty CI units or adopt a scoped profile in place of the initial contract.