## Why

The previous SCUM-specific platform grew into a tightly coupled mix of frontend shell, backend services, run executors, client bridges, plugin runtime, file operations, log streaming, database access, and generated rules. The new project needs a clean game server management platform foundation where each subproject has explicit ownership, fixed definition directories, and verifiable change rules from the first commit.

## What Changes

- Create a new four-part project layout: `run/`, `platform/`, `platform_web/`, and `plugins/`.
- Define the platform as a game server management system with 首页、服务器管理、插件市场、用户管理、AI 提供商管理.
- Treat plugins as game management plugins that define how to create and manage game servers; each installed plugin can create many server instances.
- Define AI providers as GPT/OpenAI-compatible/model-provider configuration used by plugins for assisted config reading, config generation, log diagnosis, and server file suggestions.
- Separate run-platform-plugin communication into dedicated channels for control, jobs, logs, artifacts/files, and optional game client bridge behavior.
- Require logs to be a first-class ingestion pipeline with batching, compression, sequence acknowledgement, local spool, storage adapters, and browser tail as a derived view rather than the primary transport.
- Require artifact/file transfer to be chunked, resumable, checksummed, throttled, and isolated from log ingestion and control heartbeats.
- Require every subproject to keep API DTOs, database models, domain structs, shared helpers, validation rules, and frontend types in dedicated directories instead of scattering definitions through business logic.
- Add repository governance files so future changes update rules and run automated structure checks before being considered complete.

## Capabilities

### New Capabilities
- `project-workspace-governance`: Project layout, AGENTS rules, README contracts, and automated structure validation requirements for the four subprojects.
- `game-server-platform-core`: Core platform resources for users, game management plugins, server instances, AI providers, jobs, artifacts, logs, and audit.
- `run-execution-channel`: The run-side control, job, log ingest, artifact transfer, and optional game client bridge contracts.
- `game-plugin-system`: Game management plugin packaging, local development, manifest rules, platform bridge, plugin marketplace, and multi-instance server creation.
- `platform-web-console`: The frontend console structure, plugin page bridge rules, page model, API client layout, and design constraints.

### Modified Capabilities
- None. This is a new project with no existing specs.

## Impact

- Adds project-level rules and documentation under `/Users/tasia/Desktop/code/browser`.
- Establishes OpenSpec artifacts for the initial architecture before implementation begins.
- Affects all future implementation in `run`, `platform`, `platform_web`, and `plugins`.
- Introduces an initial repository structure verifier that future changes must keep updated as rules evolve.