browser/openspec/changes/add-scum-file-config-workbench/proposal.md

Why

SCUM operators currently reach separate overview, configuration, and semantic-log surfaces, even though their routine operational work begins with declared files and safe, modeled settings. The default SCUM work surface needs to make configuration actionable without revealing host paths or turning raw text editing into the normal workflow.

What Changes

• Replace the SCUM overview-first experience with a unified 文件与配置 workbench whose default scope is the plugin-declared configuration directory.
• Add plugin-declared logical file directories/files and a modeled configuration-field catalog, including Chinese labels, help, control metadata, constraints, defaults, restart impact, and owning file.
• Reuse Platform-mediated file requests and the existing configuration diff-preview/approval/write flow so modeled changes are previewed before dispatch; expose completed declared-file reads through a bounded, redacted Platform snapshot rather than through host paths or general job payloads.
• Expose logs as declared log files inside the same workbench, with separate safe log-file scope; retain unknown configuration fields as read-only information.
• Replace the static, stacked SCUM panels with a single selection-based file workbench: directory/file navigation on one side and the selected file's modeled configuration, optional raw config mode, or read-only log content on the other.
• Embed the workbench inside the server detail section without a second plugin-page header or unrelated Companion feature panels.
• Safely migrate legacy SCUM overview/config/log routes to the new workbench.

Capabilities

New Capabilities

• scum-file-config-workbench: Declared SCUM file scopes, modeled configuration editing, log-file viewing, and safe route migration.

Modified Capabilities

• config-write-and-file-dispatch: File dispatch and config approval now consume declared logical directories/files and field ownership metadata.
• scum-operations: SCUM's primary operator surface changes from an overview to the file-and-configuration workbench.

Impact

• Affects the SCUM plugin manifest/declarations, Platform plugin validation and safe file/config DTO handling, and SCUM frontend contracts/routes/components.
• Reuses files.request, existing server configuration diff/approval/write APIs, and the SCUM runtime profile; adds a Platform-owned read-result projection without expanding filesystem or remote-access authority.