Skip to content

Fix: require manifest/log packet for PLAYER-CAPTURE VERIFIED claim#1

Open
marko1olo wants to merge 1 commit into
mainfrom
fix-proof-gate-player-capture-verified-9293077728624285275
Open

Fix: require manifest/log packet for PLAYER-CAPTURE VERIFIED claim#1
marko1olo wants to merge 1 commit into
mainfrom
fix-proof-gate-player-capture-verified-9293077728624285275

Conversation

@marko1olo
Copy link
Copy Markdown
Owner

This PR improves proof-hygiene by narrowly strengthening the static validator. It ensures that raw PNG/MCP screenshot sets cannot erroneously be claimed as "PLAYER-CAPTURE VERIFIED" without a corresponding manifest/log packet passing the validation gate.

Changes:

  • validate_proof_packet.py: Set mayClaimPlayerCaptureVerified to evaluate to status == PASS_STATUS.
  • unity_process_proof_watchdog.py: Propagate the boolean and output it to the payload and Markdown report.
  • test_validate_proof_packet.py: Update the static gate packet acceptance test to assert mayClaimPlayerCaptureVerified is True.

This affects the First 20 Minutes surface/photic route proof acceptance gates.

Evidence class: STATIC VERIFIED
Files changed:

  • Tools/ProofGate/validate_proof_packet.py
  • Tools/ProofGate/unity_process_proof_watchdog.py
  • Tools/ProofGate/test_validate_proof_packet.py

PR created automatically by Jules for task 9293077728624285275 started by @marko1olo

* Updated `Tools/ProofGate/validate_proof_packet.py` to set `mayClaimPlayerCaptureVerified` to `True` when a packet passes the static validation gate.
* Updated `Tools/ProofGate/unity_process_proof_watchdog.py` to propagate this boolean and include it in the Markdown report so human reviewers can easily see if a raw/MCP screenshot set without a manifest is trying to claim verification.
* Updated `test_validate_proof_packet.py` tests to expect the new behavior.

Co-authored-by: marko1olo <96879250+marko1olo@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant