Module parser 

The build-path parser front end.

Since M2 wave 3, RST goes through the docutils-fidelity parser in crate::rst (sphinx mode): Parser::parse builds the Document the pipeline consumes — title, toc (docutils-normalized anchors), toctree entries with per-entry lines, directive/role records for the validation system, and explicit-target labels for nitpicky mode — all derived from the doctree at parse time and serializable for the incremental cache. The M1 line-scanner is gone. Markdown stays on the wave-6 (MyST) TODO path.

Structs

ParsedFile

Everything one source file’s parse produces: the pipeline’s Document and the doctree it was derived from. The build’s read phase keeps both — the doctree is what the environment layer (tocs, titles, domains) reads, and what gets persisted per document.

Parser