diff --git a/COMPATIBILITY.md b/COMPATIBILITY.md index 2912b41..ac15d06 100644 --- a/COMPATIBILITY.md +++ b/COMPATIBILITY.md @@ -127,10 +127,11 @@ reproduce the Windows checkout byte behavior. ## Release decision **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 +break, the strict `--json` empty-stdout defect (ADR-0053) and the native +Windows/macOS portability failures. At `5fcc111` the Linux, Windows and macOS +GitHub-native jobs and Woodpecker are green, and the G3 lane PASSes locally as +an ordinary user. The release still lacks the **remote G3 security artifact** +with a matching `tested_sha` and a **`MEASURED` G4 performance report**; those +two gates remain `UNVERIFIED`. A local VM PASS is not a remote G3 proof. See +[`docs/STATUS.md`](docs/STATUS.md) §0.1 and [`docs/evidence/ci/README.md`](docs/evidence/ci/README.md). diff --git a/docs/STATUS.md b/docs/STATUS.md index e53978e..b198f53 100644 --- a/docs/STATUS.md +++ b/docs/STATUS.md @@ -102,22 +102,28 @@ The RFC-CI-0001 series fixes the release-blocking CI defects that the | 6 | `0d7e11b` | SHA-bound release-evidence aggregator, docs drift cleanup, consistent `windows-latest`/`macos-latest` statement | | 7 | `512b9f5` | evidence-generation failure fails the lane; workflow archive/verification fixes; G-C re-run | | 8 | `beb68a9` | G-C evidence/status update and the cross-platform JSON smoke exit-code fix | +| 9 | `3a29fce` | Windows PATH lookup applies `PATHEXT`; ANSI-stripped native failure annotations | +| 10 | `b898c41` | macOS parser-nesting test stack; portable process product fixture (CLI `--version` instead of `/bin/echo`) | +| 11 | `4265231` | CLI runs on an explicit 8 MiB thread (Windows 1 MiB overflow); macOS temp-path canonicalization; G3 adversarial tests opt-in | +| 12 | `a24161c` | Windows foreign temp paths stay non-verbatim (Node `lstat` rejection) | +| 13 | `5fcc111` | reject rooted Windows dependency paths (`has_root`, not `is_absolute`) | Executed evidence: | Lane | Result | Evidence | |---|---|---| -| Linux fmt/clippy/test/build (Woodpecker) | **PASS** | pipelines `#9`–`#12`, `#14`, `#16` and `#17` on the series; `#13`/`#15` were superseded/cancelled by the next push, not failures | -| Windows portability | **PASS (cross-target check)** | `cargo check --workspace --all-targets --locked --target x86_64-pc-windows-gnu` on this Linux host with MinGW; native `windows-latest` GitHub run still required for release | -| macOS portability | **UNVERIFIED** | native `macos-latest` run required; cross-check from this Linux host is blocked by `ring`'s Darwin C/asm toolchain, not by Marqdo code | -| G3 strict isolation | **PASS (local disposable VM) / remote UNVERIFIED** | `512b9f5`, `dev` uid 1000, QEMU/TCG, 7/7 + strict JSON/inert-`@knowledge`; [`evidence/2026-11-21-strict-gc-512b9f5.md`](evidence/2026-11-21-strict-gc-512b9f5.md) | +| Linux fmt/clippy/test/build (Woodpecker) | **PASS** | pipelines `#9`–`#12`, `#14`, `#16`, `#17`, `#21`–`#25` on the series; `#13`/`#15`/`#19` were superseded/cancelled by the next push, not failures | +| Linux + Windows + macOS native matrix (GitHub) | **PASS** | [run 30](https://github.com/cflmy/marqdo-cli/actions/runs/44896671929) on `5fcc111`: `fmt + clippy + test (Linux x86_64)`, `runtime contract (windows-latest)`, `runtime contract (macos-latest)`, and schema consumers all PASS | +| G3 strict isolation | **PASS (local disposable VM) / remote UNVERIFIED** | `5fcc111`, `dev` uid 1000, QEMU/TCG, 7/7 + strict JSON/inert-`@knowledge`; [`evidence/2026-11-21-strict-gc-5fcc111.md`](evidence/2026-11-21-strict-gc-5fcc111.md) | | G4 performance | **SMOKE / UNVERIFIED** | nine workloads `VERIFIED` on the dev container, 1 warmup + 3 samples; [`evidence/2026-11-21-perf-smoke-0d7e11b.md`](evidence/2026-11-21-perf-smoke-0d7e11b.md) | -Release decision: **DO NOT RELEASE.** Linux is green on Woodpecker, the strict -isolation mechanism PASSes locally as a normal user, and the platform compile -defect is fixed; but the release gate requires the same SHA to have PASSing -remote Windows/macOS jobs, a remote G3 artifact whose `tested_sha` matches, and -a `MEASURED` G4 report. None of those three remote claims is made here. +Release decision: **DO NOT RELEASE.** Linux, Windows and macOS native jobs are +green on the same SHA, and the strict isolation mechanism PASSes locally as a +normal user. The remaining release gates are the **remote** G3 artifact whose +`tested_sha` matches and a **MEASURED** G4 report on the fixed node; neither +remote claim is made here. The RFC explicitly requires the remote G3 artifact +for a release, so the local VM PASS is recorded but not promoted to a release +gate. The manifest contract is in [`evidence/ci/README.md`](evidence/ci/README.md); `tools/ci/release_evidence.py` @@ -476,9 +482,9 @@ user-written allocator is explicitly **not** claimed. print, strict file-resource refusal, forged-marker rejection and raw log. - [`evidence/RELEASE_CANDIDATE_0.1.0_8af7262.md`](evidence/RELEASE_CANDIDATE_0.1.0_8af7262.md) — G0..G12 matrix and RC decision. -- [`evidence/2026-11-21-strict-gc-512b9f5.md`](evidence/2026-11-21-strict-gc-512b9f5.md) +- [`evidence/2026-11-21-strict-gc-5fcc111.md`](evidence/2026-11-21-strict-gc-5fcc111.md) — RFC-CI-0001 series G-C: local disposable VM, `dev` uid 1000, 7/7 plus the - strict JSON and inert-`@knowledge` contracts at `512b9f5`. + strict JSON and inert-`@knowledge` contracts at `5fcc111`; the earlier `512b9f5`/`0d7e11b` runs are historical. - [`evidence/2026-11-21-perf-smoke-0d7e11b.md`](evidence/2026-11-21-perf-smoke-0d7e11b.md) — `marqdo.perf.v2` smoke: nine workloads correctness-verified, explicitly not a G4 release baseline. diff --git a/docs/evidence/2026-11-21-strict-gc-512b9f5.md b/docs/evidence/2026-11-21-strict-gc-5fcc111.md similarity index 83% rename from docs/evidence/2026-11-21-strict-gc-512b9f5.md rename to docs/evidence/2026-11-21-strict-gc-5fcc111.md index 504f1c1..53c0943 100644 --- a/docs/evidence/2026-11-21-strict-gc-512b9f5.md +++ b/docs/evidence/2026-11-21-strict-gc-5fcc111.md @@ -1,8 +1,8 @@ -# G-C strict-isolation evidence — `512b9f5` +# G-C strict-isolation evidence — `5fcc111` Status: **local disposable-VM PASS; remote G3 UNVERIFIED.** Date: 2026-11-21. Workspace `0.1.0`. Tested SHA: -`512b9f5f1da6c56959ebb801d31a1887b1c341c3`. +`5fcc111a304211dfbb3a4c85d72e0b3f4a2318be`. This is evidence for the RFC-CI-0001 CI/security series at the commit that also contains the SHA-bound evidence tooling. It is **not** a remote CI PASS and not @@ -11,10 +11,10 @@ a performance baseline. ## Source binding ```text -tested_sha 512b9f5f1da6c56959ebb801d31a1887b1c341c3 -source archive sha256:f7c975b884fae6c79fb091324a85f8bcddf5b50ffa9082d7f97eb51823254104 -strict-evidence.json sha256:d8973396db8882ed7abeec89aa4be695acbdfebef3a3bdfd99d0ad5621486cfa -lane log sha256:e9418f3b209a08524e2e5601dc14c28d46b4337cb42724c8e4f470c92d2dfa82 +tested_sha 5fcc111a304211dfbb3a4c85d72e0b3f4a2318be +source archive sha256:e13af3bbf65c576e57fde46ecf201925ad53fb70bf292b321baa96f154264fd2 +strict-evidence.json sha256:38be28aa556b04214c4b3bd3cb26e2ad00ad49c1c3a579fc9e7059784ef5c5d0 +lane log sha256:4f29201ab71b520ae3e0ea599bbff93a89cac8157fbdfc7037fac290477f83b7 base image sha256:7b90593f5532b49b7e3fe3d2743f0d1f0d822e5b07cebcd8e00c0df8069ecab9 ``` @@ -80,4 +80,5 @@ Additional contracts executed by the lane: * QEMU/TCG timing is not a performance result. The G4 baseline remains `UNVERIFIED`; see [`../performance.md`](../performance.md). * The follow-up evidence/status commit changes documentation only; the tested - code is this SHA. + code is this SHA. GitHub run 30 and Woodpecker pipeline #25 are green on this + same code SHA (before the docs-only follow-up). diff --git a/docs/security-gate.md b/docs/security-gate.md index a649602..8aa9fb1 100644 --- a/docs/security-gate.md +++ b/docs/security-gate.md @@ -4,24 +4,25 @@ Status: **PASSED on the current CI-fix series in a local disposable Ubuntu VM; Linux strict is enabled only when the runtime probe succeeds. REMOTE G3 UNVERIFIED: no self-hosted security-lane CI URL exists yet.** -Current evidence: source SHA `512b9f5f1da6c56959ebb801d31a1887b1c341c3`, +Current evidence: source SHA `5fcc111a304211dfbb3a4c85d72e0b3f4a2318be`, ordinary user `dev` (uid 1000), QEMU/TCG guest, 7/7 adversarial tests plus the strict `--json` and inert-`@knowledge` contracts — see -[`evidence/2026-11-21-strict-gc-512b9f5.md`](evidence/2026-11-21-strict-gc-512b9f5.md). +[`evidence/2026-11-21-strict-gc-5fcc111.md`](evidence/2026-11-21-strict-gc-5fcc111.md). The older `8af7262` and `b6fc182` runs are retained below as history. Snapshot: workspace `0.1.0`, 2026-11-21. See ADR-0021 and ADR-0053. > **Language-syntax status.** The lane was re-run on the RFC-LANG-0002 tree > ([`architecture/RFC-LANG-0002-unified-semantics.md`](architecture/RFC-LANG-0002-unified-semantics.md)) -> at `512b9f5`, including the strict `@knowledge`-inert check. The security +> at `5fcc111`, including the strict `@knowledge`-inert check. The security > facts are unchanged: `@exec` is a compile-time projection, not a capability > grant; `@knowledge` produces no IR and therefore no host effect; resource, > file, network, stdin/stdout, memory and budget checks remain at the > `CapabilityHost` boundary, and the strict sandbox is unaffected. See > [`STATUS.md`](STATUS.md) for the language gate and > [`evidence/2026-11-21-semantics-v2-green.md`](evidence/2026-11-21-semantics-v2-green.md). -> The earlier `0d7e11b`/`990e984` runs are code-equivalent evidence; -> `512b9f5` adds only the evidence-failure hardening in the lane script. +> The earlier `512b9f5`/`0d7e11b`/`990e984` runs are historical evidence; +> `5fcc111` is the native-green code SHA and also adds the CLI 8 MiB main +> thread, portable process fixture and the G3-only opt-in gate. This report separates three things that are often conflated: @@ -144,13 +145,13 @@ MARQDO_STRICT_ACTIVE=1 run --mode strict --json -> one JSON doc, ### 4.1 Current evidence document -`512b9f5` was archived with `git archive` and transferred as an ordinary user: +`5fcc111` was archived with `git archive` and transferred as an ordinary user: ```text -tested_sha: 512b9f5f1da6c56959ebb801d31a1887b1c341c3 -source archive: sha256:f7c975b884fae6c79fb091324a85f8bcddf5b50ffa9082d7f97eb51823254104 -strict-evidence.json: sha256:d8973396db8882ed7abeec89aa4be695acbdfebef3a3bdfd99d0ad5621486cfa -lane log: sha256:e9418f3b209a08524e2e5601dc14c28d46b4337cb42724c8e4f470c92d2dfa82 +tested_sha: 5fcc111a304211dfbb3a4c85d72e0b3f4a2318be +source archive: sha256:e13af3bbf65c576e57fde46ecf201925ad53fb70bf292b321baa96f154264fd2 +strict-evidence.json: sha256:38be28aa556b04214c4b3bd3cb26e2ad00ad49c1c3a579fc9e7059784ef5c5d0 +lane log: sha256:4f29201ab71b520ae3e0ea599bbff93a89cac8157fbdfc7037fac290477f83b7 base image: sha256:7b90593f5532b49b7e3fe3d2743f0d1f0d822e5b07cebcd8e00c0df8069ecab9 guest: Ubuntu 26.04.1, kernel 7.0.0-43-generic, bwrap 0.11.1 user: dev uid 1000 (root=false), container=none @@ -181,3 +182,6 @@ the outcome. A root PASS is rejected by the generator; this run is non-root. skip. * The current run is QEMU/TCG. It is evidence for **isolation correctness**, never for performance; see [`performance.md`](performance.md). +* The adversarial test file is opt-in: ordinary `cargo test --workspace` skips + it, the lane sets `MARQDO_REQUIRE_STRICT_SECURITY=1`, and a developer may set + `MARQDO_RUN_STRICT_SECURITY=1`. A skipped G0 test is not a G3 PASS. diff --git a/tests/README.md b/tests/README.md index 69ae654..e95dc16 100644 --- a/tests/README.md +++ b/tests/README.md @@ -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 |