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
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.
Provider v2 example (demo.sensor)
A resource provider is an external process/library pair: the CLI ships
marqdo-provider-worker, which loads this C ABI v1 library and speaks the
framed resource protocol. Nothing about demo.sensor lives in the Marqdo core,
and selecting the provider is not authorization.
./examples/provider-demo/build.sh # cc + rustc needed for the host triple
marqdo run examples/provider-demo/demo.mq.md \
--provider examples/provider-demo/build/provider.json \
--allow-provider demo.sensor
# => 5
Negative checks (all must fail before the resource call succeeds):
# No grant:
marqdo run examples/provider-demo/demo.mq.md \
--provider examples/provider-demo/build/provider.json
# A missing or non-sibling helper is fail-closed, never a PATH fallback.
# Unknown provider manifest version:
marqdo run examples/provider-demo/demo.mq.md --provider examples/provider-demo/provider.json
provider.json in this directory is a template with a zero digest; only the
generated build/provider.json names the real artifact and is runnable.