[Bug][Mobile] Usage fails on mobile although desktop returns usage data

[cachetronaut]

Description

The iOS mobile Usage screen fails to report usage for the neo environment, even though the desktop Usage screen returns real usage data for the same T3 Code setup.

The screenshots use different periods. Desktop shows 30 days, Aug 4 to Sep 2. Mobile shows 7 days, Aug 27 to Sep 2. The desktop screenshot is evidence that usage data exists. It is not a direct same-period numeric comparison.

Actual behavior

Desktop:

• The Usage screen loads successfully for Aug 4 to Sep 2.
• It shows $643.11 and 64 sessions.
• It shows 1.29B processed tokens.
• It shows $4,027.51 in cache savings.

Mobile:

• The 7 days view shows neo could not report usage.
• The chart shows No activity in this window.
• Raw token cost shows $0.00.
• Processed tokens shows 0.
• The screen does not clearly distinguish unavailable usage from genuine zero activity.
• The screen does not provide a clear retry action.

Expected behavior

• Mobile should load usage for the selected period when the data source is available.
• If neo cannot report, show it as unavailable instead of presenting zero totals as confirmed data.
• If another environment reports successfully, show its partial totals and identify neo as unavailable.
• If all environments fail, show a clear error state with a retry action.
• Keep the selected period unchanged while the app reports the error or retry state.

Steps to reproduce

1. Use a T3 Code setup with recent agent activity.
2. Open Usage on desktop and confirm that usage data appears.
3. Open the same setup in the iOS mobile app.
4. Open Usage.
5. Select 7 days.
6. Observe neo could not report usage, $0.00, 0 processed tokens, and No activity in this window.
7. For an exact comparison, select the same 7 days period on desktop.

Environment

• Device: iPhone
• App: T3 Code mobile
• App version/build: not visible in the screenshots
• Server or nightly build: not captured
• Connection type: not captured

Acceptance criteria

• Failed environments reach a visible error or timeout state.
• Reachable environments still contribute usage totals.
• All-failed states include a retry action.
• Failed usage requests are not shown as confirmed zero usage.
• The mobile result is consistent with the desktop result when both clients use the same period and connected environments.

Related reports and changes

• Usage tab keeps loading until every connected machine is online (#6363)
• Open PR: unreachable environments no longer block the Usage tab (#5920)
• Usage page presents a rate-table failure as $0.00 instead of saying cost is unavailable (#5948)

This report is narrower than the linked items. The mobile screen reaches an error and empty state while desktop returns usage data.