The Windows CI failure was a checkout byte-identity problem, not a Markdown
semantics change: CRLF goldens compared with LF parser output produced
'0 line(s) differ'.
- add .gitattributes: text files are LF, native products are binary, and the
intentional CRLF fixture stays a byte fixture
- report the first differing byte and whether only line endings differ
- fail early when a golden contains CR instead of the opaque mismatch
- assert exactly one CRLF fixture and that its golden is canonical LF
- add a markdown test proving CRLF/LF have equal structure while spans remain
byte offsets into the original source
`inspect --ast` and AST goldens now show `{"kind":"heading","level":2,...}`
instead of a nested `{"kind":{"kind":"heading",...}}` object, matching
spec/markdown-profile.md section 5 and the shape new contributors expect.
- md code nodes now carry `ticks` (delimiter length) so executable payload
offsets inside code spans map back to exact source bytes instead of pointing
at backticks; this keeps diagnostics precise for mixed text/code payloads.
- value: add the markdown.inert_executable warning code and a small clippy fix,
without changing the wire format.
- spec: document the code-span tick metadata, declare strikethrough lazy, and
make the inert-execution warning explicit for nodes outside any function.
- workspace dependencies: add unicode-ident (grammar) and glob (capability
path patterns) for the frontend/host layers.
Tests: 15 markdown + 10 value + 2 span tests pass; fmt/clippy clean.
P0 baseline: one Markdown parser, one frozen option set, no silent upgrades.
- profile: CommonMark 0.31.2 core + GFM tables/strikethrough/task lists +
dollar math + YAML front matter at byte 0, with every other extension
disabled and asserted by tests. comrak is pinned to exactly 1.0.0.
- ast::MdNode: owned, serializable node tree carrying kind, byte Span and
literal payloads. Nodes outside the profile are preserved as MdKind::Other
instead of being dropped; task list items keep their checkbox state.
- frontmatter: extracts the YAML body from the parser node, parses it once,
and exposes only the explicit `import` alias mapping; invalid YAML is
reported, never guessed.
- text: strict executable payload extraction (Text/Code only, everything else
is a hard error) and inert plain-text extraction for heading names.
- UTF-8 BOM is tolerated; all spans are re-based onto the original file.
No semantic mapping or execution exists in this crate by design.
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.