Files
marqdo-cli/docs/evidence/extension
cflmy 0b01cbd2a4 evidence(ext): SHA-bound frozen-CLI external conformance manifest; finalize RFC-EXT-0001 record
- docs/evidence/extension/6a7bb98.../manifest.json: tested_sha 6a7bb98,
  cli sha256 28e3776d..., fixture repo e4b7352c..., all 7 required categories PASS
- RFC-EXT-0001 status Implemented with PR-by-PR record and honest release caveat
- STATUS/CURRENT/COMPATIBILITY/evidence report bind the executed result
- workspace gate re-run: fmt/clippy clean, 599 passed across 67 targets

Code tree at 6a7bb98 is byte-identical; this commit adds evidence/docs only.
2026-11-22 00:48:39 +08:00
..

External-extension evidence

RFC-EXT-0001 §10.2/§11.3 requires SHA-bound proof that an unchanged CLI binary can use extensions from physically separate Git repositories. This directory holds that evidence.

  • schema.json — JSON Schema for the evidence manifest.
  • <40-hex-source-SHA>/manifest.json — generated by tools/ci/verify_extension_contracts.py; never hand-written.

Generation (from a clean fixture checkout and a release build of this repo):

cargo build --release --locked -p marqdo-cli
CLI="$(realpath target/release/marqdo)"
python3 tools/ci/verify_extension_contracts.py \
  --cli "$CLI" \
  --fixtures /path/to/marqdo-extension-conformance
python3 tools/ci/verify_extension_contracts.py \
  --validate docs/evidence/extension/<SHA>/manifest.json

The generator refuses to write evidence when:

  • the CLI binary hash changes between the start and end of the suite;
  • the fixture repository has uncommitted changes;
  • a required result is missing or FAIL;
  • UNSUPPORTED/SKIPPED is recorded without --allow-unverified and a report entry explaining the platform limitation.

A local or container run is not a substitute for the release gates in docs/releasing.md (G3/G4), and no tag is created by this evidence.