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

Record the six-step RFC-CI-0001 series, the Woodpecker pipelines, the Windows
cross-target check, the local disposable-VM G-C PASS at 0d7e11b (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 is 0d7e11b.
This commit is contained in:
cflmy committed 2026-11-21 17:37:31 +08:00
1 parent 0d7e11b6f1
commit f01e8a9bb0
7 files changed
+747 -28

No files matched your search

@@ -0,0 +1,40 @@
# Performance smoke (not a G4 baseline) — `0d7e11b`
Status: **SMOKE / development container; G4 release performance UNVERIFIED.**
Date: 2026-11-21. Source SHA
`0d7e11b6f1553fb5fc24214dddac11d5db65cf91`.
This run verifies that the `marqdo.perf.v2` sampler and the committed expected
digests work. It is **not** release performance evidence: the host is a shared
development container, the run used `--warmups 1 --samples 3 --allow-smoke`,
and it is not `--approved-node`.
```text
binary sha256 sha256:1c5621972915931976145a9df5ef5dd047348ab65f24d48f6d5b2c27c7e7cc34
Cargo.lock sha256 sha256:5b9754a3ff7f56ca0158d70772365f02dcbfbc1ebbd97a55ee09d441c2d2af01
rustc rustc 1.100.0 (0ef1bc386 2026-11-09)
recipe 1 warmup + 3 samples, release profile, SHA-derived order
platform_id dev-container-unapproved
correctness VERIFIED for all 9 workloads
report status SMOKE
```
Workloads (existing corpus plus `hello-check` and `factorial-run`):
`hello-check`, `factorial-run`, `allocator-free-list`, `json-parser`,
`table-sort`, `bytecode-vm`, `matrix-multiply`, `http-parser`,
`stdlib-print-demo`.
Every warmup output matched the committed wire digest in
`tools/perf/expected/`; a mismatch would have been `CORRECTNESS_FAIL` and its
time would not be reported. Medians from this shared host are intentionally not
reproduced as a baseline.
To obtain release evidence, run on the fixed node:
```bash
python3 tools/perf/runner.py --warmups 5 --samples 20 --approved-node \
--platform-id <fixed-node-id> --cpu-list <isolated-cpus> --out perf.json
```
See [`../performance.md`](../performance.md) and
[`../../tools/perf/README.md`](../../tools/perf/README.md).
@@ -0,0 +1,83 @@
# G-C strict-isolation evidence — `0d7e11b`
Status: **local disposable-VM PASS; remote G3 UNVERIFIED.**
Date: 2026-11-21. Workspace `0.1.0`. Tested SHA:
`0d7e11b6f1553fb5fc24214dddac11d5db65cf91`.
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
a performance baseline.
## Source binding
```text
tested_sha 0d7e11b6f1553fb5fc24214dddac11d5db65cf91
source archive sha256:8a5af9712f994ac88ed43ec1cf9708b38bc92d76a8ad761b7e07e8e23b7e3503
strict-evidence.json sha256:c9de85c60b13b9b4a71b9ccba6d1812fc0d4af6e64187c67ae7bd0e602f083e8
lane log sha256:6e9f0e6e96f505c413e008c4b0ac3bee3d65cf4a2182136dfd27678ae8e75dea
base image sha256:7b90593f5532b49b7e3fe3d2743f0d1f0d822e5b07cebcd8e00c0df8069ecab9
```
The guest verified the transferred archive digest before extraction. The
`strict-evidence.json` `source_archive_sha256_matches` field is `true`.
## Environment
```text
guest OS Ubuntu 26.04.1 LTS, kernel 7.0.0-43-generic x86_64
virtualization QEMU/TCG (no KVM), systemd-detect-virt --container -> none
user dev, uid 1000, root=false
cgroup2 rw,nsdelegate,memory_recursiveprot,memory_hugetlb_accounting
bubblewrap 0.11.1 (packaged AppArmor bwrap-userns-restrict profile)
rustc 1.100.0 (0ef1bc386 2026-11-09)
cargo 1.100.0 (3acc79c0c 2026-11-05)
python 3.14.4
cc Ubuntu 15.2.0-16ubuntu1
```
The lane runs as `dev`; a root or container PASS is not accepted. The VM is
disposable and was reused only as a build cache; the source and overlay are
created for the tested SHA.
## Result
```text
cargo test -p marqdo-sandbox --test security_linux --locked -- --test-threads=1
test result: ok. 7 passed; 0 failed; 0 ignored
./tests/security/run-lane.sh
G-C security lane: PASS
```
The seven adversarial cases:
1. `strict_child_identity_is_unprivileged_and_namespaced`
2. `strict_child_cannot_read_host_files_but_reads_the_project`
3. `strict_child_cannot_write_outside_or_into_the_project`
4. `strict_child_cannot_escape_via_proc_or_privileges`
5. `strict_child_cannot_reach_the_network`
6. `strict_supervisor_enforces_fd_and_process_limits`
7. `strict_supervisor_enforces_memory_cpu_and_output_limits`
Additional contracts executed by the lane:
* strict positive CLI: `run`, `call`, multi-module, and `--json`
(`success: true`);
* strict L1 resource boundary: a project `file` resource and a `tcp` resource
are refused with `permission.denied`;
* every external-execution flag (`--allow-foreign`, read/write/net,
native/worker plugin, kernel, trace file) exits 2;
* an `@knowledge` payload containing `resource.open` produces **no** host side
effect under strict;
* a forged `MARQDO_STRICT_ACTIVE=1` is refused in text mode (exit 1) and in
`--json` mode produces exactly one document with
`code: strict.identity_invalid` (ADR-0053).
## Limits
* No remote self-hosted security-lane URL exists for this SHA; the result is
local-VM evidence only. A release needs the remote job artifact whose
`tested_sha` equals the release SHA.
* 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.