admin343/browser
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor(scum): declare protected run requests

Browse Source
This commit is contained in:
npc0-hue
2026-07-29 22:37:16 +08:00
parent d7465bfd32
commit 99be8f0f3a
28 changed files with 497 additions and 152 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/move-scum-feature-ownership-to-plugin/implementation-blockers.md
+9 -6
View File
@@ -5,13 +5,16 @@ features are not disabled by an update string. The Companion uses typed,
platform-authorized non-production fixtures for configuration, player-state,
reward, notification, and vehicle operations; no remote server is contacted.
Run's required integration boundary is a bounded stdout/stderr record stream,
typed database projections, and fixed administration ports. It must not expose
paths, DSNs, credentials, raw rows, arbitrary SQL, shell, socket, or RCON to
the plugin, platform web, or AI. Unknown console formats create a bounded
diagnostic and no event.
Run's required integration boundary is a bounded stdout/stderr console record
stream and declared protected SQL, RCON, or management-program transports.
Plugins generate bounded request text, while Platform authorizes, approves,
queues, redacts, and forwards it only to the bound Run request. Run alone
resolves its local transport. Paths, DSNs, credentials, raw connections, host
paths, sockets, and host OS shell access never reach the plugin, platform web,
or AI. Unknown console or request formats create a bounded diagnostic for the
affected request and no fabricated event.
Remaining production enablement is operational: a deployed Run implementation
must provide the declared typed ports. Until then only the affected operation
must provide the declared protected transports. Until then only the affected operation
is reported unavailable; the plugin page and unrelated feature capabilities
remain active.