From 52215b1c98712d26656eddfcef9b066603867191 Mon Sep 17 00:00:00 2001 From: AuricStudio Date: Wed, 30 Sep 2026 01:29:56 +0800 Subject: [PATCH] Adopt beta.14 public harness release --- .chrono-harness/ci/github.json | 2 +- .chrono-harness/ci/initial.json | 2 +- .chrono-harness/distribution.json | 6 +++--- .chrono-harness/judges.json | 2 +- README.md | 18 +++++++++--------- 5 files changed, 15 insertions(+), 15 deletions(-) diff --git a/.chrono-harness/ci/github.json b/.chrono-harness/ci/github.json index 801ab8b..800430b 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": "2a067f8ae3727e5f87c88ec79fa99f6a6db6853fb6964afe4ac5563f491d1e51", + "sha256": "bb2cef0a19a6772a7e555234ee89de2947f12205de60ee8b1e5ee8071c710de0", "argv": [ "--protocol", "chrono-initial-judge/v1" diff --git a/.chrono-harness/ci/initial.json b/.chrono-harness/ci/initial.json index 35ebdfc..6703e6b 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": "2a067f8ae3727e5f87c88ec79fa99f6a6db6853fb6964afe4ac5563f491d1e51", + "sha256": "bb2cef0a19a6772a7e555234ee89de2947f12205de60ee8b1e5ee8071c710de0", "argv": [ "--protocol", "chrono-initial-judge/v1" diff --git a/.chrono-harness/distribution.json b/.chrono-harness/distribution.json index 85e68c6..73ecb30 100644 --- a/.chrono-harness/distribution.json +++ b/.chrono-harness/distribution.json @@ -1,14 +1,14 @@ { "schema": "chrono-install/v1", - "version": "v0.1.0-beta.13", + "version": "v0.1.0-beta.14", "source": { "kind": "https", - "base_url": "https://github.com/ChronoAIProject/chrono-harness/releases/download/v0.1.0-beta.13", + "base_url": "https://github.com/ChronoAIProject/chrono-harness/releases/download/v0.1.0-beta.14", "curl": "/usr/bin/curl" }, "manifest": { "file": "release.json", - "sha256": "6dd8803d8bc203bcda7c0dc563071e9256c22257483458ddf7dbf3f2e6c60843", + "sha256": "6c4d6d766b07b306f6b9e55813bd9c429519659db465b894013fe8e42312cfb3", "size": 6252 }, "installers": { diff --git a/.chrono-harness/judges.json b/.chrono-harness/judges.json index 1954471..68a095f 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": "2a067f8ae3727e5f87c88ec79fa99f6a6db6853fb6964afe4ac5563f491d1e51", + "sha256": "bb2cef0a19a6772a7e555234ee89de2947f12205de60ee8b1e5ee8071c710de0", "argv": [ "--protocol", "chrono-judge/v1" diff --git a/README.md b/README.md index 421a3e7..13ae2df 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.13. 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.14. 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.13/docs/worktree.md). +[worktree contract](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.14/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.13 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.14 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.13/docs/worktree.md#registered-recovery-and-cleanup) +[maintenance contract](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.14/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,22 +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.13/docs/worktree.md#interrupted-checkout-recovery). +See the pinned [interruption contracts](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.14/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.13/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.14/docs/git-facts.md). ## CI projections and remote retirement -The pinned beta.13 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.13/docs/release-ci.md) and [full context CI](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.13/docs/full-ci.md) contracts. +The pinned beta.14 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.14/docs/release-ci.md) and [full context CI](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.14/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.13/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.14/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.13/docs/worktree.md#explicit-metadata-rebind) and [literal identity](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.13/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.14/docs/worktree.md#explicit-metadata-rebind) and [literal identity](https://github.com/ChronoAIProject/chrono-harness/blob/v0.1.0-beta.14/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.