Skip to content

docs: fix broken relative links in docs - #2511

Open
Ajithkumar003-dev wants to merge 1 commit into
kagent-dev:mainfrom
Ajithkumar003-dev:docs/fix-broken-relative-links
Open

docs: fix broken relative links in docs#2511
Ajithkumar003-dev wants to merge 1 commit into
kagent-dev:mainfrom
Ajithkumar003-dev:docs/fix-broken-relative-links

Conversation

@Ajithkumar003-dev

Copy link
Copy Markdown

What

Fixes five relative markdown links that point at paths which do not exist, so they currently render as 404s on GitHub.

File Link Resolves to today (404) Fixed to (200)
contrib/cncf/security-self-assessment.md Security Policy contrib/cncf/SECURITY.md SECURITY.md
contrib/cncf/technical-review.md licensing contrib/cncf/LICENSE.md LICENSE
python/packages/kagent-openai/README.md skills README (x2) python/kagent-skills/README.md python/packages/kagent-skills/README.md
go/core/cmd/acp-shim/sandbox/README.md Dockerfile go/docker/acp-sandbox/Dockerfile docker/acp-sandbox/Dockerfile
go/core/cmd/acp-shim/sandbox/README.md main.go go/core/cmd/acp-shim/sandbox/main.go go/core/cmd/acp-shim/main.go

Why

Each one is an off-by-one ../ depth or a wrong file extension, and the intended target is unambiguous in every case. Two of them are in the CNCF review documents, where the dead links happen to be the Security Policy and License rows.

The acp-shim README paragraph is re-wrapped across four lines rather than two because the corrected path would otherwise push it past the ~80 column wrapping the file already uses. No wording was changed.

Docs only — no behaviour change.

Testing

  • Verified every corrected target exists in the tree.
  • Verified over HTTP against main that all five old paths return 404 and all five new targets return 200.
  • Re-ran a repo-wide relative-link scan: 10 broken links before, 4 after.

Not addressed here

Two further broken links are left alone deliberately, because the correct target can't be inferred without maintainer input:

  • docs/architecture/controller-reconciliation.md and docs/architecture/prompt-templates.md both link to go/core/internal/controller/agent_controller.go, which doesn't exist anywhere in the tree. The agent controller looks to have been refactored (agentharness_substrate_controller.go, sandboxagent_controller.go, the reconciler/ package) — happy to follow up if someone can point me at the file that replaced it.
  • docker/acp-sandbox/README.md references test-deployment.yaml and test-substrate.yaml as being "in this folder", but that folder only contains Dockerfile and README.md. That needs the manifests added, not a link edit.

Five relative markdown links pointed at paths that do not exist, so they
render as 404s on GitHub:

- contrib/cncf/security-self-assessment.md: the Security Policy link
  resolved to contrib/cncf/SECURITY.md instead of the repo-root file.
- contrib/cncf/technical-review.md: the licensing link resolved to
  contrib/cncf/LICENSE.md; the repo-root file is LICENSE, with no
  .md suffix.
- python/packages/kagent-openai/README.md: both skills links resolved to
  python/kagent-skills/README.md instead of
  python/packages/kagent-skills/README.md.
- go/core/cmd/acp-shim/sandbox/README.md: the Dockerfile link resolved to
  go/docker/acp-sandbox/Dockerfile, and the main.go link pointed into the
  sandbox directory rather than the parent acp-shim directory.

Each is an off-by-one ../ depth or a wrong extension; the intended target
is unambiguous in every case. The acp-shim paragraph is re-wrapped to keep
the file's existing ~80 column wrapping. Docs only, no behaviour change.

Signed-off-by: Ajithkumar003-dev <bhuvanaccs@gmail.com>
@Ajithkumar003-dev
Ajithkumar003-dev requested a review from a team as a code owner August 20, 2026 16:53
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants