Revert SCUM real data management change

platform_web/contracts/pages.md

@@ -2,7 +2,7 @@
 
 ## Shared Visual Contract
 
-All first-party pages inherit the platform_web game-operations style with black-mecha default materials and a selectable magical-girl theme. Page implementations must use shared theme tokens and surface classes so 首页、服务器管理、插件市场、用户管理、AI 提供商管理、系统维护, server details, drawers, dialogs, safe diffs, plugin-declared pages, and job/status surfaces all feel like one console.
+All first-party pages inherit the platform_web game-operations style with black-mecha default materials and a selectable magical-girl theme. Page implementations must use shared theme tokens and surface classes so 首页、服务器管理、插件市场、用户管理、AI 提供商管理、系统维护, server details, drawers, dialogs, safe diffs, plugin-declared pages, and workflow/status surfaces all feel like one console.
 
 - Major surfaces remain transparent jelly/glass panels with visible background desktop, icy rim light, diamond borders, shine sweeps, and candy-color accents.
 - Built-in magical desktops and user-uploaded backgrounds render behind readable contrast surfaces.
@@ -23,7 +23,7 @@ Default landing page for server owners and server administrators. Shows searchab
 
 ## 服务器详情
 
-Daily operations hub for one server. Status header shows online state, player count, TPS, latency, CPU/memory/disk progress, metric freshness, and confirmed start/stop lifecycle actions. Plugin-declared pages render as first-class server tabs before platform sections, so each game owns its safe menu surface; SCUM detail uses exactly 用户管理, 队伍管理, 实时地图, 礼包管理, and AI 助手. SCUM deployment and administrator settings move to compact header/list actions instead of a permanent management tab, and AI suggestions produce reviewable config diffs or named-field drafts without raw AI keys reaching the frontend. Raw logs, management terminal/RCON input, arbitrary config workbench, generic operation history, runtime-binding, and generic plugin-control tabs must not be exposed in server detail.
+Daily operations hub for one server. Status header shows online state, player count, TPS, latency, CPU/memory/disk progress, metric freshness, and confirmed start/stop lifecycle actions. Plugin-declared pages render as first-class server tabs before platform sections, so each game owns its safe menu surface; SCUM pages use projection-backed users, squads, map, gifts, and workflows. Built-in sections are 管理 (deployment status, metadata, administrators) and AI 助手 (LLM suggestions produce reviewable config diffs or typed workflow drafts; no raw AI keys reach the frontend). Raw logs, management terminal/RCON input, arbitrary config workbench, generic operation history, runtime-binding, and generic plugin-control tabs must not be exposed in server detail.
 
 ## 插件市场
 

platform_web/contracts/plugin-page-bridge.md

@@ -25,7 +25,7 @@ Plugin page runs with safe platform context.
 - `plugin-lifecycle.request`: declared plugin lifecycle request through Platform.
 - `ai.invoke`: platform-mediated AI invocation.
 
-The host intersects manifest-level and page-level permissions/actions before exposing context. SCUM pages receive only declared local-resource actions for 用户管理, 队伍管理, 实时地图, 礼包管理, and AI 助手; the host does not synthesize undeclared SCUM semantics.
+The host intersects manifest-level and page-level permissions/actions before exposing context. The SCUM operations page additionally intersects its command, snapshot, and query-template keys with `gameClientBridge.pages.operations`; it does not synthesize undeclared SCUM semantics.
 
 ## Forbidden
 

platform_web/contracts/pluginPageHost.ts

@@ -1 +1,14 @@
-export interface PluginPageWorkspaceActions {}
+export interface PluginPageWorkspaceActions {
+  listSCUMPlayers?: () => Promise<unknown>;
+  listSCUMSquads?: () => Promise<unknown>;
+  listSCUMSquadMembers?: () => Promise<unknown>;
+  listSCUMVehicles?: () => Promise<unknown>;
+  listSCUMFlags?: () => Promise<unknown>;
+  listSCUMPositions?: () => Promise<unknown>;
+  listSCUMOperations?: () => Promise<unknown>;
+  createSCUMOperation?: (request: unknown) => Promise<unknown>;
+  approveSCUMOperation?: (operationId: string) => Promise<unknown>;
+  listSCUMWorkflows?: () => Promise<unknown>;
+  createSCUMWorkflow?: (request: unknown) => Promise<unknown>;
+  listSCUMWorkflowSteps?: (workflowId?: string) => Promise<unknown>;
+}