feat(scum): rebuild plugin-owned management data
This commit is contained in:
@@ -8,6 +8,11 @@ Platform SHALL persist opaque plugin records scoped by plugin identifier, server
|
||||
- **THEN** Platform stores the opaque record without interpreting SCUM fields
|
||||
- **AND** another plugin or server instance cannot read the record through the scoped API
|
||||
|
||||
#### Scenario: Plugin updates a collection atomically
|
||||
- **WHEN** an authorized plugin page submits a transaction containing collection puts and deletes
|
||||
- **THEN** Platform validates the complete transaction before applying it
|
||||
- **AND** the repository exposes the resulting records as one collection change
|
||||
|
||||
### Requirement: Plugin-Owned SCUM Domain
|
||||
The SCUM plugin SHALL own its collection names, record schemas, gift behavior, map behavior, and version-specific data extraction assets.
|
||||
|
||||
@@ -23,3 +28,8 @@ SCUM machine SQLite, configuration, and log operations SHALL remain plugin-decla
|
||||
- **WHEN** a SCUM page requests a declared data refresh
|
||||
- **THEN** Platform routes the declared operation through Run
|
||||
- **AND** neither the page nor Platform's generic collection API accepts a raw host path or arbitrary SQLite statement
|
||||
|
||||
#### Scenario: Run reports declared query rows
|
||||
- **WHEN** Run completes a declared SQLite query with a structured `rows` result
|
||||
- **THEN** Platform uses only the plugin-declared collection, upsert keys, and column mappings to persist the rows
|
||||
- **AND** Platform does not branch on the game, query key, collection name, or row fields
|
||||
|
||||
Reference in New Issue
Block a user