feat: add global search across streams

[Ademiitura]

Commit Type

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (formatting, etc.)
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing or correcting existing tests
• build: Changes affecting the build system or external dependencies
• ci: Changes to CI/CD configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit

Breaking change? (If yes, add BREAKING CHANGE in the commit footer)

• Yes — this contains a breaking change
• No

---

What changed

• New GlobalSearch component in header: debounced (300ms) search across stream ID, sender, recipient, and asset code via existing listStreams q param
• Dropdown shows matching results with sender/recipient/amount preview
• Full keyboard support: arrow up/down to navigate, Enter to open stream detail, Escape to close
• Enter/click navigates to dashboard with ?streamId= set, reusing the existing useUrlFilters mechanism that drives StreamDetailDrawer
• Includes same environment fixes applied on other branches tonight (package.json/lock restore, react-router-dom dependency, pre-existing SenderDashboard syntax error, stale story type mismatches) since none have landed on main yet.

Testing done

• Ran the app locally (npm run dev) and confirmed via the Network tab that typing into the search box fires a correctly debounced streams?q=...&limit=8 request only after ~300ms of no typing, with the right query value at each stage.
• Verified npx tsc --noEmit passes cleanly.
• Verified npm run lint shows no new errors introduced by this PR (only pre-existing errors in unrelated files remain).
• Verified npm ci succeeds against the regenerated lock file.

Related issues

Closes #750

Checklist

• I used the correct commit type (see above) for the squashed commit message.
• I kept the change focused on the related issue.
• I added or updated tests where useful.
• I updated documentation where behavior changed.
• I verified the app still builds or explained why verification was skipped.
• My commits follow Conventional Commits (enforced by commitlint).

[vercel]

@Ademiitura is attempting to deploy a commit to the ritik4ever's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

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

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c4c280d3-368b-428e-b93d-17ed934329ac

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}