- Add the separate marqdo-provider-worker binary: loads one trusted c-abi-1
shared library and serves the ADR-0035 framed-JSON resource protocol, with
fail-closed startup and no in-process fallback (ADR-0038).
- Reuse StdHost::register_worker_resource_provider; language still sees only
resource.* and project-mode/name grants.
- Compile a C test provider and run open/read/write/close through the helper;
cover missing-library fail-closed. Trusted process boundary, not a sandbox;
existing plugin-Worker ABI binding remains open.
- Add ADR/spec/status/README/changelog/evidence; workspace member and tests.
Gate: fmt, clippy -D warnings, 440 tests passed.
- Add a marqdo.provider schema v1 loader (schema/version/ABI/platform library)
and StdHost::register_provider_package, reusing the C ABI adapter and shared
kind/name checks (ADR-0037).
- Add a compiled-provider + provider.json installation test; language use still
requires project mode and allow_resource_provider.
- Update ADR/spec/status/README/changelog and evidence; no registry, signature
or CLI install is claimed.
Gate: fmt, clippy -D warnings, 437 tests passed.
- Build a second C provider reporting ABI v2 and assert registration fails
with resource.unsupported.
- Assert pure/strict refuse a registered C provider kind with permission.denied.
- Refresh the C ABI evidence/test README.
Gate: fmt, clippy -D warnings, 436 tests passed.
- Add the frozen marqdo_resource_provider.h ABI (version + open/read/write/
close/last_error) and a libloading-based host adapter with version/symbol
checks and callsite-attached host errors (ADR-0036).
- Add StdHost::register_c_resource_provider using the same kind/name validation
and project-mode name grant as the in-process/worker providers.
- Compile a C shared-library test provider; cover round-trip and fail-closed
missing-library behavior. Trusted native code, not a sandbox; plugin-Worker
binding remains open.
- Update ADRs/spec/status/README/changelog and evidence.
Gate: fmt, clippy -D warnings, 435 tests passed.
- Add a host-managed helper process speaking framed JSON (4-byte BE length)
with ping/open/read/write/close/shutdown, max 1 MiB frames and structured
error mapping (ADR-0035).
- Add StdHost::register_worker_resource_provider using the same protocol,
kind-conflict and name-grant checks as the in-process provider; pure/strict
refuse provider kinds.
- Tests spawn a Python helper and cover round-trip, grant/mode denial and
missing-program failure; no parser/Value/runtime/HostOp change.
- Update ADR/spec/status/README/changelog and evidence; C ABI binding remains
open.
Gate: fmt, clippy -D warnings, 433 tests passed.
- G-C lane now runs a .mq.md TCP resource open under strict and requires
permission.denied, and rejects the --allow-net grant at the strict flag
boundary.
- Complements the existing file-resource refusal and host TCP strict test.
- 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.
- tools/pack-stdlib.py builds a byte-deterministic
marqdo-stdlib-0.1.0.tar.gz (fixed metadata, gzip mtime 0) plus a schema-tagged
descriptor with tree digest, archive SHA-256 and file list.
- Verified repeated builds are identical and the extracted tree digest matches
stdlib.json; archive is for the future external repo, not the CLI loader.
- Update ADR-0028, status/changelog/tests README and evidence.
Gate: fmt, clippy -D warnings, 430 tests passed.
- tools/perf/bench.py builds the release CLI and measures 7 .mq.md workloads
three times with wall time and peak RSS, validating --json success.
- Check in the schema-tagged JSON report and interpretation; no bytecode/JIT/
native backend was added, so P6 remains baseline-only, not complete.
- Update STATUS/changelog/tests README.
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.
- Checked-in raw G-C lane log for 00bdcad: 7/7 adversarial helper matrix,
positive CLI (Compat-C print via bundled stdlib), strict file-resource
refusal, external-surface rejection, forged-marker rejection, lane PASS.
- Evidence documents the read-only /run/marqdo-stdlib bind, strict stdio-only
policy, refused file/TCP/provider resources, and the remaining no-CI-URL /
Windows/macOS limits.
- STATUS updated to the current 426-test gate and 00bdcad strict result.
Gate: fmt, clippy -D warnings, 426 tests passed; VM lane PASS.
- 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 ResourceProvider v1 trait with name/protocol/kinds/open/read/write/close;
host still issues the opaque language Resource handle, provider tokens stay
private.
- Add StdHost::register_resource_provider with protocol/version, reserved-name
and duplicate-kind checks; add Capabilities.allow_resource_provider grants.
- Provider kinds are project-mode only; pure/strict refuse them; in-process
providers are trusted and not a sandbox (ADR-0033).
- Reuse resource.* and Result shapes; no parser/Value/runtime/HostOp changes.
- Add mock read/write provider and rejection tests, docs/spec/status/evidence.
Gate: fmt, clippy -D warnings, 423 tests passed.
- 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.
- Replace the JSON number scanner with sign/integer/fraction/exponent
scanning; return Int or Float via 整数/小数 and reject missing digits.
- Add 片段/格式化文本/格式化列表/格式化对象/格式化 recursive formatter.
- Extend fixture 62 with floats ({1,2.5,-3e2,4E-1,{a:1.0},x}) and a compact
round-trip string.
- Update P2 status: only the separate stdlib package and frozen-CLI closure
lane remain.
Gate: fmt, clippy -D warnings, 407 tests passed.
- Add alloc.double_free detection to the .mq.md free-list allocator and a
fixture assertion for a second free returning a recoverable Result.
- Add table group fixture 69 (table.row -> Map of value lists).
- Add Int matrix-multiply fixture 70 for C12 layout/iteration.
- Update counts and P2 evidence/status docs.
Gate: fmt, clippy -D warnings, 407 tests passed.
Completes the release-status updates that were staged separately from the
evidence files. Code under test is unchanged from 8af7262 (G-C 7/7, workspace
47/47); final HEAD differs only by documentation.
CI_URL: none from this host (Gitee remote, no GitHub credentials).
The convergence evidence was first recorded against f075c96. The completed
tree is 8af7262 (docs/workflow on top of the same code), and the G-C lane and
workspace suite were re-run from a clean `git archive 8af7262`. Rename the
evidence and RC reports to the final SHA and update their archive/checksum
hashes.
Source under test: 8af72620f1
G-C: 7/7 + positive CLI + forged-marker rejection PASS (ordinary user, VM)
Workspace: 47 test binaries, 0 failed
RC: marqdo-0.1.0-x86_64-unknown-linux-gnu.tar.gz,
sha256 5a42d83737c9715986f36b105feb7419a677d98f913f00e84ac19f1d4847733d
CI_URL: none from this host; remote gates remain the blockers.
WHY
- The code fixes existed locally without same-SHA release material; the G0..G12
gate matrix, G-C VM evidence, RC artifact and explicit non-claims must be
reviewable together.
- The release-candidate workflow packaged no consumers and did not verify its
own checksum in the clean-install directory.
WHAT
- Record the current Linux/VM evidence at f075c96 and keep remote CI/G-C as
UNVERIFIED; overall decision DO NOT RELEASE.
- Add G-C evidence (7/7 + positive CLI + 47-binary workspace run), RC report
with gate matrix, clean-install and checksum result.
- Update STATUS, COMPATIBILITY, CHANGELOG, README, tests/README, mapping spec
and releasing procedure for the new condition/span/power/Tool behavior.
- Harden release-candidate packaging: include tests/consumers, SOURCE_SHA,
rustc -vV, verify the checksum before extraction, and run independent
Analysis/Trace validation from the extracted archive.
- Record the local convergence note in NEXT_RELEASE_CI_CONVERGENCE.md.
TESTS
- Local fmt/clippy/workspace PASS; G-C VM PASS at f075c96.
- Linux RC: sha256 -c OK and clean-install smoke PASS.
CI_URL
- none: Gitee remote, no GitHub credentials. Windows/macOS and same-SHA G-C CI
remain the blocking gates.
BREAKING_CHANGE
- none in this docs/workflow commit.
SECURITY_SCOPE
- strict remains fail-closed; no new capability or platform claim. G-C is
local-VM evidence, not a CI-signed security URL.
The lane hard-coded target/debug/marqdo, so a reproducible run from a clean
git archive with an external CARGO_TARGET_DIR built the binary and then
reported a false missing-binary failure.
TESTS: bash -n tests/security/run-lane.sh; G-C lane on a clean archive.
CI_URL: none from this host (Gitee remote, no GitHub credentials).
SECURITY_SCOPE: unchanged; the lane still requires an ordinary user and 7/7.
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.
Adds the QEMU/TCG cloud-image, NoCloud seed, guest setup, lane invocation and
self-hosted runner registration steps. No host protections are disabled; the
packaged Bubblewrap AppArmor profile is used.
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
Records the tested code SHA, full local gate, Windows autocrlf reproduction,
release-candidate clean-install results, and the container limits that make a
non-root/namespace G-C run impossible on this host.
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.
- adopt docs/STABLE_RELEASE_IMPLEMENTATION.md as the single next-phase plan
- archive the stale M0.5 status snapshot under docs/history/
- record real local gate results, the red baseline CI, the Windows autocrlf
reproduction and the unresolved macOS/native-CI status
- add COMPATIBILITY.md (protocol versions + honest platform matrix),
CHANGELOG.md, dual license files, docs/releasing.md and docs/security-gate.md
- keep strict fail-closed: document the container EPERM/read-only cgroup probe
and the exact G-C requirements instead of claiming isolation
- document foreign environment binding (ADR-0020) and add a release-candidate
CI job that is gated on all platform jobs
A verified environment_dir was only prepended to PATH, so built-in providers
still ran the host interpreter and external entrypoints could live outside the
verified tree.
- external entrypoints must resolve inside environment_dir
- built-in providers cannot be bound to an environment (fail closed)
- bound children get exactly the environment bin on PATH, no host fallback
- declared interpreter_version is verified against the resolved program
- built-in descriptors now also run environment validation
- ADR-0020 + spec/foreign.md document the binding and limitations
- positive/negative tests for binding, outside-entrypoint, builtin binding and
version drift
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
The Windows CI failure was a checkout byte-identity problem, not a Markdown
semantics change: CRLF goldens compared with LF parser output produced
'0 line(s) differ'.
- add .gitattributes: text files are LF, native products are binary, and the
intentional CRLF fixture stays a byte fixture
- report the first differing byte and whether only line endings differ
- fail early when a golden contains CR instead of the opaque mismatch
- assert exactly one CRLF fixture and that its golden is canonical LF
- add a markdown test proving CRLF/LF have equal structure while spans remain
byte offsets into the original source
Add ADR-0019 freezing the strict availability contract: strict remains
unavailable with an actionable reason on every platform until runtime probes
and filesystem/network/process/resource escape tests pass in a dedicated
security lane. Add a CLI test asserting inspect --platform reports unavailable
and worker processes are not presented as isolation. No G-C claim is made.
- add environment_dir to KernelDescriptor and verify its deterministic
file-set digest at registration and immediately before every spawn
- reject missing digests, relative/missing dirs, symlinks, special files and
oversized environments; tampering fails with EnvironmentIntegrity
- inject MARQDO_FOREIGN_ENV and prepend <env>/bin to PATH for the child
- add a real provider test covering success and post-registration tampering
- document that uv/npm environment generation and lock-v3 integration remain
open