feat: merge Limits + Usage into unified Spend page (#24093)

docs/ai-coder/agents/platform-controls/index.md

@@ -113,14 +113,14 @@ This setting is available under **Agents** > **Settings** > **Behavior**.
 The maximum configurable value is 30 days. When disabled, workspaces follow
 their template's autostop rules (or none, if the template does not define any).
 
-### Usage limits and analytics
+### Spend management
 
 Administrators can set spend limits to cap LLM usage per user within a rolling
 time period, with per-user and per-group overrides. The cost tracking dashboard
 provides visibility into per-user spending, token consumption, and per-model
 breakdowns.
 
-See [Usage & Analytics](./usage-insights.md) for details.
+See [Spend Management](./usage-insights.md) for details.
 
 ### Data retention
 

docs/ai-coder/agents/platform-controls/usage-insights.md

@@ -1,11 +1,11 @@
-# Usage and Analytics
+# Spend Management
 
-Coder provides two admin-only views for monitoring and controlling agent
+Coder provides admin-only controls for monitoring and controlling agent
 spend: usage limits and cost tracking.
 
 ## Usage limits
 
-Navigate to **Agents** > **Settings** > **Limits**.
+Navigate to **Agents** > **Settings** > **Spend**.
 
 Usage limits cap how much each user can spend on LLM usage within a rolling
 time period. When enabled, the system checks the user's current spend before
@@ -53,7 +53,7 @@ their effective limit, current spend, and when the current period resets.
 
 ## Cost tracking
 
-Navigate to **Agents** > **Settings** > **Usage**.
+Navigate to **Agents** > **Settings** > **Spend**.
 
 This view shows deployment-wide LLM chat costs with per-user drill-down.