Add tools/ci/release_evidence.py (marqdo.release-gates.v1) plus unit tests:
missing/skipped/FAIL/UNVERIFIED and tested_sha mismatches stay
DO_NOT_RELEASE, performance may be PASS/WARN, unknown gate names are rejected.
The GitHub CI now has a release-evidence job that maps the Linux/schema and
native matrix results onto the manifest and uploads it, and both CI systems
run the evidence-tool tests.
Clear the contradictions the RFC calls out: remove the stale CURRENT.md rows
that claimed DNS/TLS/UDP and fs metadata were absent while the same table said
they were implemented; correct docs/ci.md to state that the GitHub-hosted
Windows/macOS matrix exists (Woodpecker has no such agent); keep the old
convergence plan historical; require the evidence manifest in releasing.md;
and add a docs-consistency guard for these claims.
This is step 6 of the CI/security RFC (B05/B06/B07).
Add an architecture test that rejects direct marker_present/verify_active
references from the CLI and keeps the Linux-only functions out of the
marqdo-sandbox crate root. Windows cross-target cargo check now compiles the
whole workspace (macOS cross-check is blocked only by ring's Darwin C/asm
build on this Linux host; its cfg(not(linux)) path is the same one Windows
exercises).
This completes the step 3 verification for the CI/security RFC B01.
Capture the strict child through launch_strict_capture and classify the
outcome before writing anything. In --json mode a control-plane failure now
emits exactly one error document with a stable code instead of forwarding
bubblewrap stderr and leaving stdout empty; a verified child's valid JSON is
forwarded unchanged with its own exit code. Empty, partial or non-JSON child
output becomes strict.child_invalid.
Route the remaining run --json error paths (mode, grants, missing entry,
trace) through the same contract, classify sandbox launch failures with
StrictFailureKind so probe/spawn/timeout/resource failures stay
distinguishable, and add deterministic routing tests plus forged-marker CLI
coverage. Document the decision in ADR-0053 and spec/security.md 1.2.
This is step 2 of the CI/security RFC (B02/B03).
The CLI referenced Linux-only marker_present/verify_active directly, so
macOS and Windows builds failed with E0425. Add StrictChildState and
inspect_strict_child() to marqdo-sandbox: Linux performs the full identity
verification, while every other platform rejects even a forged
MARQDO_STRICT_ACTIVE marker. The Linux-only functions are no longer
re-exported from the crate root, so future callers cannot bypass the
platform boundary.
This is step 1 of the CI/security RFC (B01).
Follow-up cleanup of text left by the concurrent implementation:
- marqdo-markdown AST, marqdo-ir statements/branch arms, frontend units,
payload and signature module docs now describe RFC-LANG-0002 roles
(payload carriers, heading modes, if/else groups, while/end, params)
- marqdo-expression public docs list parse_payload_statement and stop
describing a Markdown-link call that no longer exists
- retired markdown.invalid_construct/markdown.inert_executable constants
are documented as decode-only history for old Analysis/Trace JSON
- drop the stale 'expected red' comment in the CLI integration test
- the dev-only .mq.md review aid no longer reports semicolons inside
string literals, and skips AST baselines / expected-invalid negatives
Verified: fmt, clippy -D warnings and cargo test --workspace --locked green.
The pre-RFC link-form block-quote call was removed by RFC-LANG-0002, but the
IR still carried Stmt::Call, CallSite and CallTarget with matching branches in
the runtime, infer, call validation, loader, analysis projection and JSON
output. No mapper produces that variant any more, so it was a second call
representation that could never be reached.
- remove Stmt::Call, CallSite and CallTarget from marqdo-ir
- remove the runtime exec_call_site path and every exhaustive match arm
- remove the 'call_site' Analysis node and its JSON helpers
- state in spec/analysis-v2.md that calls are expressions; keep v1 as history
with a note that call_site is not produced by the current language
Verified: cargo clippy --workspace --all-targets -D warnings clean and
cargo test --workspace --locked green (62 targets).
Move keyword recognition out of the Markdown mapper and into the single
expression/statement parser:
- add parse_payload_statement + PayloadStatement for if/else/while/end/
return/params/ordinary; keyword matching uses complete tokens, requires
whitespace before a control expression, rejects trailing tokens/colons
and reserves the statement words in expression positions
- keep expression spans payload-relative so the frontend can rewrite them
onto the file; malformed params(...) interiors stay owned by the
signature parser (one sem.syntax diagnostic, not a duplicate)
- simplify the frontend mapper to control-stack lowering and mapped
semantic diagnostics only
- emit sem.no_entry_function from run when no Exec H2 main exists
- add else-under-while, params-in-quote, Knowledge-inertness and
no-entry tests; update the corpus counts
- make the EBNF parameter type annotation optional (params(n) is valid)
Verified: cargo fmt --check, cargo clippy -D warnings and
cargo test --workspace --locked: 501 passed, 0 failed, 2 ignored.
One Markdown-to-program mapping, no version selector or legacy mapper.
Frontend/runtime:
- resolve @exec/@knowledge heading declarations with nearest-ancestor
inheritance; only an Exec H2 is callable; add UnitKind::Knowledge and
sem.* diagnostics (mode marker, unit name, exec-without-function,
payload nesting/empty, syntax, control stack, params position,
version directive, inferred-signature lint)
- extract Strong/Emph/inline Code as one-statement carriers, refuse
nested carriers, and honour heading segment boundaries so an if/while
cannot be closed across a heading
- lower if/else/while/end to the existing Branch/Loop/Return IR with a
compile-time control stack; keep payload-relative source spans through
expression parsing and rewrite them onto the file
- accept params(...) only as the first direct Exec H2 payload; keep the
existing free-variable inference and named-only rule for inferred
signatures; fix duplicate-mode/else/end and Knowledge-body inertness
- reject marqdo_semantics/syntax front matter directives
Data and tests:
- migrate stdlib/**/*.mq.md, regenerate stdlib.json digest
- migrate examples and the full semantics/negative/runtime corpus to
the only current syntax; expected values/runtime codes preserved
- migrate Rust-embedded .mq.md fixtures, init template, CLI help and
security-lane fixtures
Verified: cargo fmt --check, cargo clippy -D warnings and
cargo test --workspace --locked (green).
- Fixture 73 implements triple-list lookup, dense conversion and sparse
multiply with Int arithmetic and exact indexing.
- Include it in the P2 pure closure lane and update golden count to 73,
C12 evidence mapping, status/README/changelog.
Gate: fmt, clippy -D warnings, 430 tests passed.
- Add semantic fixture 72: a .mq.md columnar List/Map table store, converted,
sorted and filtered; compare headers/cells with the T0 row Table via a
cell-wise helper (Table == is not structural in this language version).
- Teach the direct-runtime semantic harness to resolve entry std: imports.
- Update ADR-0032, P4 status, docs/changelog/evidence; semantic goldens 72.
Gate: fmt, clippy -D warnings, 430 tests passed.
- Add stdlib/net/http.mq.md: status/header/chunked response parsing and request
construction in .mq.md; no host HTTP/TLS implementation.
- Add stdlib/tests/http.mq.md and an end-to-end loopback test that sends a GET
over resource.open("tcp"), reads bytes, parses the response and returns
status/content-type/body.
- Update ADR-0034, status/spec/README/changelog and evidence; refresh the
bundle digest.
Gate: fmt, clippy -D warnings, 430 tests passed.
- Add crates/cli/tests/p2_closure.rs: 20 semantic fixtures run through the real
CLI in --mode pure (Capabilities::pure), source scan for foreign./plugin./
import:, and golden value/stdout comparison.
- Run the stdlib table self-test in pure mode; no host shortcut or recompilation
is needed for the selected algorithms.
- Mark P2 gate PASS locally (external stdlib repo publication and remote CI
remain outside the C01-C12 gate); add evidence and docs.
Gate: fmt, clippy -D warnings, 428 tests passed.
- Strict child now gets the verified stdlib tree read-only at
/run/marqdo-stdlib with MARQDO_STDLIB_DIR set, so Compat-C 打印 works under
strict without exposing a host path (ADR-0021 update).
- Add a strict-lane negative: resource.open(file) is refused with
permission.denied; hello/factorial/multi-module and --json still pass.
- StrictHostCommand gains stdlib_dir; CLI discovers the bundle and sandbox
binds it; sandbox tests constructors updated.
Evidence: G-C lane PASS on the disposable Ubuntu 26.04 VM (7/7 adversarial
matrix, positive CLI, strict language-resource refusal, forged marker), plus
fmt/clippy/423 local tests.
- Add stdlib/data/table.mq.md with select/filter/sort/append/set-cell/join/
group as value-returning .mq.md functions over table.columns/row/cell.
- Keep Value::Table logical semantics, GFM AST laziness and T0 physical
storage unchanged; no new table builtin or HostOp (ADR-0032).
- Add stdlib/tests/table.mq.md and a CLI test asserting shapes/order and
input immutability; refresh the bundle digest.
- Update architecture/status/spec/README/changelog and evidence.
Gate: fmt, clippy -D warnings, 420 tests passed.
- Delete HostOp::Print and StdHost::op_print; the print builtin only routes to
bundled io.写值 when Program.print_override is set, otherwise returns a
structured kernel.unavailable error (ADR-0031).
- Keep the 打印/print builtin name for arity/static validation; Value::display
remains only for CLI result rendering, not print execution.
- Teach the direct-runtime semantic harness to mirror loader stdlib injection
and import edges; replace runtime tests that used print with non-print
effects.
- Update spec/security/status/changelog/README, add ADR-0031 and evidence.
Gate: fmt, clippy -D warnings, 419 tests passed.
- Add Program.print_override and lazy stdlib injection: only programs that
call 打印/print load std:io and route to io.写值 (ADR-0030).
- Record resource.open/read/write/close as trace effect events so the stdlib
print path is auditable; HostOp::Print no longer runs on that path.
- Permit only stdio/stdout (existing console) in strict; file/network
resource opens remain permission.denied.
- Exclude std: modules from the human-readable checked-module count; update
the Python analysis consumer to accept std: instance ids.
- Add print-routing and strict-console tests, ADR-0030 and evidence.
Gate: fmt, clippy -D warnings, 418 tests passed.
WHY
- macOS/Windows failed to compile because `cfg!` left `linux::probe()` in the
type-checked branch (E0433).
- GitHub-hosted Linux can pass the strict probe and then fail the real launch
with EAGAIN; the CLI test treated the inspect snapshot as a permanent promise.
- The security matrix shared process-id-based scratch paths, so parallel
`cargo test --workspace` made its own tests clobber each other.
- Condition paragraphs silently ignored executable `Strong`/`Emph`, and
condition parse spans included the code-span backticks.
- The corpus had no native power/control-flow/inert fixtures and no independent
generic Tool consumers.
WHAT
- Dispatch strict detection through `#[cfg]` functions; add a non-Linux
compile/fail-closed regression test.
- Split `linux::run` into an injectable probe/spawn seam; test probe-OK ->
launch-EAGAIN returns LaunchFailed and never executes unrestricted.
- Make the Linux CLI contract accept only (a) successful isolated run or
(b) non-zero, diagnosed, fail-closed refusal with no project stdout.
- Give each security test a unique project/outside path and compile the helper
once.
- Reject executable roles in a condition paragraph; map condition expressions
from the literal bytes inside the backticks.
- Add 10 AST, 8 semantic, 4 compile-negative and 2 runtime-negative fixtures
for power, branch/loop conditions, source spans, inert prose/code fences and
error boundaries.
- Add `sample-view`/`sample-knowledge`/`sample-proof` independent Tool v1
packages and an end-to-end Analysis/Trace consumer test.
- Add a locked path-dependency content-tamper test.
TESTS
- cargo fmt --all -- --check
- cargo clippy --workspace --all-targets -- -D warnings
- cargo test --workspace --locked
- G-C VM lane (separate evidence commit/run)
CI_URL
- none from this host: the checkout has a Gitee remote and no GitHub
credentials. Windows/macOS CI remains UNVERIFIED.
BREAKING_CHANGE
- An executable node in a list-item condition paragraph is now a hard
`markdown.invalid_construct` error instead of being silently ignored.
SECURITY_SCOPE
- strict remains fail-closed; no downgrade, no new capability, L2 still
rejected. G-C still requires the dedicated self-hosted lane for CI-signed
evidence.
Strict mode now re-executes the CLI inside a Bubblewrap supervisor with
user/mount/PID/net/UTS/IPC namespaces, no-new-privs, all capabilities dropped,
a read-only /project, private /proc and /dev, rlimits, output capture and
wall-clock process-group cleanup. The child verifies PID 1, NoNewPrivs, empty
CapEff, an unshared uid map and loopback-only networking before project code.
- PlatformCapabilities::detect runs a real bwrap probe; no probe, no strict
- strict L1 supports pure Marqdo + Math; Foreign/ABI/worker/kernel/grants/trace
are rejected with exit 2 before sandboxing
- forged MARQDO_STRICT_ACTIVE is rejected; missing bwrap fails closed
- add adversarial helper, 7-test escape/resource matrix, seeded security lane
script and self-hosted security workflow
- executed G-C lane as uid 1000 in a disposable Ubuntu 26.04 VM: 7/7 PASS
plus positive CLI and refusal matrix; evidence in docs/evidence
- ADR-0021, spec/security.md, STATUS/COMPATIBILITY/README/CHANGELOG updated;
ADR-0019 remains for non-Linux/fail-closed rules
A document with an executable foreign.call is statically checked without a
marker side effect, then run to show the same provider does execute. This
guards the 'check/inspect cannot execute untrusted code' contract.
The macOS job failed with no_matching_artifact because the integration test
copied the Linux-only example manifest and built a Linux-named .so. Tests now
generate a manifest for the actual host triple, use the platform dynamic
library name and compiler flags, and never rewrite the tracked example
manifest.
- add a cross-platform no_matching_artifact test that runs without a C compiler
- add real tamper and ABI-major-mismatch rejection tests
- make worker fixtures platform-native; Windows remains explicitly unsupported
(no cc) rather than counted as a pass
- example build scripts emit host-specific build/ fixtures (gitignored)
- CI smoke points at the generated fixtures