Add reusable CI/CD workflows for synchronized documentation

[adrianbrowning]

What to build

Make mdcode practical to adopt in CI/CD pipelines by providing a reusable documentation-synchronization check, runnable-example validation, and release gating. A consumer should be able to copy the examples and prevent stale Markdown code blocks from reaching production.

Acceptance criteria

• The repository contains a documented end-to-end CI/CD integration path for mdcode.
• The path checks that Markdown blocks are synchronized with their linked source files.
• The path supports validating selected runnable examples.
• The release path runs the relevant mdcode checks before a package is published.
• Each deliverable is tracked as a child issue and can be completed independently.

Blocked by

• Provide a reusable CI script to check documentation synchronization #11
• Provide a CI example for validating runnable Markdown snippets #12
• Gate package releases on mdcode documentation and example checks #13

[adrianbrowning]

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Coordinate the independently delivered CI/CD examples into one complete mdcode adoption path.

Current behavior:
The initiative is already decomposed into a documentation-sync check (#11), runnable-example validation (#12), and release gating (#13). No parent-level implementation should duplicate those child deliverables.

Desired behavior:
After the child issues land, the repository presents one coherent, documented CI/CD path: consumers can check documentation drift, validate selected runnable snippets, and use the checks as release gates. The parent is complete only after the integrated path satisfies its acceptance criteria.

Key interfaces:

• Child deliverables — Provide a reusable CI script to check documentation synchronization #11, Provide a CI example for validating runnable Markdown snippets #12, and Gate package releases on mdcode documentation and example checks #13 remain the authoritative implementation work.
• Integrated documentation path — connect the child examples so a consumer can discover and adopt them in sequence.
• Release governance — publishing credentials, trusted publishing, and final release activation require maintainer control.

Acceptance criteria:

• Provide a reusable CI script to check documentation synchronization #11, Provide a CI example for validating runnable Markdown snippets #12, and Gate package releases on mdcode documentation and example checks #13 are complete and their examples remain independently usable.
• The repository documents one end-to-end adoption path from drift checking through runnable validation and release gating.
• The integrated path uses the current public CLI contract and canonical package identity.
• The maintainer has reviewed and activated any required release credentials or trusted publishing configuration.

Out of scope:

• Reimplementing any child issue within this parent.
• Adding CI providers beyond the documented example scope.
• Changing mdcode command behavior.

Why this needs a human:
This is an integration and release-governance checkpoint. It requires coordinating completed child work and approving credentials/publishing policy rather than producing a separate code change.

Verification status:
Confirmed: the three required child deliverables already exist, and #13 depends on #11 and #12.