browser/openspec/changes/complete-platform-web-management-workflows/proposal.md

Why

The platform web console now has the required first-party pages, but several management workflows still depend on local demonstration data or stop at create/status-only interactions. Operators need data-backed editing, deletion, and failure-visible empty states so the console can be used as a real game server operations workspace instead of a partially mocked prototype.

What Changes

• Replace page-visible demo fallbacks for users, AI providers, plugin marketplace data, and server configuration with explicit API-backed loading, empty, and error states.
• Complete user management with edit, role/profile update, status change, and deletion or deactivation workflows backed by platform APIs.
• Complete server management with metadata edit actions such as rename, ownership/admin changes, safe delete/archive, and clear lifecycle/history feedback without exposing run internals.
• Complete plugin marketplace operations with real empty/error states, safe install/enable/disable handling, plugin detail refresh, and no production reliance on pluginCatalog fallback data.
• Complete AI provider management with reliable list-empty behavior, create/update/status/test/model refresh workflows, and deletion or disable-only retirement semantics that preserve secret boundaries.
• Keep the existing platform_web magical game operations visual direction and role-scoped navigation while making pages dense, operational, and browser-verifiable.

Capabilities

New Capabilities

• platform-web-management-completion: Data-backed platform_web management workflows for users, servers, plugins, AI providers, and related operational states.

Modified Capabilities

• None. This change builds on existing workflow specs and adds a frontend completion contract rather than modifying archived requirement files.

Impact

• Affects platform_web/ API types/client methods, page contracts, schemas, server/user/plugin/AI provider pages, stores, tests, and browser acceptance coverage.
• May require platform/ DTOs, validators, services, repositories, and HTTP routes where current APIs do not support edit/delete/retire operations.
• May require updates to frontend structure checks if new shared contract/schema directories or rules are introduced.
• Must not add billing, cloud host sales, agent-provider/cloud-provider workflows, unrelated SaaS marketplace features, raw AI key exposure, raw host path exposure, direct run sockets, or plugin access to platform secrets.