Improve ApiUsage status filter so selecting Success/Error actually filters Call History

[greatest0fallt1me]

Description

This is a UI/UX issue. The "All Status / Success / Error" <select className="filter-select"> in the Call History section of src/ApiUsage.tsx is not wired to any state, so changing it has no effect. Users expect the visible table to update, and there is no empty state when a filter yields no rows.

Requirements and Context

• Wire the status filter to actually filter callHistory rows.
• Add an accessible label to the select and an empty state (via EmptyState) when a filter matches nothing.
• Reflect the active filter in the row count / heading for clarity.
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b task/call-history-status-filter

2. Implement changes
   • src/ApiUsage.tsx — add filter state, derive filtered rows, render EmptyState when empty
   • Add an accessible label to the select
3. Test and commit
   • npm run dev, open /api-usage, switch filters and verify the table updates
   • Include test output and notes in the PR

Example commit message

task: wire call history status filter with empty state

Acceptance Criteria

• Selecting Success/Error filters the visible rows
• The select has an accessible label
• An empty state shows when no rows match
• Row count reflects the active filter

Guidelines

• Reuse the shared EmptyState component
• Clear documentation and inline comments
• Timeframe: 96 hours