Add SCUM file management workbench

2026-08-04 11:33:34 +08:00
parent 2921edb401
commit f028a343d7
36 changed files with 1384 additions and 158 deletions
@@ -14,16 +14,19 @@ The SCUM plugin already declares runtime config mappings and log sources, while
 **Non-Goals:**

 - Arbitrary filesystem browsing, path entry, terminals, FTP/rsync controls, raw secrets, or host/socket exposure.
- Raw text as the default configuration editor, write access for unknown fields, or a new run-side protocol.
+- Raw text as the default configuration editor, direct write access for unknown fields, or a new run-side protocol.
 - Changing global server-list behavior or non-SCUM plugin pages.

 ## Decisions

 1. Add `fileWorkspace` to the plugin manifest/runtime projection. It contains safe logical directories/files and modeled fields, rather than host paths or unbounded schemas. This makes a page contract auditable and keeps ownership with the plugin.
 2. Give every modeled field an owning logical file key, Chinese operational metadata, and constrained control details. The frontend uses only these fields to compose proposed INI content; unmapped lines remain visible as read-only field records.
-3. Reuse `GET /config`, config diff preview, and config approval for the declared primary config file. Log-file selection maps declared logical files to existing Platform log streams; no new direct file-read API is introduced.
+3. Reuse declared file read/write dispatch for logical file keys. A completed `files.read` job may be projected through a Platform-owned declared-file snapshot endpoint, which accepts only a declared logical file key, returns no host path or job payload, and redacts secret-like assignment values before returning content. Modeled edits and optional raw config edits require a visible diff preview before the Platform queues a declared `files.write` job.
 4. Move SCUM from `operations` to `files-config`; the route resolver redirects old `overview`, `config`, `logs`, and `operations` keys only for `game.scum`. Other plugins keep their declared page keys unchanged.
 5. Build page content from existing shared console form/list/diff classes. No page-owned surface system or global decoration is added.
+6. Treat the SCUM workbench as one selected logical file at a time. The left pane contains only declared directories and files. The right pane presents either modeled fields or an optional raw mode for an editable configuration file, and a read-only log view for a log file. Selection changes must not trigger unbounded polling or path-based requests.
+7. Render the plugin bundle in embedded mode when it is mounted under a server-detail section. The generic plugin page frame and host-context diagnostics remain available for direct plugin routes, but must not be nested inside the file-management tab.
+8. Keep Companion player, reward, state, vehicle, and trajectory controls out of this page. Those remain available through their separately scoped plugin-control experiences and must not obscure the file workflow.

 ## Risks / Trade-offs

@@ -31,6 +34,8 @@ The SCUM plugin already declares runtime config mappings and log sources, while
 - [Existing installations still link old route keys] → normalize those keys in the common resolver before page lookup.
 - [A declared log stream is absent] → show an explicit unavailable state and never fall back to a filesystem path.
 - [INI parsing has formatting limits] → patch only declared simple key/value fields and rely on Platform preview before approval.
+- [A raw file has not completed an authorized read] → show an explicit pending or empty state rather than an invented template or stale file content.
+- [A declared file contains a secret-like assignment] → redact its value in the snapshot while retaining the surrounding file structure for operational review.

 ## Migration Plan