Files
marqdo-cli/docs/evidence/ci
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
..

CI release-evidence manifests

docs/evidence/ci/<full-40-hex-sha>/manifest.json is generated by tools/ci/release_evidence.py (schema marqdo.release-gates.v1) and recorded for the release. Do not hand-edit a manifest into PASS.

Two profiles are explicit in the manifest (profile field):

  • stable — required gates are linux, windows, macos, strict_vm; every one must be PASS on target_sha, and performance must be PASS/WARN.
  • beta — the supported scope is declared by COMPATIBILITY.md (3.0.0-beta.1: Linux x86_64 only). Required gates are linux, strict_vm, extension, clean_install, version_compat; windows/macos must be explicitly present as UNSUPPORTED (not silently omitted); strict_vm may be UNSUPPORTED only when the tested policy is an explicit fail-closed refusal; performance may be WARN with the environment recorded. Decision: BETA_RELEASE_CANDIDATE.

Rules:

  • every gate records its own tested_sha; it must equal target_sha;
  • skipped, cancelled, queued, timed-out, missing or older-SHA jobs are UNVERIFIED/FAIL, never PASS;
  • strict_vm needs a real disposable-VM strict-evidence.json (schema marqdo.strict-evidence.v1) with outcome: PASS, non-root uid and the same SHA; a URL alone is not enough;
  • performance needs a MEASURED report from the fixed node; TCG/QEMU or development-container numbers are not a baseline;
  • release_decision is RELEASE_CANDIDATE (stable) or BETA_RELEASE_CANDIDATE (beta) only when every required gate is satisfied with the same SHA. Anything else is DO_NOT_RELEASE.

The manifest is evidence, not permission to tag; owner approval is separate.