Update Swidge tables and community disclaimers

[ihsraham]

Summary

• add Rhino.fi, Velora, and USDt0 coverage to Swidge module tables while preserving package-only links where no local docs route exists
• leave LI.FI commented out in the Swidge/community module tables with a TODO to uncomment it in the draft LI.FI docs PR or after it merges
• add or normalize legal disclaimers for community/provider-owned module surfaces, including Swidge provider detail pages and community API refs
• retitle the core error-handling guide to Best Practices while keeping the existing /sdk/core-module/guides/error-handling URL stable

Local screenshots

Captured from the local Node 22 docs server.

Released Swidge provider table

Best Practices title on the existing error-handling URL

Community provider legal disclaimer

Validation

Latest validation after deferring LI.FI:

• git diff --check
• npm run check:meta
• npm run check:redirects
• LINK_CHECK_EXTERNAL=0 npm run check:links
• DOCS_SEO_QUIET_GENERATED=1 npx -y node@22.22.2 --import tsx/esm node_modules/.bin/next build

Notes

• The MCP SDK tools URL is already fixed on current develop as https://ts.sdk.modelcontextprotocol.io/v2/servers/tools.
• LI.FI is intentionally commented out until the draft LI.FI docs PR lands or merges.
• npmjs 403 responses are expected anti-bot behavior during external link checks; unrelated link drift can be fixed in unrelated PRs.