fix(docker): use WindMagi offline operator UUID
Release / release (push) Successful in 2m18s
CI / build (push) Successful in 1m21s

This commit is contained in:
dmg
2026-08-11 18:25:23 -04:00
parent 2e6fdb4e5b
commit 904faf1832
6 changed files with 29 additions and 5 deletions
+7
View File
@@ -2,6 +2,13 @@
## 2026-08-11
### US-010 offline operator identity corrected
- Reproduced WindMagi's missing operator privileges and found that name-based image setup stored the online account UUID while offline-mode login assigned deterministic UUID `6a3b6e9f-1a2f-380c-8a75-7a7ca6392c0e`.
- Replaced name-based setup with a synchronized, committed operator fixture containing the exact offline UUID; synchronization intentionally makes WindMagi the sole operator in this isolated test harness.
- Removed the misleading post-start `op WindMagi` check and made startup verify the exact name and UUID in the generated `ops.json`.
- Live restart verification passed: Spigot was healthy, RCON reported TreeFeller, `ops.json` contained only WindMagi at level 4 with the offline UUID, and the server remains available at `localhost:25565`.
### US-010 local Docker test server completed
- Added a repository-local Docker Compose harness using `itzg/minecraft-server:java25` with Spigot 26.2, persistent ignored state, offline local testing, and loopback-only port binding.