fix(backstop): BackstopActionPanel crashes — AmountInput is used but never imported

[FabianSanchezD]

Description

The BackstopActionPanel component references <AmountInput /> in both the deposit and withdraw tabs, but AmountInput is never imported. This causes a ReferenceError: AmountInput is not defined at render time, making the entire backstop deposit and withdrawal UI non-functional.

File: apps/web-app/src/features/backstop/components/ui/BackstopActionPanel.tsx

The import block only pulls in BackstopInfoAlert and QueueCountdown. The shared AmountInput component added in the latest changes (apps/web-app/src/components/AmountInput.tsx) is what should be imported here — matching how it is used in lending and swap.

Steps to Reproduce

1. Navigate to the Backstop page
2. Attempt to open the Deposit or Withdraw tab
3. The panel crashes / renders nothing

Expected Behavior

The deposit and withdraw tabs render correctly with a functional amount input field.

Acceptance Criteria

• import { AmountInput } from "@/components/AmountInput" is added to BackstopActionPanel.tsx
• Both the deposit tab (lines ~112-117) and withdraw-queue tab (lines ~181-186) render <AmountInput> without errors
• The deposit and withdraw flows work end-to-end (amount entry → button enabled → transaction submitted)
• No TypeScript errors related to this component

Labels

bug, P0, backstop

[larryjay007]

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

I would love to handle this P0 issue and restore functionality to the backstop deposit and withdrawal UI. I am fully comfortable resolving the ReferenceError by properly importing the shared AmountInput component and thoroughly testing the complete user workflow.

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

[paulpeter32-coder]

@paulpeter32-coder has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer I'm a fullstack developer and I would love to work on this issue

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

[paulddeveloper-droid]

@paulddeveloper-droid has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I count it as a privilege and opportunity to work on this issue. Please assign.

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

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[mspotless]

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

i would like to work on this issue

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

[drips-wave]

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

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