markdown-validationlisted

## Input - Markdown file(s) with `.md` extension (required) - Optional: markdownlint-cli2 config, markdown-link-check config, file pattern (`**/*.md`) ## Output Specification Return structured Markdown in accordance with [references/common-output-format.md](references/common-output-format.md). That file is the source of truth for the output contract. Structured validation results from two tools: markdownlint-cli2 → markdown-link-check. ## Execution Scope - **Always use `scripts/validate.sh`** for comprehensive validation. Do not run individual commands. - Script executes markdownlint-cli2 and markdown-link-check in order. - **Do not modify Markdown files** (except with --fix flag) - External link checking depends on network connectivity ### USE FOR: - validate markdown syntax and links before commit - investigate markdown CI failures - run scoped markdown checks for specific docs paths ### DO NOT USE FOR: - review prose quality or content strategy - validate non-markdown files - replace YAML/JSON/Terraform validation workflows ## Reference Files Guide - [common-checklist.md](references/common-checklist.md) (always read) - [common-output-format.md](references/common-output-format.md) (always read) - [common-troubleshooting.md](references/common-troubleshooting.md) (read on failure) - [common-individual-commands.md](references/common-individual-commands.md) (read on failure) ## Workflow 1. Run `bash scripts/validate.sh` (or `bash scripts/validate.sh <path>` for sc