feat: implement Stellar transaction history view

[thebabalola]

Added a new History page and a StellarHistory component to view transaction history for the connected Stellar wallet. Closes #8.

[vercel]

@bbkenny is attempting to deploy a commit to the truthixify's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

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

[thebabalola]

Hi @maintainer, I've implemented the Stellar transaction history view. Ready for review!

[thebabalola]

Hi @maintainer, I've updated this PR. Ready for review!

[truthixify]

The skeleton page is a start, but the scope here doesn't match what issue #8 asked for. Two things:

1. Scope. The PR fetches Horizon transactions for the connected wallet. The issue is asking for Wraith-specific activity tracking: stealth sends/receives/withdrawals/name-registrations, categorized by kind and direction, persisted in localStorage per (chain, wallet), with status transitions (pending → confirmed → failed) polled against Horizon, filterable by chain/kind/status, with clear-history and a Playwright test. The bare Horizon list misses the protocol-specific surface that makes this useful.

2. Rebase. Branch is from pre-develop main, the diff would revert StellarSend/Receive work that just merged. After expanding scope, rebase:

   git fetch origin
   git rebase origin/develop
   git push --force-with-lease

   Drop your changes to StellarSend.tsx and StellarReceive.tsx (they're stale-base reverts) and instead add hooks in those files that record entries into the new history store. Keep StellarHistory.tsx and pages/History.tsx but expand them per the issue spec.

Thanks @thebabalola.

[thebabalola]

I've expanded the scope to fully match issue #8:

• Rebased on develop and dropped the stale revert commits in the send/receive components.
• Built useActivityStore (using Zustand + localStorage) to persist Wraith-specific activity (sends, withdrawals, receives, registrations) per chain/wallet.
• Added a polling mechanism against Horizon to update pending -> confirmed | failed status.
• Expanded the StellarHistory UI to include filters by type and status, and a clear history button.
• Implemented the requested Playwright e2e test for the history page.

Ready for another look!

[truthixify]

The history scope expansion is much better now: activityStore.ts, the dedicated StellarHistory.tsx, the /history route, hooks in Send/Receive to record entries, plus the Playwright spec. Real shape this time.

Tiny blocker: #35 (Web Worker scanning) just landed and also touched StellarReceive.tsx, so there's a true conflict in that file. One more rebase:

git fetch origin
git rebase origin/develop
# resolve in src/components/StellarReceive.tsx by keeping both:
#   - develop's Worker integration (new Worker(...), the scanner.worker.ts onmessage handler)
#   - your activity-recording hook on the receive event
git push --force-with-lease

After that I'll merge. Thanks @thebabalola.

[thebabalola]

Hi @truthixify, I've rebased the branch on develop and resolved the conflict in StellarReceive.tsx by keeping the new Web Worker scanner integration while ensuring the activity-recording hook still fires on the receive event as requested. Everything is pushed and ready to merge!

[truthixify]

Rebase onto #35 worked. Diff is clean now, worker preserved, all your activity-store additions in place. Merging. Thanks @thebabalola.