Files
marqdo-cli/docs/evidence/extension/README.md
T
cflmy 1f6fd644a0 feat(ext): single callable binding, provider v2 CLI, capability handlers, stdlib aliases
Implements RFC-EXT-0001 PR-00..PR-07 first pass:
- CallSiteKey/CallBindingTable + one frontend binding pass; runtime dispatch by identity
- prepare composition root shared by check/run/inspect/Analysis; exact plugin reconciliation
- provider.json v2 --provider/--allow-provider worker CLI with fail-closed verification
- capability handler registry with real fs.read and audit
- verified stdlib public aliases replace print_override/AST scan
- docs: specs, ADR-0054/0055/0057/0058, README, CI/release gates, evidence

PR-04 extension selection/lock v4 and final frozen-binary evidence remain.
2026-11-22 00:17:36 +08:00

1.2 KiB

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.