Does norg provide a stable parser API for reproducible document processing?

Goal: Ensure that a development team can share norg files and obtain identical parsed representations regardless of the host machine or the version of the norg parser installed.

Constraint: The norg parser is actively evolving, and recent releases have adjusted how certain constructs—such as nested heading blocks, custom macros, and link resolution—are translated into the abstract syntax tree (AST). This evolution raises uncertainty about whether a document parsed today will yield the same AST tomorrow after a minor version bump.

Question: Does the norg project expose a versioned or compatibility‑mode parser API that locks the AST output to a specific release? Are there documented guarantees or migration notes that describe which syntactic changes are considered breaking for AST compatibility? Can a project declare a parser version in a lockfile or configuration file to guarantee repeatable builds across CI agents and developer workstations?