macOS arm64 aborted in nesting_depth_limit_is_enforced because the test-harness
thread stack is smaller than a production main thread. Run that contract test
on an explicit 8 MiB stack; the 128-level parser bound itself is unchanged.
The stdlib process product test hard-coded /bin/echo, which does not exist on
Windows. Use the test CLI itself as the granted program: the fixture reads
MARQDO_TEST_PROCESS_PROGRAM from the granted env, runs it with --version, and
the harness compares against the same invocation. process.run now forwards
SYSTEMROOT/WINDIR on Windows (process creation/DLL loading, not a capability),
and the bundled stdlib digest is regenerated for the changed test fixture.
One Markdown-to-program mapping, no version selector or legacy mapper.
Frontend/runtime:
- resolve @exec/@knowledge heading declarations with nearest-ancestor
inheritance; only an Exec H2 is callable; add UnitKind::Knowledge and
sem.* diagnostics (mode marker, unit name, exec-without-function,
payload nesting/empty, syntax, control stack, params position,
version directive, inferred-signature lint)
- extract Strong/Emph/inline Code as one-statement carriers, refuse
nested carriers, and honour heading segment boundaries so an if/while
cannot be closed across a heading
- lower if/else/while/end to the existing Branch/Loop/Return IR with a
compile-time control stack; keep payload-relative source spans through
expression parsing and rewrite them onto the file
- accept params(...) only as the first direct Exec H2 payload; keep the
existing free-variable inference and named-only rule for inferred
signatures; fix duplicate-mode/else/end and Knowledge-body inertness
- reject marqdo_semantics/syntax front matter directives
Data and tests:
- migrate stdlib/**/*.mq.md, regenerate stdlib.json digest
- migrate examples and the full semantics/negative/runtime corpus to
the only current syntax; expected values/runtime codes preserved
- migrate Rust-embedded .mq.md fixtures, init template, CLI help and
security-lane fixtures
Verified: cargo fmt --check, cargo clippy -D warnings and
cargo test --workspace --locked (green).