diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 50ef67a..acbeee3 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -150,7 +150,11 @@ jobs: shell: bash run: | set -euo pipefail + set +e json=$(cargo run -q -p marqdo-cli -- run examples/hello.mq.md --mode strict --json) + code=$? + set -e + test "$code" -eq 1 JSON_DOC="$json" python3 - <<'PY' import json, os document = json.loads(os.environ["JSON_DOC"]) diff --git a/docs/STATUS.md b/docs/STATUS.md index df36a93..fd877a1 100644 --- a/docs/STATUS.md +++ b/docs/STATUS.md @@ -105,10 +105,10 @@ Executed evidence: | Lane | Result | Evidence | |---|---|---| -| Linux fmt/clippy/test/build (Woodpecker) | **PASS** | pipelines `#9`–`#12` and `#14` on `0d7e11b`; `#13` was superseded/cancelled by the next push, not a failure | +| Linux fmt/clippy/test/build (Woodpecker) | **PASS** | pipelines `#9`–`#12`, `#14` and `#16` on `512b9f5`; `#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** | `0d7e11b`, `dev` uid 1000, QEMU/TCG, 7/7 + strict JSON/inert-`@knowledge`; [`evidence/2026-11-21-strict-gc-0d7e11b.md`](evidence/2026-11-21-strict-gc-0d7e11b.md) | +| 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) | | 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 @@ -474,9 +474,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-0d7e11b.md`](evidence/2026-11-21-strict-gc-0d7e11b.md) +- [`evidence/2026-11-21-strict-gc-512b9f5.md`](evidence/2026-11-21-strict-gc-512b9f5.md) — RFC-CI-0001 series G-C: local disposable VM, `dev` uid 1000, 7/7 plus the - strict JSON and inert-`@knowledge` contracts at `0d7e11b`. + strict JSON and inert-`@knowledge` contracts at `512b9f5`. - [`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-0d7e11b.md b/docs/evidence/2026-11-21-strict-gc-512b9f5.md similarity index 87% rename from docs/evidence/2026-11-21-strict-gc-0d7e11b.md rename to docs/evidence/2026-11-21-strict-gc-512b9f5.md index d238699..504f1c1 100644 --- a/docs/evidence/2026-11-21-strict-gc-0d7e11b.md +++ b/docs/evidence/2026-11-21-strict-gc-512b9f5.md @@ -1,8 +1,8 @@ -# G-C strict-isolation evidence — `0d7e11b` +# G-C strict-isolation evidence — `512b9f5` Status: **local disposable-VM PASS; remote G3 UNVERIFIED.** Date: 2026-11-21. Workspace `0.1.0`. Tested SHA: -`0d7e11b6f1553fb5fc24214dddac11d5db65cf91`. +`512b9f5f1da6c56959ebb801d31a1887b1c341c3`. 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 0d7e11b6f1553fb5fc24214dddac11d5db65cf91 -source archive sha256:8a5af9712f994ac88ed43ec1cf9708b38bc92d76a8ad761b7e07e8e23b7e3503 -strict-evidence.json sha256:c9de85c60b13b9b4a71b9ccba6d1812fc0d4af6e64187c67ae7bd0e602f083e8 -lane log sha256:6e9f0e6e96f505c413e008c4b0ac3bee3d65cf4a2182136dfd27678ae8e75dea +tested_sha 512b9f5f1da6c56959ebb801d31a1887b1c341c3 +source archive sha256:f7c975b884fae6c79fb091324a85f8bcddf5b50ffa9082d7f97eb51823254104 +strict-evidence.json sha256:d8973396db8882ed7abeec89aa4be695acbdfebef3a3bdfd99d0ad5621486cfa +lane log sha256:e9418f3b209a08524e2e5601dc14c28d46b4337cb42724c8e4f470c92d2dfa82 base image sha256:7b90593f5532b49b7e3fe3d2743f0d1f0d822e5b07cebcd8e00c0df8069ecab9 ``` diff --git a/docs/security-gate.md b/docs/security-gate.md index c2020e9..a649602 100644 --- a/docs/security-gate.md +++ b/docs/security-gate.md @@ -4,24 +4,24 @@ 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 `0d7e11b6f1553fb5fc24214dddac11d5db65cf91`, +Current evidence: source SHA `512b9f5f1da6c56959ebb801d31a1887b1c341c3`, 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-0d7e11b.md`](evidence/2026-11-21-strict-gc-0d7e11b.md). +[`evidence/2026-11-21-strict-gc-512b9f5.md`](evidence/2026-11-21-strict-gc-512b9f5.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 `0d7e11b`, including the strict `@knowledge`-inert check. The security +> at `512b9f5`, 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 `990e984` run is the earlier code-equivalent evidence; `0d7e11b` adds -> only the CI/docs evidence commit on top. +> The earlier `0d7e11b`/`990e984` runs are code-equivalent evidence; +> `512b9f5` adds only the evidence-failure hardening in the lane script. This report separates three things that are often conflated: @@ -144,13 +144,13 @@ MARQDO_STRICT_ACTIVE=1 run --mode strict --json -> one JSON doc, ### 4.1 Current evidence document -`0d7e11b` was archived with `git archive` and transferred as an ordinary user: +`512b9f5` was archived with `git archive` and transferred as an ordinary user: ```text -tested_sha: 0d7e11b6f1553fb5fc24214dddac11d5db65cf91 -source archive: sha256:8a5af9712f994ac88ed43ec1cf9708b38bc92d76a8ad761b7e07e8e23b7e3503 -strict-evidence.json: sha256:c9de85c60b13b9b4a71b9ccba6d1812fc0d4af6e64187c67ae7bd0e602f083e8 -lane log: sha256:6e9f0e6e96f505c413e008c4b0ac3bee3d65cf4a2182136dfd27678ae8e75dea +tested_sha: 512b9f5f1da6c56959ebb801d31a1887b1c341c3 +source archive: sha256:f7c975b884fae6c79fb091324a85f8bcddf5b50ffa9082d7f97eb51823254104 +strict-evidence.json: sha256:d8973396db8882ed7abeec89aa4be695acbdfebef3a3bdfd99d0ad5621486cfa +lane log: sha256:e9418f3b209a08524e2e5601dc14c28d46b4337cb42724c8e4f470c92d2dfa82 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