Contributing

The 53000-53099 allocation is active for this dialect, and message IDs are stable once assigned.

Proposing a message or change

Open a pull request against military.xml. Keep additions within the Scope and Boundaries, and allocate new IDs from the reserved shared blocks listed in Message ID Allocation (update IDMAPPING.md in the same PR).

CI regenerates the C headers on every pull request that touches the XML, so a schema error shows up before review.

Commit and PR title format, the DCO sign-off, what makes a change wire-breaking, and the rules for AI-assisted contributions are in CONTRIBUTING.md.

Improving these docs

The site is built with VitePress from the docs/ directory. Hand-written pages live in docs/en/, and the sidebar is defined in docs/en/SUMMARY.md. The message reference pages are generated from military.xml and are not checked in. Diagrams are written as mermaid code fences and drawn in the browser; mermaid is loaded only on pages that have one. Only plain mermaid fences are drawn, and the build doesn't check diagrams, so preview them with npm run docs:dev. Mermaid wraps the labels of loop, alt and similar boxes to fit the box and splits a name that is too long for it with a hyphen, so break long labels yourself with <br/>.

cd docs
pip install beautifulsoup4 lxml
npm install
npm run docs:messages   # generate the message reference from military.xml
npm run docs:dev        # local preview at http://localhost:5173