Files
marqdo-cli/docs/evidence/2026-11-20-provider-package.md
cflmy 974102dfc3 feat(host): add provider package manifest v1
- Add a marqdo.provider schema v1 loader (schema/version/ABI/platform library)
  and StdHost::register_provider_package, reusing the C ABI adapter and shared
  kind/name checks (ADR-0037).
- Add a compiled-provider + provider.json installation test; language use still
  requires project mode and allow_resource_provider.
- Update ADR/spec/status/README/changelog and evidence; no registry, signature
  or CLI install is claimed.

Gate: fmt, clippy -D warnings, 437 tests passed.
2026-11-20 23:28:30 +08:00

1.6 KiB

RFC-CM CM-A09 evidence: provider package manifest v1

Date: 2026-11-20 (Asia/Shanghai) Repository: marqdo-cli Baseline: 5e5c3a8 plus this step's changes. Decision record: ADR-0037 Related: C ABI provider, STATUS §5. Scope: local manifest installation; no registry/signature/Worker binding.

Manifest

{
  "schema": "marqdo.provider",
  "schema_version": 1,
  "name": "cabi",
  "kinds": ["cabi.sensor"],
  "abi": "c-abi-1",
  "library": {"linux": "libecho_provider.so", "default": "libecho_provider.so"}
}

StdHost::register_provider_package validates schema/version/ABI, resolves the platform library relative to the manifest, loads it through the ADR-0036 C ABI adapter and registers it through the shared kind/name checks. Language use still requires project mode and allow_resource_provider("cabi").

Test

crates/marqdo-host/tests/c_provider.rs::provider_package_manifest_installs_a_c_abi_library:

  1. compile the C provider with cc -shared;
  2. write provider.json next to it;
  3. register_provider_package(&manifest) succeeds;
  4. resource.open("cabi.sensor", ...) and resource.read return c-.

Existing C tests cover version mismatch, missing library and pure/strict refusal. No parser/Value/runtime/HostOp change was needed.

Not done

  • Provider registry/download, signatures, dependency resolution, semver.
  • CLI install/uninstall commands; installation is host embedding API only.
  • Untrusted-provider isolation, strict-mode providers, plugin-Worker binding.
  • Windows library build lane.