Secure starter submission flow - #3
Merged
Merged
Conversation
KerrikStone
marked this pull request as ready for review
July 23, 2026 17:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
submit.py; completion now confirms evaluation and links to the public replay.MLG-XXXXteam-card format while retaining the explicit demo code.Why
The production rehearsal found that generated team cards use short codes such as
MLG-BHJ3, but the packaged CLI rejected them before contacting the server. The starter also exposed score fields that the event is intentionally removing and documented an obsolete cooldown.Impact
Participants can authenticate with the actual printed card, submit normally, and receive a completion/replay link without score leakage.
Validation
submit.py login MLG-BHJ3config flow passed