The pre-RFC link-form block-quote call was removed by RFC-LANG-0002, but the
IR still carried Stmt::Call, CallSite and CallTarget with matching branches in
the runtime, infer, call validation, loader, analysis projection and JSON
output. No mapper produces that variant any more, so it was a second call
representation that could never be reached.
- remove Stmt::Call, CallSite and CallTarget from marqdo-ir
- remove the runtime exec_call_site path and every exhaustive match arm
- remove the 'call_site' Analysis node and its JSON helpers
- state in spec/analysis-v2.md that calls are expressions; keep v1 as history
with a note that call_site is not produced by the current language
Verified: cargo clippy --workspace --all-targets -D warnings clean and
cargo test --workspace --locked green (62 targets).
Replace the Strong/Emph/List/Quote mapping in place with the single
@exec/@knowledge heading-mode model, unified payload carriers and keyword
control flow.
- add the authoritative RFC, ADR-0052 and a historical ADR index
- rewrite spec/mapping.md and spec/expression.ebnf as the normative
mapping/statement grammar; update evaluation, references, math,
foreign, package-format, plugin-abi, security and schema notes
- rewrite README, AGENTS, COMPATIBILITY and CHANGELOG for the breaking
language change; update the architecture index/overview and active docs
- mark superseded planning docs, compute RFCs, evidence and syntax-role
ADRs as historical/superseded without rewriting their decisions
- add migration guide, per-file inventory and dev-only audit scripts
The frontend/stdlib migration is completed in the following commits; this
commit contains documentation only.
- add ProjectIdentity (manifest root instance or workspace snapshot digest)
and remove absolute-path root ids from Analysis bytes
- replace the resources count with an addressable array over the two real
marqdo-ir resource kinds (formula, code), including unit/span/payload digest
and code language
- project diagnostics by module/relative path/span, removing machine paths
- define the digest as SHA-256 of the exact emitted bytes so consumers can
verify it; Trace binds to the same digest
- add analysis-v2 spec and JSON schema, supersede v1, update the independent
Python consumer, schemas and docs
- tests: location-independent byte equality and resource addressing