Delete orphaned root-level ApiUsage duplicate

[greatest0fallt1me]

Summary

src/ApiUsage.tsx (717 lines) and its test duplicate src/pages/ApiUsage.tsx (861 lines); App lazy-loads only the pages version. Similar duplicates exist for ThemeToggle, CallHistoryRow, FiltersSidebar and PlanBadge across src/, components/ and pages/.

Why this matters

Contributors fix bugs in the wrong copy, and tests of dead code inflate coverage while the live page stays untested.

Scope

Remove src/ApiUsage.tsx and src/ApiUsage.test.tsx after porting any unique tests, and open follow-ups for the other duplicate pairs with a table of which copy is live.

Relevant code in CalloraOrg/Callora-Frontend:

• src/ApiUsage.tsx
• src/ApiUsage.test.tsx
• src/pages/ApiUsage.tsx
• src/ThemeToggle.tsx
• src/pages/ThemeToggle.tsx

Priority

Low

Acceptance criteria

• src/ApiUsage.tsx is removed
• Unique assertions are ported to pages tests
• No import references the removed file
• Duplicate pairs are listed for follow-up

Validation

npm run build && npm test -- --run src/pages/ApiUsage.test.tsx

Non-goals

• Typo-only, formatting-only, or cosmetic changes.
• Unrelated refactors, dependency upgrades, or broad rewrites.
• Removing safeguards or weakening validation to make tests pass.

Contributor application

Before coding, describe the affected modules, proposed state/invariant changes, test strategy, compatibility considerations, and an estimate. Wait for assignment before starting implementation.

PR requirements

Use a feature branch and include Closes #<issue-number>. Address every criterion, map criteria to code and tests, explain security and failure-mode handling, and ensure CI passes.

Quality review

A maintainer will assess correctness, completeness, test depth, compatibility, observability, and adverse-case handling. A substantive implementation is required; merge or CI status alone does not guarantee reward eligibility.

---

Generated by Claude Code

[Ssoleed]

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

Hello maintainer, i would like to work on this issue

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

[Androrat09990]

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

I’ve carefully reviewed the requirements and can work on resolving the issue while ensuring the implementation meets the stated criteria.

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

[drips-wave]

Congratulations, @Ssoleed! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

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