Update status, compatibility, changelog, README, architecture overview,
ADR status, migration guide, contributor/CI/security/release notes and
the per-file inventory from 'migration pending' to the verified state:
- language SHA ffd1cc9: fmt/clippy clean, workspace 501 passed / 0 failed
/ 2 ignored, stdlib digest regenerated and pack-verified
- green evidence report added; the prior intermediate evidence is marked
superseded
- inventory regenerated: 1015 classified files, 0 pending
- explicit non-claims: Windows/macOS native lanes and the disposable-VM
strict lane were not re-run at this SHA, so the release decision remains
DO NOT RELEASE
Verified: cargo test -p marqdo-cli --test docs_consistency (4/4) and
git diff --check.
2.1 KiB
CI/CD
Current setup
- Git remote:
https://git.cflmy.cn/cflmy/marqdo-cli.git - Woodpecker:
https://ci.cflmy.cn - Pipeline definition:
.woodpecker.yml - Credentials are local-only and ignored; see development-credentials.md. Do not put tokens in pipeline files or commit messages.
The default Docker pipeline runs on push and pull request:
test:
rustup component add clippy rustfmt
apt install curl/ca-certificates + Node.js 22
cargo fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace --locked
build (depends on test):
cargo build --release --locked -p marqdo-cli
Node.js 22 is required because the optional foreign-kernel tests use ES-module syntax; Debian bookworm's Node 18 fails those tests.
Language contract note.
cargo test --workspaceincludes conformance fixtures that execute.mq.mdsource under RFC-LANG-0002. The implementation, stdlib digest and corpus are green atffd1cc9; a red executable-source suite is a real regression, not an expected migration state. Do not "fix" it by restoring the old mapper or regenerating goldens; seeSTATUS.md. The pipeline definition itself (fmt/clippy/test/build, security lane, platform gaps) is unchanged.
What this pipeline does not cover
- Strict security lane: needs a disposable VM/self-hosted runner with Bubblewrap/AppArmor namespace support. See security-vm.md. The Docker pipeline is not an OS-isolation proof.
- Windows/macOS native lanes: no runners are configured.
- Release publication/signing: no release job is defined.
Local reproduction
export PATH="$HOME/.cargo/bin:$PATH"
cargo fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace --locked
cargo build --release --locked -p marqdo-cli
Local API/trigger
The ignored .secrets/dev.env may contain a Woodpecker API token for local
queries/triggers. The token is not needed by the pipeline itself and must never
be committed.