test(scum): add migration parity fixtures

openspec/changes/move-scum-feature-ownership-to-plugin/implementation-blockers.md

@@ -11,14 +11,21 @@ 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.
 
+Controlled read-only migration fixtures now verify configuration, player
+history, gifts, state-patch audits, and trajectories in
+`plugins/tests/fixtures/scum-migration-parity.ts`. They preserve only
+allowlisted plugin fields and maintain transition provenance. The existing
+isolated Companion tests continue to cover its safe command boundary. Neither
+test set provides an end-to-end SCUM executor or event producer.
+
 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.
+- 5.5 and the remaining end-to-end portion of 6.2: the required adapter
+  coverage and isolated non-production SCUM 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