feat(scum): add read-only migration flags

2026-07-29 11:57:41 +08:00
parent 47738acfd6
commit 6c503e567c
5 changed files with 105 additions and 8 deletions
@@ -0,0 +1,28 @@
+# Verified implementation blockers
+
+Checked 2026-07-29 against the pinned read-only UE4SS reference at
+`bae91527355f14faa63c1df65f742cc48594ba1b` (UE4SS 3.0.1). The accompanying
+capability evidence is recorded in
+`plugins/examples/scum-server-plugin/companion/UE4SS_CAPABILITY.md`.
+
+The reference offers only a fixed, online-recipient `SendChat` path, which is
+already bounded by the supported `player.notify` adapter. It has no versioned
+server-side schema, identity binding, acknowledgement contract, or isolated
+non-production fixture for login/logout events, network correlation, position
+or vehicle events, reward delivery, or state reads and writes.
+
+Consequently these tasks remain open and blocked rather than simulated:
+
+- 4.1–4.4: no legitimate versioned event producer exists for semantic player,
+  network, position, or vehicle data.
+- 5.1 and 5.3: no documented, version-bound state-patch or reward-delivery
+  adapter exists.
+- 5.5 and 6.2: the required adapter coverage and isolated non-production
+  fixtures do not exist.
+- 6.3: transitional SCUM APIs and models still have callers and cannot be
+  removed before the parity and rollback evidence required by 6.2.
+- 6.4: final full verification is deferred until the blocked adapters and
+  isolated integration environment exist.
+
+No fallback to raw RCON, credentials, SQL, direct game-database access, OCR,
+screenshots, keyboard/mouse injection, or desktop automation is permitted.