markdown-tooling 1.16: advance the markdownlint-cli2-action pin (managed workflow, needs a payload cut)

[chrisdpurcell]

Context

.github/workflows/lint-markdown.yml pins DavidAnson/markdownlint-cli2-action at
6bf21b07787794f89a243495939cd651942aeabe # v24. A newer patch release is available
(markdownlint-cli2 0.23.1 -> 0.23.2; markdownlint itself unchanged).

The pin cannot be edited in this repository. The workflow is package-managed:

path = ".github/workflows/lint-markdown.yml"
owners = ["markdown-tooling"]
versions = { markdown-tooling = "1.15" }
provenance = "provider"
policy = "managed"

(.standards/lock.toml:660-668.) Hand-editing it would be CP-MODIFIED-MANAGED drift and would fail
the repository's own gate, so the pin can only advance through a markdown-tooling 1.16 payload cut.

Scope

Cut markdown-tooling 1.16 advancing the action pin, and ship it in a release. Bundle it with other
markdown-tooling work if any is pending, rather than cutting a payload for this alone.

Out of scope

Hand-editing the rendered workflow in this or any consumer repository.

Acceptance criteria

1. markdown-tooling 1.16 renders the updated pin, with the commit SHA and the version comment agreeing.
2. All predecessors stay byte-immutable and selectable.
3. project-standards validate and the reconcile check pass in this repository after the cut.
4. The Lint Markdown workflow still passes on a clean tree.

Constraints

Payload bytes are immutable after publication, so the pin advance is inherently a new-version cut. The
existing pin is functional, not defective — this is maintenance, not a fix.

Verification

Reconcile this repository onto the new version and confirm the rendered workflow matches the payload
byte-for-byte with no CP-MODIFIED-MANAGED finding.

Evidence / references

• .github/workflows/lint-markdown.yml:90 — the current pin.
• .standards/lock.toml:660-668 — the managed-ownership record.
• Deliberately deferred during the v5.27.0 train: a fifth payload cut for a linter patch bump was not
  proportionate to that release.

[chrisdpurcell]

Resolved by markdown-tooling 1.16, cut in PR #224 (merged to testing as 4ef087a, ships in v5.28.0). Pin advanced to DavidAnson/markdownlint-cli2-action@21c1be1b93ad9ed58fa840aacc3f279cde2a72ff # v24.2.0; SHA and comment agree (asserted by test_markdown_tooling_1_16.py); 1.15 byte-immutable; validators green; the rendered workflow re-renders at release-time reconcile and hosted CI proves it on main.

[chrisdpurcell]

Correction to the closing comment: markdown-tooling 1.16 merged to testing as d7c30017 (PR #224), not 4ef087a3 (which is the hygiene PR #223). Tag v24.2.0 dereferences to commit 21c1be1b93ad9ed58fa840aacc3f279cde2a72ff, confirmed via gh api by the orchestrator.