Console: group org sidebar + split Activity pages + add Storage (PVC instances)

[rowan-stein]

User request

We refactored Console navigation; now implement the updated spec:

• Group the organization sidebar into 5 always-expanded groups.
• Split the old combined Monitoring view into 4 separate Activity pages/routes: Workloads, Storage, Threads, Usage.
• Implement the Activity → Storage page showing persistent volume instances/PVCs.

Source doc: agynio/architecture/changes/2026-04-22-console-sidebar-grouping.md

Decisions provided:

• Used: skip/placeholder if no field exists.
• Storage lists actual volume instances/PVCs.
• Name: use an id for now.

Specification (from architecture)

Sidebar grouping

Per product/console/console.md#sidebar and change doc, org sidebar must render 5 always-expanded groups (no collapse UI):

1. Organization: Overview, Members
2. Agents: Agents, Volumes, Runners, Apps
3. Models: LLM Providers, Models
4. Secrets: Secret Providers, Secrets, Image Pull Secrets
5. Activity: Workloads, Storage, Threads, Usage

Activity split + Monitoring removal

• Replace the combined Monitoring page with separate routes/pages under Activity:
  • Workloads
  • Storage
  • Threads
  • Usage
• Remove Monitoring from nav.
• Back-compat: old Monitoring route should redirect to Activity → Workloads.

Storage page

Per product/console/console.md#storage:

• Table columns:
  • Name (id for now)
  • Size (provisioned size)
  • Used (placeholder if not available)
  • Attached to (agent/MCP/hook or “unattached”)
  • Status (bound, pending, released, failed)
• Default sort: name.
• Data source: volume instances from Runners (PVC-level), via Gateway.

Required cross-repo changes

This feature requires coordinated updates:

1. agynio/api: expose volume query methods on agynio.api.gateway.v1.RunnersGateway:
   • GetVolume
   • ListVolumes
   • ListVolumesByThread
2. agynio/gateway: implement the new ConnectRPC endpoints by forwarding to RunnersService.
3. agynio/console-app: UI changes (sidebar grouping, Activity routes, Storage page).

Acceptance

• Org sidebar renders 5 groups with headers/spacing; no collapse interaction.
• Workloads/Storage/Threads/Usage are separate routes/pages reachable from sidebar.
• Storage page lists runner volume instances with required columns (Used shown as placeholder if unavailable).
• Old Monitoring page is removed; old Monitoring route redirects to Workloads.