Remove the hardcoded discovery time in SearchResultsVisualizer

[RUKAYAT-CODER]

Overview
src/components/search/SearchResultsVisualizer.tsx:68 displays a static 'discovered in 0.8s' string regardless of the actual query duration, misrepresenting real search performance to users. Either measure and show the real duration or remove the claim.

[Yinklekay]

@Yinklekay has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Yinklekay to this issue.

[Ayomide-codex]

@Ayomide-codex has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please kindly assign. I’d love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ayomide-codex to this issue.

[Meemlahsabi]

@Meemlahsabi has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, I’ve taken the time to understand the issue details and I’m confident I can provide an efficient, maintainable, and well-structured solution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Meemlahsabi to this issue.

[tobemacauley-rgb]

@tobemacauley-rgb has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hey I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @tobemacauley-rgb to this issue.

[CodeMayor]

@CodeMayor has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd like to work on this issue because it improves the accuracy of the search experience by removing misleading UI feedback. I'll replace the hardcoded discovery time with the actual query duration where available, or remove the static claim if reliable timing cannot be determined, while keeping the implementation lightweight and consistent with the existing search flow.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @CodeMayor to this issue.

[Ghadaffijr]

@Ghadaffijr has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would love to take this on and can have the pr ready before the deadline.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ghadaffijr to this issue.

[DTriple-p]

@DTriple-p has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi there, I'd like to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DTriple-p to this issue.

[deslawson]

@deslawson has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @deslawson to this issue.

[drips-wave]

Congratulations, @DTriple-p! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @DTriple-p: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊