Repository navigation
docs: fix DeepWiki badge - #3373
Conversation
- replace the challenged badge endpoint with Shields - preserve the DeepWiki label and repository link - verify the replacement serves a valid SVG
There was a problem hiding this comment.
Independent documentation cross-review of the current revision: 9/10; no blocking findings.
The complete diff changes only the README badge image source. The Markdown link structure, descriptive 'Ask DeepWiki' alternative text, and existing repository destination are preserved. This is a suitably small fix with no runtime or CI configuration changes.
Current workflow passed its license/policy job; build and cluster jobs were skipped. Independent HTTP/XML verification retrieved the replacement as HTTP 200 image/svg+xml with well-formed SVG and the expected accessible label. The unchanged destination returned cached HTML; fresh origin availability and GitHub image-proxy/browser rendering remain unverified.
Purpose of the PR
The Ask DeepWiki badge renders as a broken image when its origin returns an anti-bot challenge (HTTP 429; GitHub image proxy returns 502).
Main Changes
Use a static Shields badge while preserving the existing label and DeepWiki repository link.
Verifying these changes
git diff --checkpasses and the replacement returns a valid SVG.Does this PR potentially affect the following parts?
Documentation Status
Doc - TODODoc - Done: README.md is updated in this PR.Doc - No Need