Extract SolverHeaderCard and SolverFillHistory as real, reusable components

[james2177]

Description: src/components/SolverHeaderCard.test.tsx and src/components/SolverFillHistory.test.tsx already exist and each define an inline local implementation of the component under test — but no SolverHeaderCard.tsx or SolverFillHistory.tsx actually exists in src/components/. Meanwhile, src/app/solve/[address]/page.tsx duplicates the same header-card and fill-history markup inline, and separately references CopyButton, SkeletonCard, and isValidStellarPublicKey without importing them. Extract the two real components and wire the page to use them.

Problem Statement & Context: This is duplicated, drifting logic hiding a broken page: solve/[address]/page.tsx currently cannot compile as written (missing imports), and the two test files describe a cleaner component boundary that was never actually built, leaving the tests validating throwaway inline copies rather than real shipped code.

Scope & Acceptance Criteria:

• Create src/components/SolverHeaderCard.tsx and src/components/SolverFillHistory.tsx matching the interfaces implied by their existing test files (solver: Solver prop for the header card; solverAddress: string prop for the fill history, internally using useIntentFeed).
• Update src/app/solve/[address]/page.tsx to import and render these two components instead of its inline duplicated markup, and fix the missing CopyButton/SkeletonCard/isValidStellarPublicKey imports.
• Update SolverHeaderCard.test.tsx and SolverFillHistory.test.tsx to import the real components instead of defining local inline copies.
• Out of scope: changing either component's visual design beyond what's needed to match the existing test expectations and page layout.

Implementation Guidelines:

1. Key files: src/components/SolverHeaderCard.test.tsx, src/components/SolverFillHistory.test.tsx, src/app/solve/[address]/page.tsx, src/lib/stellarAddress.ts, src/components/CopyButton.tsx, src/components/Skeleton.tsx.
2. Match the props/behavior already asserted in the two test files exactly, since those tests should pass unmodified (aside from the import swap) once the real components exist.
3. Edge cases: SolverFillHistory's existing inline version filters useIntentFeed's 8-item-capped feed by solver === solverAddress, which may under-represent a solver's full history — consider (and note in the PR, even if not fixed here) whether it should use a different, unbounded data source; at minimum, don't silently change this behavior without flagging it.
4. Testing: npm run typecheck must pass (this file currently would not compile); run SolverHeaderCard.test.tsx and SolverFillHistory.test.tsx against the real components; add a page.test.tsx case for solve/[address] confirming the extracted components render with real solver data.

Definition of Done:

• Code written, tested; solve/[address]/page.tsx compiles and renders correctly with no missing imports.
• Both orphaned test files now validate real, shipped components.
• PR passes CI (npm run typecheck, npm test, npm run build).
• Reviewed and approved.

Resources: src/components/SolverHeaderCard.test.tsx, src/components/SolverFillHistory.test.tsx, src/app/solve/[address]/page.tsx

Complexity: High (200 points)

[reactjay]

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

Hi Maintainer I’d love to work on this issue. I’ve gone through the description and requirements, and I’m confident I can implement the fix, please assign it to me. Thanks!

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

[Markadrian6399]

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

I would like work on this issue

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

[drips-wave]

Congratulations, @Markadrian6399! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Markadrian6399: 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 🌊