Add the independent program IR from blueprint sections 7.1 and 11:
- ModuleId, FunctionId and UnitId canonical identities; UnitInfo/UnitKind for
heading scopes (root, namespace, function, section).
- Function with explicit or inferred signature metadata, params and defaults;
assignments, expression statements, link-form calls, branches, loops and
returns, all carrying source spans.
- CallTarget distinguishes same-module, import-alias-qualified and
link-resolved calls.
- ImportDecl from explicit front-matter imports; Resource records inert
Formula/Code artifacts with SHA-256 content hashes and owning units.
- Module anchors, resolved import edges and Program lookup helpers used by the
runtime and CLI.
- Builtin registry (names, aliases, arity, named-only/effect flags) shared by
static validation and runtime dispatch; adding a builtin is a spec change.
Prose is absent from the IR by construction, so narrative edits cannot change
the executable projection.
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.