docs: add exclusions documentation for non-fiat stellar anchors

[AdeMi20]

Summary

I evaluated stellarport.io's viability as a fiat off-ramp by analyzing its stellar.toml file and transfer server endpoint, discovering that it functions strictly as a gateway and DEX for crypto assets (like BTC, ETH, and XRP) with an unresponsive transfer API. Based on this lack of fiat settlement capabilities, I concluded it was unsuitable for integration and documented this exclusion decision, along with the technical reasoning, in a newly created docs/anchors/exclusions.md file within your stellar-intel codebase.

Linked issue

Closes #468

Changes

Testing notes

Automated

• npm run typecheck · ⏳ not run / ✅ green / ❌ failing
• npm run lint · ⏳ not run / ✅ green / ❌ failing
• npm run test · ⏳ not run / ✅ green / ❌ failing
• npm run build · ⏳ not run / ✅ green / ❌ failing

New / modified tests

Manual verification (if applicable)

Screenshots / recordings

Before	After

Checklist

Correctness

• The PR title follows Conventional Commits (auto-linted)
• One logical change; unrelated cleanup was split into a separate PR
• npm run typecheck passes
• npm run lint passes with zero new warnings (we run --max-warnings 0 in CI)
• npm run test passes; new behaviour has a test
• npm run build passes

Data integrity

• No fabricated rates, stub prices, or placeholder exchange rates (see the no-fabricated-rates rule in CONTRIBUTING.md)
• No isMock, // MOCK, // TODO: replace with real data, or commented-out real code
• If touching an anchor: the anchor's stellar.toml is publicly resolvable at https://{domain}/.well-known/stellar.toml and contains TRANSFER_SERVER_SEP0024
• If touching SEP-10: network passphrase assertion is intact (mainnet only)
• If touching SEP-24: the 10s AbortController timeout is intact on anchor fetches
• If touching the status poll: terminal states (completed | refunded | error) still stop the SWR loop

Security & non-custody (see docs/NON_CUSTODY.md once it lands)

• No new code path holds user keys, user funds, or long-lived anchor JWTs
• Every signing action is performed by the user's wallet (Freighter today)
• No secrets committed; .env.local is unchanged; new env vars are added to .env.example

Docs

• User-facing behaviour change → CHANGELOG.md entry under [Unreleased]
• API / schema change → relevant docs/*.md updated in the same PR
• Architecture change → docs/ARCHITECTURE.md updated (file map, diagram, or invariants as applicable)
• Public-facing feature → screenshot added to docs/showcase/images/ when relevant
• New env var → .env.example + README env table updated

Release hygiene

• If this touches a wave deliverable, the matching [ ] in docs/ROADMAP.md is updated
• No dependency added without justification in the PR description
• No breaking change hidden inside a non-breaking commit

Breaking changes

None.

For reviewers

[vercel]

@AdeMi20 is attempting to deploy a commit to the ezedikeevan's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@AdeMi20 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

[ezedike-evan]

Two CI failures to resolve before this can merge:

1. check (node 20) / check (node 22) — the CI check jobs are failing. Please run npm run lint && npm run test locally, fix any errors, and push.
2. lint-pr-title — the PR title docs: add exclusions documentation for non-fiat stellar anchors fails the Conventional Commits lint. Please update to e.g. docs(anchors): document stellarport.io exclusion as non-fiat DEX gateway and re-push.