Use dynamic category titles and update descriptions to match live site

- Remove hardcoded category title mapping, use simple title-casing from schema
- Update category descriptions to match sprites.dev/api documentation

Co-Authored-By: Claude Opus 4.5 <[email protected]>

Author: kylemclaren

scripts/generate-api-docs.ts

@@ -837,22 +837,7 @@ ${streamingEventsDocs}
 }
 
 function getCategoryTitle(category: string): string {
-  const titles: Record<string, string> = {
-    sprites: 'Sprites',
-    exec: 'Exec',
-    checkpoints: 'Checkpoints',
-    services: 'Services',
-    proxy: 'HTTP Proxy',
-    policy: 'Policy',
-    organization: 'Organization',
-    tokens: 'Tokens',
-    files: 'Files',
-    filesystem: 'Filesystem',
-    attach: 'Attach',
-  };
-  return (
-    titles[category] || category.charAt(0).toUpperCase() + category.slice(1)
-  );
+  return category.charAt(0).toUpperCase() + category.slice(1);
 }
 
 // Manual pages that are not generated from schema but should be included
@@ -885,17 +870,21 @@ const MANUAL_PAGES: ManualPage[] = [
 
 function getCategoryDescription(category: string): string {
   const descriptions: Record<string, string> = {
-    sprites: 'Create, list, update, and delete Sprites',
-    exec: 'Execute commands in Sprites via WebSocket',
-    checkpoints: 'Create, list, and restore environment snapshots',
-    services: 'Manage background services running in Sprites',
-    proxy: 'Forward HTTP requests to services inside Sprites',
-    policy: 'Manage access control policies',
-    organization: 'Organization settings and information',
-    tokens: 'Create and manage API tokens',
-    files: 'Upload and download files',
-    filesystem: 'Browse and manage the filesystem',
-    attach: 'Interactive terminal sessions via WebSocket',
+    sprites:
+      'Sprites are persistent environments that hibernate when idle and wake automatically on demand. You only pay for compute while actively using them—storage persists indefinitely.',
+    exec: 'Run commands inside Sprites over WebSocket connections. The exec API is designed for both one-shot commands and long-running interactive sessions.\n\nSessions persist across disconnections—start a dev server or build, disconnect, and reconnect later to resume streaming output. A binary protocol efficiently multiplexes stdin, stdout, and stderr over a single connection.',
+    checkpoints:
+      "Checkpoints capture your Sprite's complete filesystem state for instant rollback. They're live snapshots—creation takes milliseconds with no interruption to running processes.\n\nUse checkpoints before risky operations, to create reproducible environments, or to share known-good states across a team. Copy-on-write storage keeps incremental checkpoints small; you only store what changed.",
+    services: 'Manage background services running in your Sprite environment.',
+    proxy:
+      'Tunnel TCP connections directly to services running inside your Sprite. After a brief WebSocket handshake, the connection becomes a transparent relay to any port.\n\nUse this to access dev servers, databases, or any TCP service as if it were running locally. The proxy handles connection setup; your client speaks directly to the target service.',
+    policy:
+      'Control outbound network access using DNS-based filtering. Policies define which domains sprites can reach, with support for exact matches, wildcard subdomains, and preset rule bundles.\n\nChanges apply immediately—existing connections to newly-blocked domains are terminated. Failed DNS lookups return REFUSED for fast failure.',
+    organization: 'Organization settings and information.',
+    tokens: 'Create and manage API tokens.',
+    files: 'Upload and download files.',
+    filesystem: 'Browse and manage the filesystem.',
+    attach: 'Interactive terminal sessions via WebSocket.',
   };
   return (
     descriptions[category] || `${getCategoryTitle(category)} API endpoints`