# Compatibility and support matrix Snapshot: workspace version **0.1.0**, RFC-EXT-0001 tree on `feat/extensible-ecosystem`, no release tag cut. This file records what was actually verified and separates it from what is only implemented. Executed status is in [`docs/STATUS.md`](docs/STATUS.md); SHA-bound external evidence is under [`docs/evidence/extension/`](docs/evidence/extension/README.md). ## Language source syntax (breaking change) **The `.mq.md` source language is a breaking change.** The current contract is [RFC-LANG-0002](docs/architecture/RFC-LANG-0002-unified-semantics.md) (accepted by [ADR-0052](docs/adr/0052-unified-markdown-semantics.md)), with the normative summaries in [`spec/mapping.md`](spec/mapping.md) and [`spec/expression.ebnf`](spec/expression.ebnf): - H1–H6 headings declare `@exec`/`@knowledge` modes; unmarked headings inherit the nearest ancestor's mode and the document root is Knowledge. - Only an Exec H2 is a callable function. H2 Knowledge is inert and H3–H6 are non-callable sections. - In an Exec scope, `Strong`, `Emph` and inline `Code` are interchangeable carriers of one statement; the original emphasis role is gone. - Control flow comes from keywords in the payload (`if`/`else`/`while`/`end`/ `return`/`params(...)`). Ordered lists, bullet lists and block quotes are inert presentation containers. - There is no version selector, `--legacy` path or fallback mapper. Consequences for compatibility: - **Old pre-RFC `.mq.md` source is not executable.** A file that relied on `Strong` = execute, `Emph` = return, ordered list = branch, bullet list = loop, block quote = call or a first code-span signature must be rewritten by AST role (see `docs/migration/README.md`). A parse failure is a hard diagnostic, never a fallback to prose. - The Markdown parser profile stays `marqdo.md.v1`; only the Markdown→program mapping changed. Rendering of otherwise-ordinary Markdown is unaffected. - **Implementation state:** RFC-LANG-0002 is implemented by the frontend, expression parser, IR lowering, runtime and bundled stdlib. At `9c1723d` the workspace gate is `cargo test --workspace --locked`: 507 passed, 0 failed, 2 ignored, and the stdlib digest is regenerated and verified. See [`docs/STATUS.md`](docs/STATUS.md) and [`docs/evidence/2026-11-21-semantics-v2-green.md`](docs/evidence/2026-11-21-semantics-v2-green.md). ## Public protocol versions | Surface | Version | Compatibility rule | |---|---|---| | Markdown profile | `marqdo.md.v1` | Frozen parser/options. The RFC-LANG-0002 mapping rewrite keeps this profile; the source-language break is tracked above, not by a new profile id. | | Language / CLI | workspace `0.1.0` | Pre-1.0. The `.mq.md` source language changed incompatibly (RFC-LANG-0002); there is no old-syntax execution path. CLI flags may change with a changelog note; `strict` refusal is contractual. | | `marqdo.lock` | v4 | v3 is rejected with an explicit `marqdo lock` migration error; v1/v2 are rejected with a relock instruction; `run`/`call`/`check` never rewrite or fetch the lock. `extensions:` records manifest/artifact identity (integrity, not publisher auth). | | Analysis | v2 | Consumers reject unknown majors; incompatible field changes require v3. | | Trace | v2 | Binds to the exact Analysis bytes; unknown majors rejected. | | CLI Tool | v1 | Manifest schema, SemVer negotiation and whole-bundle digest are stable for v1. | | Plugin ABI | v1 | Struct layout/version negotiation frozen; `--trust-native-plugin` is required for in-process loading. The static manifest signature is authoritative; `run` reconciles loaded exports/signatures/owners/artifact digests exactly (`ext.plugin_binding_mismatch`); ABI v1 defaults are rejected. | | Resource Provider manifest | v2 | `schema_version: 2`, `abi: c-abi-1`, `transport: worker`; v1 is rejected (`ext.unsupported_provider_schema`), no silent migration. CLI `--provider`/`--allow-provider`; trusted worker, not an OS sandbox. | | Callable resolution | ADR-0054 | One registry + one binding pass; `check` and `run` bind the same `CallSiteKey`; no runtime name fallback. Import aliases colliding with builtin/plugin dotted namespaces are rejected. | | Analysis `calls[].state/target` | v2 (projection) | Now projected from the unique binding; official stdlib aliases appear as `function`. Schema/version unchanged; private binding table not serialized. | | Extension selection | lock v4 | `marqdo.yaml.extensions` only `./path` or `@alias/path`; declaration is not a grant; declared identity must match the lock (`ext.extension_lock_mismatch`). | | Foreign wire | v1 | One-shot request envelope; provider descriptors are explicit. | ## Platform / feature evidence Legend: **PASS** = executed on this snapshot with logs; **UNVERIFIED** = code is portable/tested locally but the native platform lane has not run here; **UNSUPPORTED** = deliberately not claimed; **FAIL-CLOSED** = request is refused. | Feature | Ubuntu Linux x86_64 | macOS arm64 | Windows x86_64 | |---|---|---|---| | Markdown profile / AST goldens (160) | PASS | UNVERIFIED (cfg fix + CRLF fix) | UNVERIFIED (cfg fix + CRLF fix) | | Rust interpreter / unified semantics (73) | PASS | UNVERIFIED | UNVERIFIED | | Addressable `Memory` P1 (ADR-0022) | PASS | UNVERIFIED | UNVERIFIED | | Resource streams CM-A06 (ADR-0025/0026: stdout + project file read/write) | PASS | UNVERIFIED | **FAIL-CLOSED** (`strict` refuses resource opens) | | `run` / `call` / `check` / `inspect` / `fmt` | PASS | UNVERIFIED | UNVERIFIED | | lock v4 path/Git graph + sync + tamper | PASS | UNVERIFIED | UNVERIFIED | | Extension selection/lock v4 (`extensions:`, identities, `inspect --extensions`) | PASS | UNVERIFIED | UNVERIFIED | | Callable single binding + `ext.import_namespace_conflict`/`symbol.unknown`/plugin reconciliation | PASS | UNVERIFIED | UNVERIFIED | | Official stdlib public aliases (print de-magic; byte-identical output) | PASS | UNVERIFIED | UNVERIFIED | | Resource Provider v2 CLI (`--provider`/`--allow-provider`, worker helper) | PASS (linux/x86_64; real C sensor + helper) | **FAIL-CLOSED** (`ext.platform_unsupported`) | **UNSUPPORTED** | | Capability handler registry (`fs.read` handler, audit, unavailable) | PASS | UNVERIFIED | UNVERIFIED | | External conformance repository (`marqdo-extension-conformance`, frozen CLI) | PASS (provisional development binary; release rerun pending) | UNVERIFIED | UNVERIFIED | | Analysis v2 / Trace v2 + Python consumers | PASS | UNVERIFIED | UNVERIFIED | | Tool Protocol v1 + 3 independent consumers | PASS | UNVERIFIED | UNVERIFIED | | Native ABI (`plugin inspect`, trusted call) | PASS (C fixture) | UNVERIFIED (host-native fixture) | **UNSUPPORTED** | | Worker ABI + `fs.read` bridge | PASS (Unix) | UNVERIFIED | **UNSUPPORTED** (Unix-gated) | | Foreign Python/Node | PASS (system `python3`/`node`) | UNVERIFIED | UNVERIFIED | | Foreign pinned environment binding | PASS | UNVERIFIED | UNVERIFIED | | `strict` Linux L1 (pure Marqdo + Math) | PASS, probe-gated, 7/7 VM lane | **FAIL-CLOSED** | **FAIL-CLOSED** | | `strict` L2 (Worker/Foreign/native) | **UNSUPPORTED** (flags refused) | **UNSUPPORTED** | **UNSUPPORTED** | The Ubuntu column is from this development host (Ubuntu 26.04 container) and a disposable Ubuntu 26.04 QEMU/TCG VM for the security lane. It is **not** a GitHub Actions result: this checkout has a Gitee remote and no GitHub credentials. A fresh local clone with `core.autocrlf=true` was used to reproduce the Windows checkout byte behavior. ## Strict L1 scope (ADR-0021) - Enabled only when the runtime Bubblewrap probe succeeds. Probe failure or a probe→launch race exits non-zero with a diagnostic and **never** falls back to `project`. - Inside the sandbox: user/mount/PID/net/UTS/IPC namespaces, no-new-privs, empty capabilities, read-only `/project`, private `/proc`/`/dev`/`/tmp`, rlimits and wall-clock/output supervision; the child verifies `PID 1`, `NoNewPrivs`, `CapEff=0`, a non-initial uid map and no non-loopback network. - Refused before launch: `--allow-read`, `--allow-write`, `--allow-foreign`, `--allow-plugin`, `--plugin`, `--trust-native-plugin`, `--kernel`, `--trace-file`. - Strict L2 (letting Worker/Foreign/native plugin run inside the sandbox) is not implemented and must not be inferred from L1 passing. ## Minimum environment - Rust 1.82+ (verified with 1.100.0). - Linux/macOS: a C compiler for Native ABI fixtures; Python/Node only for Foreign kernels; `git` for Git dependencies. - `strict` additionally requires Bubblewrap and a kernel/environment that permits user, mount, PID and network namespaces. See [`docs/security-gate.md`](docs/security-gate.md) and ADR-0021. ## RFC-EXT-0001 platform statements * Provider worker transport: linux/x86_64 only; macOS/Windows return `ext.platform_unsupported` (compile-only, fail-closed). The RFC's macOS provider lane is **not claimed**. * Windows Native/Worker ABI remains **UNSUPPORTED**; a Linux PASS does not substitute for it. * `strict` L1 continues to refuse plugins/providers/foreign kernels; strict L2 is not implemented. A worker is a trusted process, not an OS sandbox. * The external conformance suite is a mandatory **additional** release gate (`docs/releasing.md` §7); it does not replace G3/G4/native lanes. ## Explicitly unsupported in this candidate - Pre-RFC `.mq.md` source syntax (Strong-execute / Emph-return / ordered-list branch / bullet-list loop / block-quote call / first code-span signature). Old sources are a rewrite task, not a compatibility mode: there is no `--legacy`, `marqdo_semantics` selector or second mapper. - OS-level strict isolation on macOS/Windows (Linux only, probe-gated). - Strict L2: Worker/Foreign execution inside strict (refused in L1). - Windows Native/Worker ABI runtime support. - Automatic uv/npm/venv provisioning; only an explicitly provisioned, pinned directory is verified (and must contain a regular-file executable). - Registry/package publishing, JIT, Knowledge/Proof/View built-ins, sessions, and general-purpose CAS. The three `sample-*` tools are test fixtures for the generic Tool protocol, not product features. - Tagged Windows/macOS release archives: the native **build/test** matrix is green at `5fcc111`, but the tag/dispatch release-candidate job has not produced those archives. ## Release decision **DO NOT RELEASE.** The RFC-CI-0001 series fixed the platform `E0425` build break, the strict `--json` empty-stdout defect (ADR-0053) and the native Windows/macOS portability failures. Linux, Windows and macOS native jobs are green, and G4 is `MEASURED`/`WARN` on the designated Woodpecker agent (`1199c88`, 9/9 correctness-verified, pinned CPU). The release still lacks the **remote G3 security artifact** with a matching `tested_sha`; a local VM PASS is not a remote G3 proof. The G4 node is a shared powersave host, so its gate is provisional. See [`docs/STATUS.md`](docs/STATUS.md) §0.1 and [`docs/evidence/ci/README.md`](docs/evidence/ci/README.md).