From d41884be78cb82eeb568edded84e93e221bf2273 Mon Sep 17 00:00:00 2001 From: Vincent Koc Date: Fri, 13 Nov 2026 09:33:23 +0800 Subject: [PATCH] docs(release): bind candidate notes to the manifest --- .github/openclaw/release-notes.md | 4 ++-- OPENCLAW.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/openclaw/release-notes.md b/.github/openclaw/release-notes.md index 1303a4328ceb2..effaf78e5cd69 100644 --- a/.github/openclaw/release-notes.md +++ b/.github/openclaw/release-notes.md @@ -1,6 +1,6 @@ AOT value-flow no longer treats every host text evaluator as called merely because a program may run unseen code. Language evaluators and reachable host evaluator calls keep their existing behavior. Qualification covers a real Bun-host negative/positive regression pair and the existing native control for all five language evaluators. -Qualification now pins Bun `ae14f84a8f978f069ce8deadb4c5582b3331f139`, including repaired socket reconnect teardown and aliased/computed customization-hook coverage. Its runtime transpiler-cache gate expects format 53; the historical baseline remains format 36. Frozen harness adapters and the four AOT platform cases remain unchanged; final-source platform qualification is still required. +Qualification pins Bun to the exact candidate commit and tree recorded in the release manifest's `variants.candidate`, including repaired socket reconnect teardown and aliased/computed customization-hook coverage. Its runtime transpiler-cache gate expects format 53; the historical baseline remains format 36. Frozen harness adapters and the four AOT platform cases remain unchanged; final-source platform qualification is still required. AOT valueflow preserves arbitrary module answers when the program registers customization hooks, including calls through aliases. Bun must declare the registration builtin and retain its host loader calls; consumers need a joint rebuild with the matching engine headers and libraries. @@ -59,7 +59,7 @@ Other previously released engine changes remain included: Source-provenance jobs now check out complete Git history so ancestry validation can cover every merged patch commit. Sparse checkouts and the existing provenance guards remain unchanged. -Qualification requires all 21 artifact builds and the existing native Linux, Linux ARM64 and Windows ARM64 gates. The active Linux consumer now pins Bun `ae14f84a8f978f069ce8deadb4c5582b3331f139`, builds Release with AOT enabled and LTO disabled, and consumes `bun-webkit-linux-amd64-aot` from the same qualification source. Its native build has no source compatibility adapter. The current test-only adapter is measured separately; historical build/test patches and receipts remain unchanged and replay through their frozen qualification revision. Four unchanged `test/aot/every-platform.test.ts` cases must compile and execute images through the same measured binary, without failures, skips or todos. Sync and assembly revalidate the pinned test bytes, binary identity and archived log digest. Run [41565570543](https://github.com/openclaw/WebKit/actions/runs/41565570543) passed all 21 builds and the Linux, Darwin ARM64 and Windows ARM64 gates for source `94019e6ad8f7e786ec293617799b85eb57ca3e40`; assembly then failed from runner disk exhaustion, so nothing was published. That evidence remains bound to its source; every engine archive must be rebuilt and qualified from the final publication commit. The Linux Bun comparison now builds only the historical `b83b544ef744b6ab0dc1feadb59652261d64291d`/`1600131e46b5af48bbda3559af8d8a3327230b6e` baseline with recorded patches 000/012, and the exact current candidate with the measured engine manifest. The former `7b573c05d0c52dffc67d4d25daf108bed5930cf2` qualification used a measured source compatibility patch for the upstream BuiltinCode and heap-only BigInt APIs; that historical adapter is retained unchanged. The build receipt binds every original/adapted file digest and the exact compiled-input set, then requires restoration of the frozen checkout before runtime qualification. Baseline and test harness adapters remain excluded from compiled inputs. Existing node:sqlite BigInt read/write, result-metadata and range tests plus the custom-framework Bake production prerender case exercise the changed embedding APIs on the same measured binary. Existing lazy process builtins, even/odd matcher cases and 18 primitive/container serialization cases cover the removed private BigInt32 paths without changing the serialized sign, length or digit encoding. The ordinary embedding retains every feature through the engine removable-feature hooks; an unchanged Collator sensitivity case and a native URL getter smoke must complete without skips. Standalone native probes use the engine-owned untrimmed hook implementation. It preserves the original ordered 44-file/46-result selection and grouped scheduling under the explicit `candidate-pass-baseline-observed-v1` policy, and runs the 85-path historical/current selection union. Every selected candidate file must pass; ordinary baseline failures and unreported file suites remain visible. This measures a Bun-plus-engine upgrade, not an engine-only change. +Qualification requires all 21 artifact builds and the existing native Linux, Linux ARM64 and Windows ARM64 gates. The active Linux consumer pins Bun to the exact candidate commit and tree recorded in the release manifest's `variants.candidate`, builds Release with AOT enabled and LTO disabled, and consumes `bun-webkit-linux-amd64-aot` from the same qualification source. Its native build has no source compatibility adapter. The current test-only adapter is measured separately; historical build/test patches and receipts remain unchanged and replay through their frozen qualification revision. Four unchanged `test/aot/every-platform.test.ts` cases must compile and execute images through the same measured binary, without failures, skips or todos. Sync and assembly revalidate the pinned test bytes, binary identity and archived log digest. Run [41565570543](https://github.com/openclaw/WebKit/actions/runs/41565570543) passed all 21 builds and the Linux, Darwin ARM64 and Windows ARM64 gates for source `94019e6ad8f7e786ec293617799b85eb57ca3e40`; assembly then failed from runner disk exhaustion, so nothing was published. That evidence remains bound to its source; every engine archive must be rebuilt and qualified from the final publication commit. The Linux Bun comparison now builds only the historical `b83b544ef744b6ab0dc1feadb59652261d64291d`/`1600131e46b5af48bbda3559af8d8a3327230b6e` baseline with recorded patches 000/012, and the exact current candidate with the measured engine manifest. The former `7b573c05d0c52dffc67d4d25daf108bed5930cf2` qualification used a measured source compatibility patch for the upstream BuiltinCode and heap-only BigInt APIs; that historical adapter is retained unchanged. The build receipt binds every original/adapted file digest and the exact compiled-input set, then requires restoration of the frozen checkout before runtime qualification. Baseline and test harness adapters remain excluded from compiled inputs. Existing node:sqlite BigInt read/write, result-metadata and range tests plus the custom-framework Bake production prerender case exercise the changed embedding APIs on the same measured binary. Existing lazy process builtins, even/odd matcher cases and 18 primitive/container serialization cases cover the removed private BigInt32 paths without changing the serialized sign, length or digit encoding. The ordinary embedding retains every feature through the engine removable-feature hooks; an unchanged Collator sensitivity case and a native URL getter smoke must complete without skips. Standalone native probes use the engine-owned untrimmed hook implementation. It preserves the original ordered 44-file/46-result selection and grouped scheduling under the explicit `candidate-pass-baseline-observed-v1` policy, and runs the 85-path historical/current selection union. Every selected candidate file must pass; ordinary baseline failures and unreported file suites remain visible. This measures a Bun-plus-engine upgrade, not an engine-only change. Compatibility startup and three unchanged memory-release tests, feature regressions, inspector checks and runtime transpiler-cache replacement from baseline format 36 to candidate format 53 and warm replay all reuse the same candidate binary. Eleven current Bun WebKit-upgrade cases must pass without skips. Native ARM64 also runs the parser-arena and both heap-teardown API regressions with three exact completed JUnit identities. Its existing build also links testaot and executes the two compiled namespace cases and eight compiled module-program cases beside the matching jsc. Both selections use the supported single-process native mode under one 600-second supervisor, retain nested image-process supervision, and require every ordered case name and the exact zero-failure summaries. This ARM64 proof covers engine image execution; the separate four-case Linux Bun gate covers its pinned AOT compiler. Neither is ALS/facade integration qualification. Immutable build-tool receipts bind the historical baseline logger adapter and actual build commands to the binaries. The current candidate uses its native build logger without a patch; identical source, compiled-input inventory and executable guards still apply. The consumer identity binds those receipts, source/index, sole tracked manifest overlay, engine archive, binary bytes, measured runtime and separately copied worker fixture. Fixed post-build adapters provide the same reporter, retry accounting, safe logging and process-termination evidence to both frozen Bun pins. The optional crash-remapper install also uses its frozen lockfile on both pins; installation refusal still permits tests to run, without exempting the lockfile from source-restoration guards. Each invocation binds its ordered selection, raw results and terminal observations to that identity; its receipt is finalized only after exact source restoration. Assembly verifies the actual uploaded bytes against that receipt. The historical W113/W150 adapter reconstruction is retired; runtime counterparts are already landed in the candidate. Historical findings above are not fresh qualification results for this source. Consumers must jointly rebuild Bun with the exact engine headers and libraries. diff --git a/OPENCLAW.md b/OPENCLAW.md index ca26d8686c2f5..4a5673f98d740 100644 --- a/OPENCLAW.md +++ b/OPENCLAW.md @@ -86,7 +86,7 @@ concurrent GC. This workflow provides the pre-merge check; it cannot publish. For final publication, dispatch the reviewed full SHA with `publish: true`. This builds every lane and runs all qualification gates before waiting at the protected `openclaw-artifacts` environment. Only the publication job has repository write -permission. It assembles exactly the ten archives, `manifest.json`, +permission. It assembles exactly 21 native-lane archives plus one AOT-source archive, `manifest.json`, `SHA256SUMS`, `provenance.tar.gz`, and `LICENSE-SOURCES.txt`. Repository immutable releases must be enabled. Once the publishing dispatch is