Stellar federation

[RemmyAcee]

Close: #33

Here's a summary of what was done in this continuation pass:

introduction.mdx
— Guides section updated with the two missing entries:

[Spectre + Stellar Cookbook] with a one-line description
[Stellar Federation Addresses] with a one-line description
types.mdx
— three fixes:

Chain enum corrected: CKB = "ckb" was missing (it appeared in the SDK overview and guides but not in the types reference)
Stellar chain types import block updated to include the four federation types
New ## Stellar Federation Types section added with full documented interfaces for FederationRecord, FederationCache, FederationErrorCode, and FederationError — including the st:xlm: detection note on accountId and the guidance to use err.code over err.message for programmatic handling
The federation guide itself was already complete from the previous session. These three changes close all the cross-reference and consistency gaps across the doc site

[drips-wave]

@RemmyAcee Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[RemmyAcee]

Done, Close: #52

[truthixify]

Other docs PRs are landing one by one, which means most of them now conflict on docs.json (because each registers its new page there) and sometimes guides/privacy-best-practices.mdx. Quick rebase clears it:

git fetch origin
git rebase origin/develop
# in docs.json: keep all entries from both sides
# in privacy-best-practices.mdx: keep both your addition and develop's
git push --force-with-lease

Content of the PR itself is clean — this is just the registration ordering.

[truthixify]

@RemmyAcee — closing as superseded by #57, which I just merged. #57 includes the same federation guide content (plus the custom assets guide + SAC audit). Issue #33 has been closed since the federation work is now on develop.