Files
marqdo-cli/docs/developers/release-limits.md
T
cflmy 2c7c4f31e7
Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
ci/woodpecker/push/main Pipeline was successful
ci/woodpecker/manual/performance Pipeline was successful
CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
release(3.0.0-beta.1): product version migration, beta gates, archive tooling and developer docs
REL-01: workspace/CLI/Analysis product version 3.0.0-beta.1 with updated
Cargo.lock; project.marqdo is enforced against the running core with
package.marqdo_range_invalid/package.marqdo_incompatible fail-closed
diagnostics; Tool SemVer prerelease negotiation tests; init template and
examples use the beta range. Verify init derives the project name from the
target directory instead of falling back to 'example'.

REL-02: beta support matrix is Linux x86_64 only; macOS/Windows are explicitly
experimental/unclaimed; strict policy and G4 Beta-only WARN are documented for
the release evidence.

REL-03: deterministic release packaging (tools/release/package.py) ships the
CLI and provider worker together with SOURCE_SHA, RELEASE_INFO.json,
known-limitations, specs, developer docs, examples incl. built plugin/provider
artifacts and consumers; tools/release/smoke.py cold-install tests the archive.

REL-04: docs/developers entry pages; corrected and self-contained third-party
integration handbook; stale Proposed/native-only/informational spec claims
fixed; release/status/compatibility/changelog/releasing docs updated.

REL-05: release_evidence.py gains an explicit beta profile
(BETA_RELEASE_CANDIDATE) distinct from the stable profile; Woodpecker build
step now packages and smoke-tests the archive on every pipeline.

Adds a runnable Resource Provider v2 example and corrects check --emit to
Analysis v2.
2026-11-22 02:31:32 +08:00

4.7 KiB

Marqdo 3.0.0-beta.1 — known limitations

This file ships in the release archive as KNOWN_LIMITATIONS.md. It is part of the release record: the beta support claim is exactly what is written here. Items marked unsupported must fail closed, not be silently emulated.

Platform support

Platform Beta status Notes
Linux x86_64 (glibc) Supported release platform The archived marqdo and marqdo-provider-worker binaries target x86_64-unknown-linux-gnu and are the only binaries this release claims.
Linux aarch64 Not built No release artifact; source may build.
macOS (arm64/x86_64) Experimental, not claimed Core CLI may work, but no macOS provider worker, no native plugin ABI claim and no macOS release artifact.
Windows x86_64 Experimental, not claimed Core CLI may compile/run; the plugin/provider C ABI and provider worker are not claimed.

pure and project are language execution modes, not OS sandboxes. project may access resources only through explicit grants, but it runs as the user and is not a security boundary against hostile code.

strict isolation

strict is Linux-only and probe-gated. The beta release claims it only when the same-SHA G3 evidence recorded in docs/evidence/ is present; otherwise this file and the release notes must say strict: unsupported and the runtime must fail closed (no project code executes).

Even when available:

  • strict L1 covers the pure language plus native Math;
  • strict L2 (Worker/Foreign/Provider inside strict) is unsupported and every such flag is refused with exit 2;
  • rlimits are used for resource limits, not cgroup-v2 accounting;
  • the network is denied with a network namespace, not a seccomp allowlist;
  • a PASS is evidence for isolation correctness, never for performance.

Extensions

  • Callable plugin ABI v1: native and worker transports exist. Native loads into the host process and requires the explicit unsafe --trust-native-plugin; a C ABI is not a sandbox. Worker is crash isolation with handshake/call timeouts, not an OS sandbox. Wasm, hot unload and a full worker capability broker are unsupported. Windows C ABI is not claimed.
  • Resource Provider v2: Linux x86_64 worker transport only. The marqdo-provider-worker helper must be next to the marqdo executable; missing/renamed helpers fail closed (ext.worker_unavailable) and PATH is never consulted. A provider is not a sandbox.
  • Foreign kernels: any language can be registered with kernel.json, but the kernel process is a normal child process; it is not sandboxed, and the host must refuse unauthorized, digest-mismatched, timed-out or wire-incompatible kernels.
  • CLI tools: a tool is an ordinary user-authorized executable and does not inherit pure/project/strict guarantees from the documents it reads. MARQDO_BIN, MARQDO_TOOL_PROTOCOL, MARQDO_PROTOCOL_ANALYSIS and MARQDO_PROTOCOL_TRACE are the only helpers the CLI injects.
  • Extension selection (marqdo.yaml.extensions, lock v4) is never authorization. --allow-plugin, --allow-provider and --allow-foreign are still required.

Compatibility and versioning

  • 3.0.0-beta.1 is a prerelease, not stable and not LTS. Breaking changes inside the 3.0 beta series are allowed and announced in the changelog.
  • The product version is independent of protocol versions: Analysis v2, Trace v2, Tool v1, Plugin ABI v1, Foreign wire v1, Provider manifest v2 and lock v4 keep their own major numbers. Do not infer them from 3.0.0-beta.1.
  • The official bundled stdlib keeps its independent package version 0.1.0. A plugin .mq.md package version such as 0.1.0 is also independent.
  • project.marqdo in marqdo.yaml is enforced in this release. SemVer prerelease rules apply: >=3.0.0,<4.0.0 does not accept a beta core; beta users must declare a prerelease range such as >=3.0.0-beta.1,<4.0.0.
  • Old cflmy/marqdo source syntax, package format and plugin ABI v2 are not compatible. There is no --legacy or downgrade path; migration is a separate documented workflow.

Artifact integrity

Archives are accompanied by SHA256 checksums and RELEASE_INFO.json (source_sha, target triple, toolchain, binary hashes). Checksums prove content integrity only; they are not a publisher signature. A digest obtained from an untrusted Git URL does not make the code trustworthy.

Deliberately deferred

strict L2, Wasm plugins, macOS/Windows provider worker, automatic uv/npm environment creation, a distributed package registry, JIT execution, built-in Knowledge/Proof/View commands, a mature async/concurrency model, and platform installers. The planned direction is external Tool repositories consuming the public protocols, not new core commands.