chore(deps-dev): bump markdownlint-cli2 from 0.23.1 to 0.23.2

[dependabot]

Bumps markdownlint-cli2 from 0.23.1 to 0.23.2.

Changelog

Sourced from markdownlint-cli2's changelog.

0.23.2

• Update dependencies

Commits

• b82a6c8 Update to version 0.23.2.
• e4e659d Add a stub for process.nextTick (using queueMicrotask) now that globby (indir...
• 99760af Bump globby from 16.2.1 to 16.2.2
• 3070236 Address new ESLint warnings from previous commit.
• 6e3cc93 Bump eslint-plugin-unicorn from 71.1.0 to 72.0.0
• 4ba8177 Add eslint-package-json/all to lint script, address new issues.
• 9cb99b2 Refactor eslint.config.mjs to use defineConfig, change eslint-plugin-n from "...
• 37fb0ec Address new ESLint warnings from previous commit.
• f7fea61 Bump eslint-node-test from 0.2.0 to 0.3.0
• 85bb5e7 Bump js-yaml from 5.2.1 to 5.2.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[chrisdpurcell]

Triage: this pin is coupled to an action major and to shipped rationale

No payload-managed file is touched, so the control plane is quiet. coherence fails on the pin:

FAILED tests/coherence/test_pins.py::test_package_json_pins_both_tools
FAILED tests/coherence/test_pins.py::test_lockfile_agrees_with_package_json

tests/coherence/test_pins.py:8 is explicit about why the number is fixed:

MARKDOWNLINT_CLI2_PIN = "0.23.1"  # Keep aligned with markdownlint-cli2-action@v24.

Two couplings make this more than a lockfile bump

1. The action pin. The local CLI pin is deliberately kept in lockstep with DavidAnson/markdownlint-cli2-action@v24 (pinned in _EXTERNAL_ACTIONS) so local runs and CI runs use the same engine. Moving the npm dep alone breaks that alignment — the point of the comment. If v24 does not ship 0.23.2, this bump makes local and CI diverge silently, which is worse than being one patch behind.

2. Shipped rationale cites this exact version. markdown-tooling 1.12 records 0.23.1-specific behavior as a rejected alternative:

• versions/1.12/README.md:143 — restoring .gitignore parity via the gitignore switch was rejected because "Version 0.23.1 exposes it only as a key in a .markdownlint-cli2.* runner config, with no CLI or action input".
• versions/1.12/providers/markdown_tooling.py:102-103 and resources/self-host-lint-markdown.yml:73 carry the same reasoning, which is why the package ships explicit exclusions instead.

If 0.23.2 changed how that switch is exposed, the rejected-alternative rationale stops being true and the shipped design decision needs revisiting — a payload change, not a dependency change.

What this PR actually needs

• Confirm whether markdownlint-cli2-action@v24 bundles 0.23.2; if not, this should wait for the action.
• Confirm 0.23.2 did not change gitignore exposure; if it did, markdown-tooling's rationale and exclusion strategy need updating in a new minor.
• Then update MARKDOWNLINT_CLI2_PIN and keep the alignment comment accurate.

Left open deliberately.

Automated triage; no code changed.