docs(status): record the native-green matrix and final G3 evidence
ci/woodpecker/push/woodpecker Pipeline was successful
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

GitHub run 30 on 5fcc111 is green for Linux, windows-latest and macos-latest
(the native failures were Windows PATHEXT/temp/rooted-path issues, macOS test
temp canonicalization and a Windows 1 MiB main-thread overflow). Woodpecker
#25 is green on the same SHA, and the disposable-VM G3 lane PASSes 7/7 plus the
strict JSON/inert-@knowledge contracts.

The release decision stays DO_NOT_RELEASE, now only for the remote G3 artifact
with matching tested_sha and the MEASURED G4 report; the native platform block
is closed. Document that the adversarial suite is G3-opt-in so ordinary
cargo test --workspace cannot turn a hosted namespace-capable host into a G0
failure.
This commit is contained in:
cflmy committed 2026-11-21 19:07:07 +08:00
1 parent 5fcc111a30
commit fd04ffb98e
5 files changed
+53 -34

No files matched your search

+7
View File
@@ -35,6 +35,13 @@ tests/
└── README.md this file
```
G3 security matrix: `crates/marqdo-sandbox/tests/security_linux.rs` is
**opt-in**. Ordinary `cargo test --workspace` skips it so a namespace-capable
but non-disposable host cannot turn the G0 Linux gate red. The disposable-VM
lane sets `MARQDO_REQUIRE_STRICT_SECURITY=1` (a missing mechanism fails); a
developer opts in with `MARQDO_RUN_STRICT_SECURITY=1`. A skipped G0 test is
never a G3 PASS.
Rust harnesses (all in `crates/cli/tests/`):
| Harness | What it proves |