should we use a markdown linter in CI?

Might help to make sure that external contributions are consistent

Review the repository's existing CI configuration and Markdown content to determine the current consistency gaps and available checks. Done means deciding whether to adopt a Markdown linter, documenting the chosen scope and configuration, and defining how the check should run for external contributions.

Written by the indexing model from the issue text.