The workspace test suite includes python/node foreign kernels; the Rust image
has Python but not Node, so marqdo-foreign tests failed with KernelUnavailable.
- Add ADR-0039: keep stdlib in-repo while architecture is small; extraction is
a future trigger-driven option, not a pending gate. Update ADR-0028,
STATUS, architecture index, package/P2/completion evidence.
- Add .woodpecker.yml (fmt/clippy/test + release build) for ci.cflmy.cn.
- Add docs/development-credentials.md and ignore .secrets/ plus .env.local;
real credentials stay in the ignored local file and are never committed.
Gate: fmt, clippy -D warnings, 440 tests passed.
- Map every objective bullet (P2 closure, Compat-B/C, CM-A08/A09/A10/A11,
P4-P6) to commits, tests, ADRs and checked-in evidence.
- Record the final 440-test gate and strict VM lane result.
- Explicitly list external/unavailable items (GitHub CI URL, Windows/macOS,
external stdlib repo publication, plugin-Worker ABI binding, P6 optimizer)
so none is claimed as completed or CI-verified.
Gate: fmt, clippy -D warnings, 440 tests passed.
- 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
- enforce at most 64 capability requests and 64 KiB per serialized request
in both the worker handler and the host bridge
- return structured capability.budget_exceeded / request_too_large errors and
kill the worker on a host-side violation
- add a real C loop fixture and CLI test proving a runaway plugin is stopped
without producing file contents
- update ADR-0018, plugin-abi and STATUS
Replace the /bin/sh tool fixtures with a std-only fixture compiled by rustc,
and use platform EXE_SUFFIX for entrypoints. Windows/macOS workspace tests now
run the whole Tool protocol suite instead of skipping it. Keep C ABI/worker
and package/Git tests Unix-only and document that remaining gap.
- add request-scoped capability_request/capability_reply/capability_error
frames to the worker transport (ADR-0018); no C ABI change
- worker routes its capability handler through stdin/stdout, the host serves
requests inside the existing invoke deadline and binds identity from the
spawned worker, never from frame text
- both native and worker plugins now execute a granted fs.read through
ProjectFs with audit; unsupported capabilities return capability.unavailable
- add a real C capability plugin and CLI test for granted read and denial
- document the bridge and that strict OS isolation (H3-B) is still refused
- CapabilityBroker::execute separates authorization from execution; native
plugins requesting fs.read get real project file bytes through ProjectFs
- unsupported capabilities (fs.write/net/process/console/vendor without a
handler) return capability.unavailable instead of empty success
- keep audit decisions for granted/denied/unavailable without logging contents
- document that worker capability bridging, live ABI session identity and OS
isolation (H3-B) remain open; no G-C claim is made
- add environment_id/environment_digest/interpreter_version to KernelDescriptor
- require external CLI descriptors to pin an absolute executable and a full
provider digest
- verify the digest at registration and immediately before every spawn;
tampering after registration fails with ForeignError::Integrity before spawn
- validate digest formats and reject relative external entrypoints
- pin the example provider digest and add an integrity test
- document that uv/npm environment materialization and lock integration remain
open; strict isolation is unchanged and still refused
- add an independent schema job with a pinned Draft 2020-12 validator that
validates real Analysis v2/Trace v2/Tool artifacts and negative mutations
- tighten the tool schema (SemVer, package-relative entrypoint, non-empty
protocol arrays)
- run cargo test --workspace plus portable CLI/analysis/trace smoke and a
strict-refusal assertion on Windows and macOS
- record honestly that Tool/C-ABI/worker runtime coverage remains Unix-only
- replace the hand-rolled version matcher with semver; require valid tool
versions and marqdo ranges
- declare SupportedProtocols (tool 1, analysis 2, trace 2) and negotiate tool
Analysis/Trace declarations at install and dispatch; disjoint/empty sets fail
closed with tool.protocol_incompatible
- record a v2 whole-bundle manifest (path/size/sha256 + deterministic bundle
digest), copy exactly that bundle into staging, re-verify it, and recompute it
before every dispatch
- reject auxiliary-file, extra-file, missing-file and entrypoint tampering,
record/command mismatches, traversal and a source root record.json
- remove tools by detaching with rename before deletion
- expose negotiated protocol environment variables to declared tools
- update tool-v1 and STATUS; add negotiation/bundle tests
- bind traces to the logical project identity and the exact emitted Analysis
digest; every span-bearing event carries module_id
- add host TraceState budgets (100k events / 32 MiB defaults), CLI
--trace-max-events/--trace-max-bytes, terminal trace.truncated events, and a
final serialized byte cap; budgets never change run.status
- disable semantic recording when no trace is requested
- cap worker frames at 8 MiB, align request/result/capability wire caps, make
clean EOF distinct from protocol errors, and mark/kill a worker after a
transport failure instead of reusing it
- add trace-v2 spec/schema, independent trace consumer, CI check and tests
- record the S2/C state in STATUS
- add ProjectIdentity (manifest root instance or workspace snapshot digest)
and remove absolute-path root ids from Analysis bytes
- replace the resources count with an addressable array over the two real
marqdo-ir resource kinds (formula, code), including unit/span/payload digest
and code language
- project diagnostics by module/relative path/span, removing machine paths
- define the digest as SHA-256 of the exact emitted bytes so consumers can
verify it; Trace binds to the same digest
- add analysis-v2 spec and JSON schema, supersede v1, update the independent
Python consumer, schemas and docs
- tests: location-independent byte equality and resource addressing
RuntimeError and CallFrame now carry a logical ModuleId and an origin
(source/callsite). Errors are attributed at function/body boundaries so the
innermost callee module wins; argument-binding errors and host/plugin/foreign
boundaries are attributed to the caller callsite without fabricating a foreign
stack.
The CLI resolves (module_id, span) through LoadedProject::locate instead of
indexing every span against the entry file. Unknown modules and out-of-range
spans keep the module id and byte span but emit null line/file. Human output and
frames now point at the correct file.
Record the decision in ADR-0017 and supersede the ADR-0006 limitation. Add an
end-to-end imported-module division-by-zero test.
- lock the full transitive closure with per-instance alias edges, root
manifest digest, full content digests and structured path/git sources
- reject v1/v2 locks; validate ids, digests, edges, reachability and sources
- resolve every locked edge by (parent instance, alias) and fail closed on
missing locks/edges/records, digest or source drift and root drift
- require a lock for run/check/inspect when dependencies exist and map lock
errors to exit 1
- make sync strict in both modes, never rewrite the lock, and materialize the
whole closure with env.json schema 2
- verify Git cache markers, require full commit hashes and confirm HEAD
- stop add/remove from patching the lock; regenerate example locks
- update package-format.md and STATUS for S1
Add content_profile_version 1 with one selection shared by hash_tree and
materialization: exclude .git/.marqdo, include target, reject symlinks and
special files, propagate walk errors, enforce file/size/depth budgets, and use
a domain-separated length-prefixed encoding (fixes the old NUL-delimiter
ambiguity). Materialization hashes exactly the bytes it writes and verifies the
expected digest before publishing.
Record the decision in ADR-0016 and update the package-format hash contract.
The property test builds all fixtures in code but asserted that
tests/properties/ existed. Git does not track empty directories, so a fresh
clone failed before exercising the invariance checks. Drop the assertion and
the now-unused repo_root helper; keep every prose-invariance assertion intact.
Record the S0/H0 local gate and the pending CI URL in STATUS.
- move the staging package into docs/CORE_STABILIZATION_AND_ECOSYSTEM_GATE.md
- preserve the original package README as appendix C and delete the staging dir
- cross-reference the current-stage baseline from README, AGENTS, STATUS,
blueprint, M0.6 plan, audit and contributor guide
- pass workers an explicit temporary manifest so plugin.yaml naming is not a
hidden constraint
- remove temporary manifests after handshake
- reconcile STATUS with implemented multi-export, broker, worker, handle,
Git/env and CI behavior; document strict isolation as the remaining blocker
- add a hidden __plugin-worker mode that loads one native library in a child
process and serves length-prefixed JSON invoke frames
- add host WorkerPlugin with ready handshake, export cross-check, per-call
timeout and crash/EOF propagation
- route kind: worker without in-process trust; native still requires explicit
trust; wasm is rejected explicitly
- report worker_processes=true while keeping strict OS isolation unavailable
- test successful worker calls and worker crash isolation
- update plugin ABI spec and R2 status
- add runnable examples for an unknown-name Tool, multi-export plugin,
external kernel provider and same-name multi-version packages
- add JSON Schemas for Analysis v1, Trace v1 and Tool v1 and validate them in CI
- extend CI with protocol/consumer smoke tests and a Windows/macOS cargo check
- add --kernel provider descriptors and R6 example integration tests
- document the examples and update M0.6 status
- add content-addressed Git checkout cache for exact revisions; no hooks,
submodules or floating branches
- resolve transitive @alias imports from each package's own manifest
- materialize locked path/Git packages into .marqdo/env atomically and prefer
a matching env copy in the resolver
- make sync a real environment sync while keeping lock immutable
- kill Unix foreign-kernel process groups so grandchildren do not survive
- add Git/env/transitive integration tests and update package/security specs
- add check --emit with a deterministic, read-only semantic projection:
package-aware modules, signatures, normalized bodies, refs, calls,
diagnostics and source digests
- remove stale analysis artifacts on compile errors; atomic writes
- add run/call --trace-file with interpreter call/branch/loop/return events
and host effect events under one sequence; redact values and record error
status
- add Analysis/Trace v1 specs, ADR-0015 and an independent Python consumer
- add contract tests for determinism, stale artifacts, trace ordering/status
and secret redaction
- add tool install/list/remove and unknown-command dispatch without hardcoded
tool names or clap variants
- validate and copy local tool packages atomically, reject entrypoint escapes
and symlinks, record and re-verify SHA-256
- forward OsString args, stdio, cwd and exit status without a shell; never
execute PATH programs implicitly
- add black-box tests for arbitrary names, Unicode args, built-in conflicts,
traversal, version mismatch, tampering and PATH hijacking
- add ADR-0013 and mark R3 complete
- add PluginHandleTable with owner, run id and generation scoping
- reject forged, cross-owner, cross-run and post-unload handles
- reject any plugin_handle returned by plugin or foreign-kernel output,
including nested values
- add ADR-0014 and update value-wire/security specs
- register every plugin export by its complete dotted name; reject conflicting
loads atomically instead of overwriting the first namespace
- route plugin calls by full export name and expose loaded descriptors to the
runtime
- add CapabilityBroker for core grants and vendor policy, with audit records
- accept syntactically valid vendor capability requests in manifests while
still denying them until a trusted policy exists
- add check --plugin static signature validation without dlopen
- test multi-export C plugin routing, conflict rollback, broker decisions and
static arity rejection
- add KernelDescriptor/KernelRegistry with built-in Python/Node providers
- route run/call through the registry; external providers need an explicit
executable and wire version
- expose provider registration on StdHost and use it in the foreign adapter
- add mocklang registration/call, duplicate-label, wire-version and timeout tests
- update spec/foreign.md and M0.6 progress
- add CallableId/Descriptor/Origin and CallableRegistry in marqdo-ir
- include builtins, Marqdo functions and declared ABI exports in one static
lookup model with deterministic conflict rules
- validate declared plugin export signatures in the frontend without loading
any shared library
- add registry and frontend static-plugin-signature tests
- replace path-only ModuleId with {instance, relative_path} and canonical
<instance>::<path> encoding
- add PackageResolver/ResolvedPackage in marqdo-package for path sources;
hash package trees deterministically for content-addressed instance ids
- move import resolution out of the CLI loader; reject package escapes
- emit lock_version 2 with instance ids and migrate v1 lockfiles
- update references/package-format specs and the function-ref golden
- add package resolver tests for stable identity across path moves
- move the revision package into docs/ and spec/, preserving all content
- record the M0.6 plan/audit cross-references and Proposed status
- correct stale STATUS claims about CI, console capability and check --refs
- add Accepted ADRs 0008-0012 for package identity, callable resolution,
plugin export routing, capability broker and kernel providers
- record the passing R0 baseline gate (fmt, clippy, workspace tests)
Complete the documentation set for the M0.5 toolchain, grounded in the code:
- spec/references.md: import/reference/call edges, identities, loader rules,
anchors, `ref` resolution/ambiguity, `check --refs` validation.
- spec/value-wire.md: exact wire_version 1 typed encoding, integer-as-decimal
string rule, special floats, limits and exact float round-trip.
- spec/security.md: modes (strict refuses without OS isolation), capabilities,
path rules, budgets, tracing, foreign process caveats, plugin trust.
- spec/package-format.md: marqdo.yaml/lock formats, validation, lock/sync,
unsupported registry/git/environment work.
- spec/plugin-abi.md: ABI v1 layout/ownership/negotiation, manifest/artifact
rules, wire envelopes, loader lifecycle, trust boundary, SDK/C demo, and the
implemented CLI plugin-invocation flow with its limitations.
- spec/math.md and spec/foreign.md: the implemented math subset and the
foreign request/response/timeout/capability contract.
- docs/adr/0001..0007: accepted decisions for the span foundation, inert
executables outside function bodies, ref ambiguity (S-07), strict refusal,
AST normalization, CLI contract and BigInt/typed wire (S-08).
- docs/contributor-guide.md: repo map, workflow, fixture/golden updates,
quality gate, ADR/commit policy.
- docs/STATUS.md: P0-P7 matrix with evidence, open items and the blueprint §18
Alpha checklist (conclusion: not yet Alpha-complete), including known
divergences rather than overclaims.
- README.md rewritten from "design-only starter" to the working implementation
with quickstart, implemented phases, deliberate limits and doc index.
- AGENTS.md: updated pointers/workflow only; architectural rules unchanged.
- Consistency fixes in spec/mapping.md/evaluation.md (inert emph outside
functions, unsupported math.simplify/differentiate).
- host: `打印` checks the console capability at the execution point (pure and
project modes grant it, but the boundary is now real instead of decorative).
- cli: `marqdo call --json` reports "command":"call" instead of "run".
Non-error diagnostics (for example `markdown.inert_executable` for a would-be
execution node outside any function body) are now printed to stderr before
execution and included in `--json` run output, instead of being silently
hidden on a successful run.
Findings from the conformance corpus workstream, all fixed at the source:
- value/wire: enable serde_json's float_roundtrip so typed wire floats keep
their exact digits across foreign/plugin boundaries (Python pi*9 now stays
28.274333882308138).
- host: default interpreter stack budget lowered to 128 frames so deeply
recursive documents hit a structured resource.exhausted instead of exhausting
the native debug-build Rust stack; --stack remains available.
- frontend/map: calling an external HTTP(S) link is reported as ref.unresolved
(consistent with other unresolvable call targets) instead of math.unsupported.
- frontend/analyze: invalid front matter emits a single frontmatter.invalid
diagnostic (the YAML error is not repeated by the imports pass).
- spec/mapping: clarify that would-be execution nodes outside any function body
are inert with a markdown.inert_executable warning (no "return outside a
function" hard-error claim).
- tests: add the conformance corpus and harness (150 AST goldens, 36 semantic
goldens, 48 hard-error + 6 warning + 10 runtime-error negatives, CLI/module/
plugin integration tests, prose-invariance properties) and update the
three reported observations to the fixed behaviour.
Blueprint section 4.2: reference edges are static, never execution.
- For every loaded document, resolve same-document anchors, relative file
links and target anchors (analysing referenced files statically without
executing them); unresolved targets produce `ref.unresolved` errors with
source spans.
- External HTTP(S) links are treated as external references, not errors.
- `inspect --refs` continues to print the resolved edge graph as JSON.
Blueprint section 10 / P6: exports of an explicitly trusted plugin are callable
from a `.mq.md` file through a bound namespace.
- host: StdHost::load_plugin requires an explicit trust decision and a granted
plugin capability, loads the native artifact through the ABI v1 loader with
no capability handler (all plugin host-capability requests denied), and
dispatches HostOp::PluginInvoke through the typed wire request/response.
In-process native code is documented as sharing the host address space; no
isolated worker transport exists in this build.
- runtime: a qualified call whose base is not a local value, import alias or
builtin namespace is routed to the plugin namespace; plugin calls take named
arguments only and plugin values become Marqdo values (Unit when absent).
- cli: run/call gain `--plugin <path>`, `--trust-native-plugin` and reuse
`--allow-plugin <package>`; missing trust/grant/loaded namespace surface as
structured errors.
- frontend: member-call bases are namespaces (builtin/import/plugin), never
inferred parameters, so `solver.add(...)` does not invent a parameter.