## Why

The architecture stream has implemented many platform, run, frontend, and plugin capabilities, but the current project still needs an evidence-driven baseline that proves which first-party flows are real, partial, demo-only, or blocked. The next change should verify the existing product surface before adding more product scope, so follow-up work can target gaps instead of assuming the platform is operational end to end.

## What Changes

- Add a baseline verification change that audits current functionality across `platform/`, `run/`, `platform_web/`, and `plugins/`.
- Classify required first-party areas and system flows as `real`, `partial`, `demo-only`, or `blocked` using executable evidence.
- Require API/run/plugin proof commands, frontend build/test commands, structure validation, and browser walkthrough evidence.
- Require a proof report that covers 首页、服务器管理、插件市场、用户管理、AI 提供商管理, run-mediated lifecycle, durable logs, artifact/file transfer, and plugin capability boundaries.
- Keep this change verification-only: it records current reality and follow-up gaps, but does not implement product fixes.

## Capabilities

### New Capabilities

- `current-platform-e2e-baseline`: Evidence-based classification of current platform behavior across backend APIs, run executor channels, frontend workflows, and game management plugin boundaries.

### Modified Capabilities

- None.

## Impact

- Affects OpenSpec verification artifacts and may add proof scripts, reports, or test harnesses under the matching roots.
- Does not add billing, cloud host sales, agent-provider/cloud-provider workflows, unrelated marketplace features, direct browser/plugin access to run, raw host path exposure, or raw AI key exposure.
- Produces follow-up implementation recommendations only after evidence exists.