fix(ci): Resolve double JSON.parse in redirect chain lint workflow

[s1gr1d]

Fix a regression in CI (breaks on every new PR right now)

Workflow added in: #18620

Fix SyntaxError: "[object Object]" is not valid JSON in the redirect chain lint CI step by removing redundant double-parse of the lint result output.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ready	Preview	Jul 13, 2026 11:56am
sentry-docs	Ready	Preview	Jul 13, 2026 11:56am

[sentry]

Bug: The lint_result output is a JSON-encoded string. A single JSON.parse is not enough to convert it into an object, causing the script to fail silently.
_{Severity: MEDIUM}

Suggested Fix

The lintResultRaw variable is a JSON-encoded string that needs to be parsed twice to become a usable JavaScript object. Restore the double JSON.parse call, which will first unescape the string and then parse the resulting JSON string into an object.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: .github/workflows/lint-redirect-chains.yml#L74

Potential issue: The `steps.lint.outputs.lint_result` variable is a string containing
JSON. The `toJSON()` function in the GitHub workflow escapes this string, creating a
JSON-encoded string. The code then uses a single `JSON.parse` on this value. This only
reverses the `toJSON()` escaping, resulting in `lintResult` being a string of JSON, not
a JavaScript object. Consequently, attempts to access properties like
`lintResult.redirectChains` and `lintResult.contentLinkIssues` return `undefined`. This
causes the script to silently fail and not post the linting results as a PR comment.

_{Did we get this right? 👍 / 👎 to inform future reviews.}