docs(status): record the CI/security convergence evidence
ci/woodpecker/push/woodpecker Pipeline was canceled
Linux strict security lane (G-C) / strict isolation escape matrix (push) Canceled after 0s
CI / fmt + clippy + test (Linux x86_64) (push) Canceled after 0s
CI / schema instance validation + consumers (push) Canceled after 0s
CI / runtime contract (macos-latest) (push) Canceled after 0s
CI / runtime contract (windows-latest) (push) Canceled after 0s
CI / release evidence manifest (push) Canceled after 0s
CI / release candidate artifact (macos-latest) (push) Canceled after 0s
CI / release candidate artifact (ubuntu-latest) (push) Canceled after 0s
ci/woodpecker/push/woodpecker Pipeline was canceled
Linux strict security lane (G-C) / strict isolation escape matrix (push) Canceled after 0s
CI / fmt + clippy + test (Linux x86_64) (push) Canceled after 0s
CI / schema instance validation + consumers (push) Canceled after 0s
CI / runtime contract (macos-latest) (push) Canceled after 0s
CI / runtime contract (windows-latest) (push) Canceled after 0s
CI / release evidence manifest (push) Canceled after 0s
CI / release candidate artifact (macos-latest) (push) Canceled after 0s
CI / release candidate artifact (ubuntu-latest) (push) Canceled after 0s
Record the six-step RFC-CI-0001 series, the Woodpecker pipelines, the Windows cross-target check, the local disposable-VM G-C PASS at0d7e11b(7/7 plus the strict JSON and inert-@knowledge contracts), and the correctness-verified performance SMOKE run. Keep the release decision at DO_NOT_RELEASE because the same SHA still lacks a remote Windows/macOS native PASS, a remote G3 artifact and a MEASURED G4 report. Include the RFC itself and link it from docs/ci.md. This is the documentation follow-up to step 6; the tested code SHA is0d7e11b.
This commit is contained in:
1 parent
0d7e11b6f1
commit
f01e8a9bb0
7 files changed
+747
-28
No files matched your search
+8
-3
@@ -126,6 +126,11 @@ reproduce the Windows checkout byte behavior.
|
||||
|
||||
## Release decision
|
||||
|
||||
**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_8af7262.md`](docs/evidence/RELEASE_CANDIDATE_0.1.0_8af7262.md).
|
||||
**DO NOT RELEASE.** The RFC-CI-0001 series fixed the platform `E0425` build
|
||||
break and the strict `--json` empty-stdout defect (ADR-0053), Woodpecker is
|
||||
green at `0d7e11b`, and the G3 lane PASSes locally as a normal user. However
|
||||
the same SHA has **no remote Windows/macOS native PASS, no remote G3 security
|
||||
artifact and no `MEASURED` G4 performance report**. Those gates remain
|
||||
`UNVERIFIED`; a local or cross-target PASS is not a platform/security release
|
||||
proof. See [`docs/STATUS.md`](docs/STATUS.md) §0.1 and
|
||||
[`docs/evidence/ci/README.md`](docs/evidence/ci/README.md).
|
||||
Reference in new issue
Block a user