13 lines
1.3 KiB
Markdown
13 lines
1.3 KiB
Markdown
## 1. Reference-Aligned SCUM Operations
|
|
|
|
- [x] 1.1 Positive prompt: Deliver practical SCUM user, squad, map, and gift operations shaped by the mature reference tools while retaining the current plugin/platform/Run ownership model.
|
|
- [x] 1.2 Directional prompt: Update `platform/`, `platform_web/`, and the SCUM plugin package using existing projection, gift, manifest, and themed-console patterns; verify backend, frontend, plugin, structure, and OpenSpec checks.
|
|
- [x] 1.3 Boundary prompt: Do not reintroduce direct SQLite/FTP/browser SQL access, raw RCON, host paths, copied map tiles, unrelated product areas, or a `run/` tree.
|
|
- [x] 1.4 Separate observed timed-gift completion events from platform gift catalog/revision/grant records.
|
|
- [x] 1.5 Resolve SCUM gift item definitions and map geometry from the versioned installed plugin package.
|
|
- [x] 1.6 Implement searchable player and squad-filtered user projections plus roster/flag-aware squad detail.
|
|
- [x] 1.7 Implement layered projection map with plugin-declared coordinate conversion and marker inspection.
|
|
- [x] 1.8 Implement a gift workspace that clearly separates definitions/grants from observed completed timed-gift events.
|
|
- [x] 1.9 Add focused tests and run the required validation suite.
|
|
- [x] 1.10 Stage only task files, commit on `main`, and push the configured remote after verification succeeds.
|