build: integrate markdownlint for documentation consistency

[JacksonFergusonDev]

Motivation

Relying solely on relaxed global IDE settings for Markdown introduces parsing vulnerabilities when documentation is rendered across different engines (e.g., GitHub Flavored Markdown vs. strict CommonMark). Missing blank lines around fenced code blocks or contiguous list items can corrupt the Abstract Syntax Tree (AST), resulting in raw text nodes instead of the intended DOM structures.

This PR establishes a repository-level linting baseline to enforce AST-critical formatting while explicitly bypassing stylistic constraints (like strict line lengths) that often cause unnecessary diff churn.

Changes

• +.markdownlint.yaml:
  • Establishes structural integrity rules (e.g., MD031/MD032 for block spacing, ATX-style headings, and consistent list markers).
  • Disables MD013 (line length) and MD033 (inline HTML) to preserve complex layouts and prevent URL breakage.
• ~.pre-commit-config.yaml:
  • Adds the markdownlint-cli hook to automatically resolve standard formatting deviations locally.
• ~.github/workflows/ci.yml:
  • Injects an npx --yes markdownlint-cli step into the CI pipeline to ensure documentation compliance.
• Documentation Cleanup:
  • Applied automated fixes to README.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md, and all internal documentation to satisfy the new linting requirements and resolve CI failures.

Testing

• Verified pre-commit run --all-files correctly detects and auto-fixes syntax deviations.
• Verified CI workflow successfully executes the linting step via npx across the entire file tree.
• Confirmed documentation renders correctly after automated structural adjustments.