- `marqdo add <name> --path <dir>` / `--git URL --rev SHA` and
`marqdo remove <name>` edit marqdo.yaml only after validating the dependency
source (path-relative, git pinned by exact rev, no duplicate entry).
Removing a dependency also drops its stale lock entry; locking stays an
explicit step so no version changes happen silently.
- Manifest serialization omits empty dependency/plugin maps and empty
capability requests, keeping generated manifests readable and stable.
Blueprint section 8, minimum viable P3:
- marqdo.yaml parsing/validation: project identity, dependency sources (path or
git with mandatory exact rev), plugin requirements, capability requests;
absolute dependency paths, ambiguous sources and unpinned git are errors.
- marqdo.lock: lock_version, sorted packages, canonical YAML with no
timestamps or machine paths so repeated locking is byte-identical.
- discover_root walks up to the nearest marqdo.yaml.
- Manifest::template for `marqdo init`.
Create the Marqdo CLI Rust workspace with the module boundaries from the
development blueprint (section 11):
- marqdo-span: byte spans and line/column mapping shared by every layer
- marqdo-value, marqdo-expression, marqdo-markdown, marqdo-ir
- marqdo-frontend, marqdo-runtime, marqdo-host, marqdo-sandbox
- marqdo-math, marqdo-foreign, marqdo-package
- marqdo-plugin-abi, marqdo-plugin-sdk
- marqdo-cli (binary `marqdo`)
Pin the Markdown parser exactly (comrak =1.0.0, no default features) so the
frozen profile can never drift silently. Dependencies are centralized in
workspace.dependencies; no crate is allowed to add its own version of a shared
dependency.