feat: add baseline anti-cheat protection for issue #2

[rbxict]

Summary

• add the missing Python anti-cheat monitor so the baseline debugger and suspicious-process checks exist for both implementations in issue #2
• keep the native client aligned by fixing the invalid C++ integrity exit code path while preserving the same guarded-exit behaviour
• add focused Python regression coverage and document how to run the checks from a clean checkout

Validation

• python -m py_compile anti_cheat.py
• python -m unittest discover -s . -p "test_*.py" -v

Notes

• I verified the Python monitor locally on this checkout; the C++ path was reviewed at source level but not compiled here because the MSVC toolchain is not installed in this environment

Payout Details

• EVM: 0xe744f6791a685b0A0cC316ED44375B69361c837F
• SOL: 8BsByR6rPqxDPku6dYtdoiSk6bdgE9YETbLQF2RGSw1C

/claim #2

Closes #2
PoA: poa_6c8f67fc40a11300

[rbxict]

I force-pushed a metadata-only follow-up so the branch carries a real CLI-generated PoA in the commit body and the PR reads cleanly. I also re-ran the Python verification on this checkout: python -m py_compile anti_cheat.py and python -m unittest discover -s . -p "test_*.py" -v both pass.