- 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
- 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
- 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
- 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.
- `marqdo add <name> --path <dir>` / `--git URL --rev SHA` and
`marqdo remove <name>` edit marqdo.yaml only after validating the dependency
source (path-relative, git pinned by exact rev, no duplicate entry).
Removing a dependency also drops its stale lock entry; locking stays an
explicit step so no version changes happen silently.
- Manifest serialization omits empty dependency/plugin maps and empty
capability requests, keeping generated manifests readable and stable.
Create the Marqdo CLI Rust workspace with the module boundaries from the
development blueprint (section 11):
- marqdo-span: byte spans and line/column mapping shared by every layer
- marqdo-value, marqdo-expression, marqdo-markdown, marqdo-ir
- marqdo-frontend, marqdo-runtime, marqdo-host, marqdo-sandbox
- marqdo-math, marqdo-foreign, marqdo-package
- marqdo-plugin-abi, marqdo-plugin-sdk
- marqdo-cli (binary `marqdo`)
Pin the Markdown parser exactly (comrak =1.0.0, no default features) so the
frozen profile can never drift silently. Dependencies are centralized in
workspace.dependencies; no crate is allowed to add its own version of a shared
dependency.