Conversation
Collaborator
🟡 Heimdall Review Status
|
huklaa
force-pushed
the
agent/audit-broken-redirect-destinations
branch
3 times, most recently
from
August 26, 2026 09:16
168c32a to
13945a2
Compare
Author
|
Hi maintainers — #1801 has been implementation-ready for a while, including focused redirect-auditor tests. Could someone please take a look or point me to the appropriate reviewer? I’m available to address feedback immediately. |
huklaa
force-pushed
the
agent/audit-broken-redirect-destinations
branch
from
September 11, 2026 21:03
de4f094 to
bf24e23
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Description
What changed? Why?
Adds a focused redirect destination auditor for "docs/docs.json".
The tool:
This helps address the broken redirect debt tracked in #1783 without guessing replacement targets or making unrelated redirect changes.
Notes to reviewers
This PR intentionally adds tooling only. It does not rewrite existing redirect destinations.
The default mode is report-only so the current known redirect debt does not break normal workflows. A "--strict" mode is included for targeted validation or future CI use once the redirect tree is clean.
How has it been tested?