From a113d894962d8c00eb02efb42e0e73f8b084a1fa Mon Sep 17 00:00:00 2001 From: cflmy Date: Fri, 20 Nov 2026 16:01:43 +0800 Subject: [PATCH] docs: bind README/COMPATIBILITY/CHANGELOG to the convergence SHA Completes the release-status updates that were staged separately from the evidence files. Code under test is unchanged from 8af7262 (G-C 7/7, workspace 47/47); final HEAD differs only by documentation. CI_URL: none from this host (Gitee remote, no GitHub credentials). --- CHANGELOG.md | 2 +- COMPATIBILITY.md | 4 ++-- README.md | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 5a6960f..d861940 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -88,7 +88,7 @@ currently `0.1.0`; no release tag has been cut. Dates use ISO 8601. sandbox starts. Strict L2 inheritance is future work. - Capability brokers and worker processes remain cooperative authorization/crash isolation, not an OS sandbox. -- The G-C lane was re-run at `f075c96` from a clean `git archive` in a +- The G-C lane was re-run at `8af7262` from a clean `git archive` in a disposable Ubuntu 26.04 VM as ordinary user `dev`: 7/7 adversarial tests, positive CLI contract and forged-marker rejection PASS. This is still a local VM result, not a self-hosted GitHub security-lane URL. diff --git a/COMPATIBILITY.md b/COMPATIBILITY.md index d12a22e..f2fdbd7 100644 --- a/COMPATIBILITY.md +++ b/COMPATIBILITY.md @@ -1,6 +1,6 @@ # Compatibility and support matrix -Snapshot: workspace version **0.1.0**, code/security SHA **`f075c96`**, no +Snapshot: workspace version **0.1.0**, code/security SHA **`8af7262`**, no release tag cut. This file records what was actually verified and separates it from what is only implemented. @@ -85,4 +85,4 @@ reproduce the Windows checkout byte behavior. **DO NOT RELEASE.** G1/G2/G3 (native CI) and G9 (self-hosted security-lane CI URL) have no real remote PASS for this SHA. See -[`docs/evidence/RELEASE_CANDIDATE_0.1.0_f075c96.md`](docs/evidence/RELEASE_CANDIDATE_0.1.0_f075c96.md). +[`docs/evidence/RELEASE_CANDIDATE_0.1.0_8af7262.md`](docs/evidence/RELEASE_CANDIDATE_0.1.0_8af7262.md). diff --git a/README.md b/README.md index a3bdd29..00be4bb 100644 --- a/README.md +++ b/README.md @@ -16,11 +16,11 @@ plugin ABI v2 are not claimed to work here. > Analysis v2, Trace v2, Tool v1, Plugin ABI v1 (native + worker) and pinned > Foreign providers are implemented and covered by tests on Linux. The > macOS/Windows `E0433` platform-cfg failure and the Linux strict -> probe→launch race are fixed in source at `f075c96`, but the native +> probe→launch race are fixed in source at `8af7262`, but the native > Windows/macOS and GitHub Linux lanes have not been re-run from this > checkout. **`strict` OS isolation is available on Linux only when the > runtime Bubblewrap probe passes**; it was verified against the full -> escape/resource matrix in a disposable Ubuntu 26.04 VM at `f075c96` +> escape/resource matrix in a disposable Ubuntu 26.04 VM at `8af7262` > (ADR-0021). macOS/Windows fail closed, strict L2 (Worker/Foreign) is not > implemented, and the broker/worker are not a sandbox. The release decision > is **DO NOT RELEASE** until the remote gates have same-SHA URLs. See