docs: replace broken Vaunt board links

[johnfinnerty-nz]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added, or deleted? (Required)

Replace obsolete Vaunt community board links with the current Vaunt documentation URL in .vaunt/add-tidb-docs-dash-badge.md.

Addresses only the Vaunt 404 reported in #23746. The Windsurf 429 and Stack Overflow 403 failures are outside this PR's scope, so the issue should remain open.

Previously recorded validation: the replacement URL returned HTTP 200 and git diff --check passed. Those checks were not rerun for this description-only correction.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

• Related code change PR links (if applicable):
• This PR is translated from:
• Other reference link(s): Broken Link Detected #23746 (Vaunt 404 only)

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

Summary by CodeRabbit

• Documentation
  • Renamed the TiDB documentation subsection to “Add a community board badge.”
  • Updated the badge text and links to direct readers to the open-source community documentation.
  • Updated template guidance to use the documentation page as a fallback destination.
  • Removed the outdated bullet linking directly to the community boards page.

[ti-chi-bot]

Hi @johnfinnerty-nz. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

Welcome @johnfinnerty-nz!

It looks like this is your first PR to pingcap/docs 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to pingcap/docs. 😃

[pingcap-cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jackysp for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: df30bcee-f6b4-490b-b81c-3d44d441970c

📥 Commits

Reviewing files that changed from the base of the PR and between 79cd093 and 5662c9a.

📒 Files selected for processing (1)

• .vaunt/add-tidb-docs-dash-badge.md

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

The Vaunt badge instructions now use the Vaunt developer documentation URL. The badge heading and alt text were updated, and the unavailable community-board link was removed.

Changes

Vaunt badge documentation

Layer / File(s)	Summary
Update badge instructions .vaunt/add-tidb-docs-dash-badge.md	The badge heading and alt text were updated. The pingcap and {{github_username}} links now target the Vaunt developer documentation. The community boards bullet was removed, and the documentation URL is described as a fallback.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Severity of issue fixed: Low

Merge Risk: ⚪ Minimal · up to 5662c

The badge instructions now direct users to the current Vaunt documentation instead of unavailable community-board URLs. The change is ready to merge.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The changes update the broken Vaunt URL identified in issue [#23746] and replace related obsolete community-board links with the current documentation URL.
Out of Scope Changes check	✅ Passed	All changes are limited to Vaunt community-board link updates in the file identified by issue [#23746]. No unrelated changes are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Title check	✅ Passed	The title clearly and concisely describes the primary change: replacing broken Vaunt board links.
Description check	✅ Passed	The description covers the required change, affected version, related issue, AI involvement, and scope. Optional checklist items are appropriately left unchecked.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}