chore(cursor): resync install.sh tool pins with ci-workflows v0.27.1

[kyle-sexton]

Closes #154

Summary

.cursor/install.sh pins each local tool to the version the CI composite actions use, so that a local .cursor/check.sh run gives the same verdicts as CI. The pins and their authority comment were still at ci-workflows v0.17.2. This repo's CI runs v0.27.1: every ci-workflows action in .github/workflows/*.yml is pinned to 4610c31… # v0.27.1.

Fix

• The authority comment now names v0.27.1, the version CI actually runs. It does not name the latest release (v0.30.x). The script mirrors CI, so its pins move when this repo's CI pins are bumped (by hand, through the fleet convergence pass), not when ci-workflows publishes a release.
• typos 1.49.0 → 1.50.1 and editorconfig-checker 3.11.1 → 3.11.2, with each SHA-256 taken from the v0.27.1 action's sha256 default.
• gitleaks, lychee, actionlint, shellcheck, check-jsonschema, and markdownlint-cli2 already matched v0.27.1. They are unchanged.
• Out of scope: automatic syncing of these pins, which the issue listed as a consideration. The file stays hand-maintained.

Verification

• Each version and hash was read from gh api repos/melodic-software/ci-workflows/contents/.github/actions/<tool>/action.yml?ref=v0.27.1.
• bash -n and shellcheck pass on .cursor/install.sh.

Related

• The issue proposed v0.30.0. That would have moved local checks ahead of CI, most visibly editorconfig-checker 4.x, which renames the binary: build(editorconfig)!: upgrade editorconfig-checker to 4.0.2 ci-workflows#632.
• build(deps): bump typos, editorconfig-checker, markdownlint-cli2, check-jsonschema defaults ci-workflows#628, #631

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-28T18:20:55.771116Z	910081a	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.