browser/openspec/changes/move-scum-feature-ownership-to-plugin/proposal.md

Why

SCUM plugin behavior must survive server updates without treating a game, UE4SS, database, build, or revision string as a feature kill switch. The prior plan incorrectly used static compatibility gates.

What Changes

• Move all SCUM feature authority to the plugin and its Companion, with generic platform authorization, isolation, audit, queue, storage, and Run channels.
• Replace build/version/revision gates with runtime schema and capability probes.
• Let Run provide bounded SCUM stdout/stderr records, typed database reads, and fixed administration operations only through platform-authorized channels.
• Require field allowlists, pre-read/safe-window/write-confirmation flows, and succeeded/failed/unknown results for mutating adapters.
• Preserve fixed-template vehicle.spawn; its private #spawnvehicle <vehicleCode> audit text never enters a result or page payload.

Non-Goals

No arbitrary RCON, SQL, shell, socket, path, DSN, credential, raw database row, OCR, screenshot, keyboard/mouse injection, or desktop automation is introduced. No SCUM import or game.scum branch is added to platform_web.