:bug: Broken link in demos/weather-agent/demo-ui.md: https://github.com/rossoctl/rossoctl/blob/main/docs/authbridge/deployment-guide.md
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open demos/weather-agent/demo-ui.md and locate the reference to the rossoctl deployment guide. Replace the broken reference with a valid documentation link, then verify that it resolves successfully and that the link-health scan no longer reports a 404.
Written by the indexing model from the issue text.
Description
Describe the bug
Broken link detected by automated link health scan.
Repo: rossoctl/cortex
File: demos/weather-agent/demo-ui.md
Broken URL: https://github.com/rossoctl/rossoctl/blob/main/docs/authbridge/deployment-guide.md
HTTP Status: 404
First detected: 2026-09-28
Scan ID: 2026-09-28-001
Steps To Reproduce
- Open https://github.com/rossoctl/cortex/blob/main/demos/weather-agent/demo-ui.md
- Click or follow the link to
https://github.com/rossoctl/rossoctl/blob/main/docs/authbridge/deployment-guide.md - Observe 404 error
Expected Behavior
The link should resolve to valid documentation.
Additional Context
Category: internal
Detected by: OpenClaw Link Health Scanner (cron: link-health-scanner)
- Dominant language
- Go
- Stars
- 13
- Forks
- 40
- Avg merge
- 12h 11m
- Merged PRs (30d)
- 186
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rossoctl/cortex
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
Similar issues
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
priority/4/normal status/needs-triage type/bug/unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
authelia/authelia#13292 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
blinklabs-io/actions#138 ·
Maintainers usually reply within 1 day
-
[UI] AlbumDetails collapses multi-genre list to single primary genre on viewports < lg breakpointOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day