Markdown translation handoff exercise, 12 November 2026

Fictional studio CLI documentation with manually supplied English/French copy.
The studio command is an inert example. It is not a real Nativ command and is
not installed or executed by this exercise. The example.com URL is illustrative.
No customer file, paid generation or language-quality benchmark is included.

Files:
source.md: English reference.
fr.md: manually written French wording, with declared technical literals intact.
broken.md: intentionally changed command flag and destination URL.
contract.json: eight declared exact snippets and expected occurrence counts.
check_contract.py: read-only, network-free Python3 standard-library helper.
README.txt: these instructions.

Extract the ZIP and run:
python3 check_contract.py contract.json source.md
python3 check_contract.py contract.json fr.md
Expected for both: PASS: 8 declared literal checks (not a complete Markdown review)

python3 check_contract.py contract.json broken.md
Expected failure: example shell block: expected literal count 1

The checks cover one complete fenced command block, inline command, file path,
runtime variable, external link destination, section-link destination, explicit
anchor and a frontmatter identity line. Human-readable titles, labels and prose
can change. Read the contract and helper before using private input.

Limitations: this helper counts literal snippets. It is not a Markdown/MDX/HTML
parser, syntax validator, link checker or translation evaluator. It does not
prove the snippets are in the right place, detect arbitrary new code or links,
test commands, validate frontmatter schemas, or judge meaning/negation. The
example URL does not identify a real reference page. It normalizes LF/CRLF
when reading and tolerates a leading UTF-8 BOM. It never writes either file.

Adapt the contract to the document and reviewed changes. A destination URL may
need to change deliberately for a localized site. An intentional change needs
review and a revised contract, not a forced equality to the English source.
Preview the result with your actual docs renderer and run its build/link checks.
Explicit anchor handling and frontmatter rendering vary by publishing system.
Keep normal Markdown preview security enabled; there are no remote images or
scripts in these files. Language approval remains separate from these checks.
