test(scum): verify companion dispatch boundaries

This commit is contained in:
npc0-hue
2026-07-29 11:03:06 +08:00
parent acf4e4a8f0
commit 32015a4d9b
6 changed files with 109 additions and 29 deletions
@@ -0,0 +1,34 @@
# Pinned UE4SS capability evidence
This Companion has inspected the read-only reference repository at commit
`bae91527355f14faa63c1df65f742cc48594ba1b` (`scum_simple_rcon_ue4ss` v0.1.0,
verified build target RE-UE4SS 3.0.1).
## Verified capability
The source implements a game-thread `SendChat <type 0-7> "message"
[SteamID64]` path. A targeted send accepts only a 17-digit SteamID64 that
resolves to a real, currently online `ConZPlayerController` with a live
`UNetConnection`; it fails closed when the reflected
`MiscStatics:SendChatLineToPlayer` schema differs. This can support a
version-bound, typed `player.notify` adapter once the deployed Companion is
given a platform-authorized typed transport. The adapter must use one fixed
chat type, cannot accept arbitrary RCON text, and may place its generated
command text only in protected audit data.
## Explicitly unavailable
The reference contains no versioned server-side producer or documented API for:
- successful player login/logout records;
- raw network identity/fingerprint values suitable for correlation;
- player or vehicle position, or player/vehicle transitions;
- item/reward delivery; or
- skill/attribute read, safe-window checking, or mutation.
Therefore the Companion must not parse invented `LOGIN`/`LOGOUT` lines, upload
semantic events, correlate network identifiers, or claim trajectory, reward,
or game-state-patch support from this reference. The missing contract is a
version-pinned UE4SS extension/API that defines the event or operation schema,
identity binding, acknowledgement/result semantics, and non-production
integration fixture for each capability.