- marqdo.yaml.extensions accepts only ./path or @alias/path, resolves to a regular file inside its owning package, never grants - lock_version 4 records plugin/kernel/provider manifest+artifact identity; v3 requires explicit 'marqdo lock' migration; sync/check/run compare identity - check stays static; run re-verifies artifact bytes; pure/strict refuse - inspect --extensions reports declared/locked identity, plugin descriptors and stdlib aliases with authorization 'not_granted' - black-box extension_selection suite (13) + package-layer tests; specs/ADR-0056 - workspace gate: fmt/clippy clean, 599 passed across 67 targets
Multi-version package example
Two directories declare the same package name geometry at versions 1.0.0
and 2.0.0. They receive different package-instance ids and different
ModuleIds; importing both aliases is not an implicit override.
marqdo run examples/packages-multi-version/index.mq.md
marqdo lock
marqdo lock must be run from the example directory because it discovers the
project from the current working directory:
(cd examples/packages-multi-version && ../../target/debug/marqdo lock)
The lock records both content-addressed instances; no version silently wins.