## ADDED Requirements

### Requirement: Reference-aligned SCUM projection workspaces
The system SHALL present SCUM users, squads, map points, and gifts as connected operator workspaces backed by platform projections and typed workflows.

#### Scenario: Operator filters users by squad
- **WHEN** an operator searches or selects a squad in the SCUM users workspace
- **THEN** the page filters real local player projections by the selected name, Steam identifier, or squad without querying `SCUM.db` from the browser

#### Scenario: Operator inspects a squad
- **WHEN** an operator selects a squad
- **THEN** the page shows its observed members, leader markers, and related flag observations without fabricating missing values

### Requirement: Plugin-declared SCUM map geometry
The system SHALL use SCUM plugin package geometry to project current map-point overlays.

#### Scenario: Operator changes map layers
- **WHEN** an operator enables or disables players, vehicles, bases, or flags
- **THEN** the map renders only the selected real projection classes using the installed plugin's declared coordinate frame

### Requirement: Distinct observed and operational gifts
The system SHALL keep observed SCUM timed-gift completion events separate from platform-owned gift definitions and grant state.

#### Scenario: Operator opens gifts
- **WHEN** an operator opens SCUM gift management
- **THEN** the workspace distinguishes platform gift definitions and grants from completed in-game timed-gift observations

### Requirement: Versioned plugin game data
The system SHALL resolve SCUM gift item definitions from versioned plugin package data.

#### Scenario: SCUM version changes
- **WHEN** the server uses a plugin package with a different declared SCUM item catalog
- **THEN** gift validation uses that plugin package data without changing platform source code