DX-051: Add a link checker to the docs pipeline

[IbrahimIjai]

Context

Broken internal links are the most common documentation defect and the easiest
to prevent. External links break too, but on someone else's schedule — which is
why they must not be able to fail a pull request.

Scope

• bun run --cwd apps/docs check:links validating every internal link and
  heading anchor against the page index, plus image and asset paths.
• Anchor validation checks the target heading actually exists on the target page.
• Internal checking runs on every pull request in CI.
• External link checking is a separate scheduled workflow that opens an issue on
  failure rather than blocking merges, with a configurable ignore list.
• Report groups failures by source file with line numbers.

Acceptance criteria

• A broken internal link or anchor fails CI with file and line.
• External failures never block a pull request.
• The scheduled job opens exactly one issue per run, not one per link.
• Runs clean against the full site at the time of merge.

Out of scope

• Checking links in application code outside apps/docs.

---

Spec: docs/dx_1/001_docs_site.md §7 · Depends on: DX-050

[mkolade]

@mkolade has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi can i be assigned to this. I’m really interested in helping out with this task and can guarantee a clean, timely solution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mkolade to this issue.

[TheWeirdDee]

@TheWeirdDee has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on #563, adding a focused documentation link-checking pipeline that catches internal documentation defects without making external availability a merge blocker.

I’ll first inspect the existing apps/docs tooling and the DX-050 implementation to reuse established conventions. I’ll implement bun run --cwd apps/docs check:links to index the documentation pages and validate internal links, heading anchors, images, and asset paths. Anchor checks will verify that the referenced heading actually exists on the destination page rather than only checking that the page exists.

Failures will be grouped by source file and include useful line numbers so contributors can locate and fix broken references quickly. The command will return a non-zero exit code for internal-link failures and remain limited to apps/docs, without scanning application code.

CI will run the internal checker on every pull request. External links will use a separate scheduled workflow with a configurable ignore list; failures will be reported through exactly one issue per scheduled run and will never block PRs.

I’ll add focused tests covering valid/invalid internal links, missing anchors, broken image/asset paths, line-number reporting, and external-link failures. I’ll also verify the checker against the complete documentation site to ensure the existing content passes cleanly.

The PR will remain scoped to the documentation checker and its CI/workflow configuration, with no unrelated application changes. I’ll run the full docs validation and relevant repository checks and include the exact commands/results in the PR.

The PR will reference Closes #563 and document the checker behavior, CI separation between internal and external links, ignore-list configuration, issue-reporting behavior, and verification evidence.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TheWeirdDee to this issue.

[johnmic0132]

@johnmic0132 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer! I’d love to take on this issue and get it done efficiently. Kindly assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @johnmic0132 to this issue.

[razeprasine]

@razeprasine has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I would love to resolve this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @razeprasine to this issue.

[drips-wave]

Congratulations, @razeprasine! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @razeprasine: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@razeprasine's PR #644 was approved and merged by @IbrahimIjai.

🏆 @razeprasine: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (904 total points). Track your full progress on GrantFox.

👏 Great work, @razeprasine! Keep contributing to SO4-Markets.