We've had issues with various links in the console being broken but having no visibility on the breakage (recent example: help/Quickstarts content). To that end, it would be nice to have a live crawler to validate link content in stage (or prod) and identify which links are broken.

Attempts to build such a "scanner" were performed in the past, but the technical focus was on scanning source code, which wasn't a good approach. Results were disappointing. With a scanner that runs against a "real" version of the application running in stage, we are more likely to get meaningful results.

AC

• Crawler "Walks" links in consoledot after logging in (methodology for crawling left up the developer)
• The "Crawler" should produce a program-consumable report of links that are suspected to be broken (and where they were found). Output could be JSON, CSV, etc. It merely needs to be readable by a program.
• The Crawler should be something that can be scheduled and executed, regardless of the tooling environment (Konflux, Jenkins, CircleCI, anything). Something driven by a CLI would be ideal.