Release 0.3.0: legaldown-validator 0.4.0

[dvejsada]

This bumps the version to 0.3.0 for the release built on legaldown-validator 0.4.0's public API (#3). After merging, publish a GitHub Release tagged v0.3.0 on the merge commit. That release uploads the package to PyPI.

Changes

• __version__ goes from 0.2.0 to 0.3.0. It is the only place the version is set, and the publish workflow checks the tag against it.
• CONFORMANCE.md names legaldown-render 0.3.0 and legaldown-validator 0.4, worded the way the v0.2.0 text was.
• Roadmap:
  • New "v0.3 — Validator 0.4.0 (this release)" entry.
  • The planned DOCX and PDF milestones move to v0.4 and v0.5, so v0.3 is not claimed twice.
  • ADR 0004 gets a dated note saying the same, the way ADRs 0002 and 0007 were amended.
• The two HTML goldens embed <meta name="generator" content="legaldown-render X.Y.Z">. Only that line changes in each.

Checked

• ruff check . is clean.
• pytest: 192 passed, 1 skipped (the spec corpus).
• Conformance against LegalDown v0.2: 197 passed.
• The publish workflow's steps, run locally on this commit:
  • python -m build succeeds, and twine check --strict passes for the sdist and the wheel.
  • The tag check with TAG=v0.3.0 reports "version 0.3.0 matches tag 0.3.0".
  • Smoke test from the wheel alone: legaldown-render --version prints legaldown-render 0.3.0, and the Czech continental render works.
  • The wheel metadata has Requires-Dist: legaldown-validator<0.5,>=0.4.0. legaldown-validator 0.4.0 is on PyPI.

Draft release notes for v0.3.0

Requires legaldown-validator 0.4 (`>=0.4.0,<0.5`); `pip install -U legaldown-render` brings it in. Renders LegalDown (specification 0.2, Rendering level) to HTML and plain text.

- Uses only the validator's public API (`legaldown`, `legaldown.syntax`, `legaldown.grammar`), so `validator_bridge.py` is gone
- Rendered output is unchanged, except that a quote nested past the validator's depth (17+ levels of quotes and list items combined) holding only an HTML comment no longer renders an empty paragraph
- Answers files: a UTF-8 BOM is now accepted, and a pathologically nested YAML file gives a clean error (both from validator 0.4.0's `load_answers`)
- Known limitations: see [CONFORMANCE.md](https://github.com/ForLegalAI/legaldown-render/blob/v0.3.0/CONFORMANCE.md) (link reference definitions, ForLegalAI/legaldown-validator#92)

Full change: #3

🤖 Generated with Claude Code

https://claude.ai/code/session_01Q3fBapGwQ2J2vLzpDyjB5t

---

Generated by Claude Code