Show cloud computer lifecycle and capacity in chat and status #38

Project

Cloud computer platform

Source: Cloud computer scale architecture audit

Upstream qualification: OpenAgentsInc/openagents#11

Outcome

Give users and operators an accurate view of logical computers, queued work, active runtime leases, failures, cleanup, and quota pressure without exposing raw cloud topology or creating a second state authority.

Scope

Build user and operator projections from the durable cloud-computer and Work authorities. Keep live events bounded and reconstructible after reload.

Chat experience

• Show each logical computer with a stable label and cold, queued, starting, active, stopping, failed, or destroyed state.
• Distinguish logical inventory from active runtime count.
• Show why a computer is queued, including chat concurrency, tenant budget, provider capacity, stale quota, or an incident drain.
• Stream bounded command and lifecycle progress from the existing conversation activity projection.
• Provide owner-scoped start, attach, cancel, stop, checkpoint, restore, fork, and destroy controls only when the current capability allows them.
• Show effective runtime class, custody, network policy, budget, and retained artifact or checkpoint behavior without exposing provider administration details.
• Preserve identical state and controls for text and voice conversations.

Status and operator experience

• Add active, cold, queued, failed, leaked, and quarantined computer counts.
• Show allocatable and reserved CPU, memory, scratch, warm capacity, and cleanup reserve by public-safe runtime class.
• Show quota observation age, configured safety ceiling, remaining headroom, and denied admission counts.
• Show queue time, cold-start time, checkpoint and restore duration, cleanup duration, command ambiguity, reattachment, and zero-residue failure indicators.
• Link bounded incidents and exact qualification or placement receipts.
• Never expose project IDs, zones, hostnames, guest addresses, raw provider errors, credentials, private paths, or customer workspace content.

Deliverables

• Chat components and events for logical computer inventory and lifecycle.
• Owner controls with loading, disabled, refusal, cancellation, and terminal states.
• /status projections and operator detail views.
• Accessible keyboard, focus, contrast, screen-reader, responsive, and empty-state behavior.
• LiveView tests that use stable element IDs and outcome-based assertions.
• Projection contract documentation and privacy review.

Acceptance criteria

• A chat with 30 logical computers and four active leases presents both counts accurately.
• Queued computers update when capacity becomes available without a full-page refresh.
• Reloading chat or /status reconstructs state from durable authority instead of treating missed PubSub events as truth.
• Another owner cannot observe names, commands, checkpoints, usage, or controls.
• Text and voice surfaces render the same logical computer and runtime state.
• Provider topology and secrets do not appear in HTML, JSON, logs, analytics, or browser events.
• The UI remains usable with 30 computers and does not render unbounded output or event history.

Dependencies

Depends on #37 and OpenAgentsInc/openagents#11.

Project linkage

The Projects API currently enforces repository-local project items. This openagents.com issue links the OpenAgentsInc/openagents project here and must appear in the qualification report.