23 lines
1.4 KiB
Markdown
23 lines
1.4 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: SCUM plugin package
|
|
The repository SHALL include a first-party local SCUM server plugin package with manifest metadata, create-form schema, lifecycle action templates, and plugin page declarations.
|
|
|
|
#### Scenario: SCUM manifest validates
|
|
- **WHEN** plugin manifest validation runs with default targets
|
|
- **THEN** it MUST validate the SCUM plugin manifest and reject unsafe raw host paths, direct run sockets, bearer credentials, passwords, raw AI keys, and undeclared transport details
|
|
|
|
### Requirement: SCUM plugin marketplace discovery
|
|
The platform SHALL be able to register the SCUM plugin manifest and project it into the plugin marketplace using safe platform registry metadata.
|
|
|
|
#### Scenario: SCUM plugin is discoverable
|
|
- **WHEN** the SCUM plugin manifest is registered through platform APIs
|
|
- **THEN** `GET /api/v1/plugin-marketplace/plugins?serverType=scum&keyword=scum` MUST include the SCUM plugin without exposing unsafe fields
|
|
|
|
### Requirement: SCUM multi-instance creation
|
|
The platform SHALL allow the SCUM plugin to create multiple independent SCUM server instances through the existing platform-mediated server lifecycle workflow.
|
|
|
|
#### Scenario: Two SCUM servers are created from one plugin
|
|
- **WHEN** local debug proof creates two server instances using the SCUM plugin
|
|
- **THEN** both instances MUST have distinct IDs and names, share the SCUM plugin association, and receive independent lifecycle install jobs
|