AntiSkidAC compatibility notes

AntiSkidAC verifies client installations and maintained known runtime indicators:
- logical loaded-mod identities and versions,
- attributed physical mod JAR BLAKE3-256 hashes,
- required/prohibited/approved-mod policy,
- explicitly configured managed files and directory content,
- nonce-bound manifest responses, runtime reports and heartbeat deadlines,
- maintained known class, registry and exposed network indicators.

Normal gameplay remains authoritative in Minecraft, Forge and gameplay mods.
AntiSkidAC has no movement, reach, CPS, rotation, inventory/window or ability
heuristics to enable. Client resource baselines are best-effort observations,
not proof that transformed runtime classes or the whole process are trustworthy.

Native Forge targets: 1.6.4, 1.7.10, 1.8.9, 1.12.2, 1.16.5, 1.18.2 and 1.20.1.
Native NeoForge target: 1.21.11. Use the matching Minecraft/loader artifact.
Java 8 is required through 1.16.5; 1.18.2/1.20.1 require Java 17; 1.21.11 requires Java 21.
Forge 1.6.4 retains stock ASM 4.1; its production classes use Java 7 bytecode.
Development directories/virtual roots are not approved physical artifacts.
Nested JAR bytes are hashed when exposed; no whole nested dependency graph is attested.
Legacy brand/payload violation scoring and verbose/file diagnostics are available
on 1.7.10/1.8.9/1.12.2; other adapters enforce manifests and client runtime reports. No UniMixins/Mixin dependency is
required by AntiSkidAC. The shared core is bundled inside the adapter JAR.
The integrated-server owner is exempt from the remote attestation exchanges;
remote LAN guests and dedicated-server clients must satisfy server policy.

Server policy is authoritative, but a hostile client can falsify its reports.
The server cannot directly inspect native DLL attaches, client classloader
mutation or client event registration. No process, browser or arbitrary machine
scan is performed. Only configured installation content is read for attestation.
