[Caneryy]

Summary

• Resolve an anchor's TRANSFER_SERVER_SEP0024 and read one SEP-24 transaction with a pasted SEP-10 bearer token.
• Explain every documented status, and keep an expired or rejected token distinct from a missing transaction.
• Keep the token in memory for the request only. It is not copied into the result.

Files

• features/sep24-transaction-status-tracker/

Out of scope

• Does not run a SEP-10 challenge or obtain a token.
• Does not start a deposit or withdrawal.

Test plan

• npx vitest run features/sep24-transaction-status-tracker (24 passed)
• npm run verify:features -- sep24-transaction-status-tracker (35 files)
• Confirm a 401 is labeled as a rejected token and a 404 is labeled as a missing transaction

Closes #505

[drips-wave]

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

[Caneryy]

Fixed the TypeScript error in lib/sep24-status-fetch.ts.

toSep24TransactionStatusTrackerErrorCode was typed as the full error union, so invalid_home_domain looked like a fetch result. That code only comes from input parsing. The fetch helper now returns unauthorized, transaction_not_found, or request_failed.