Skip to content

Add Orchestra Swidge community module docs

Created by: ihsraham

Summary

  • Add docs for the Flashnet-maintained community Swidge module wdk-protocol-swidge-orchestra@0.2.0.
  • Place Orchestra under the existing Swap and Bridge IA, after the Swidge protocol interface page and before the Velora and USDT0 provider pages.
  • Add overview, usage, configuration, API reference, and guide pages for quotes, execution, persistence, recovery, and error handling.
  • Document package-filtered route discovery, link the live Orchestra route matrix as provider-level data, and call out the route filters apps should apply before exposing routes.
  • Document client-key status reads with readToken, and add sourceTokenAddress / sourceTokenIdentifier to the API options reference.
  • Align /sdk/swidge-modules, /sdk/all-modules, /sdk/community-modules, static LLM docs, and related module pages with the documented module set.
  • Remove stale STON.fi TON placeholder references and remove the generic Swap module reference / Bridge module reference sidebar links from the Swap and Bridge section.

References

Validation

  • git diff --check
  • git diff --check upstream/develop...HEAD
  • PATH="/opt/homebrew/opt/node@22/bin:$PATH" npm run check:meta
  • PATH="/opt/homebrew/opt/node@22/bin:$PATH" npm run check:redirects
  • PATH="/opt/homebrew/opt/node@22/bin:$PATH" LINK_CHECK_EXTERNAL=false npm run check:links
  • PATH="/opt/homebrew/opt/node@22/bin:$PATH" npm run build
  • curl -I -L --max-time 20 https://orchestration.flashnet.xyz/v1/orchestration/routes

The local build generated 250 static pages and @vahor/next-broken-links found 0 broken links. The build still prints existing docType warnings on older docs pages outside this PR.

Merge request reports