Repository navigation
Prepare forty-team DevDay rehearsal fixtures and runbook - #18
Merged
Merged
Conversation
soohyunme
marked this pull request as ready for review
October 8, 2026 16:53
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
2 participants
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.
Prepare a forty-team DevDay rehearsal under
devday-rehearsal-2026on the existing shared platform. The previous two-team QA event remains intact. Application support and migration 0016 are in https://github.com/soohyunme/hackathon-platform/pull/17.Add an event-bound seed/deadline tool and an operational runbook. Seed creates twenty synthetic teams per track, an event-only QA administrator, three first-round judges per track and six common final judges, forty synthetic PDFs/ZIPs and QA draft scoring sessions. It copies actual submission fields/saved rubrics and uses the application workbook template when actual rubrics are absent. Use one DB transaction; refuse to overwrite an existing rehearsal. Store passwords and submission codes only in a mode-0600 private administrator file, then distribute individual credentials through private channels.
Validation in a disposable PostgreSQL database: 40 complete code receipts; 80 authorized downloads with byte-identical SHA-256; ZIP integrity; per-track judging access; common-final access to both tracks; QA accounts denied access to the actual event. The app integration also exercises freeze, scoring and aggregation. Deadline controls are hard-bound to the rehearsal event and audited.
This PR changes no production deployment manifest or real event data. Shared API/DB/storage/cookie origin are intentional after the user's clarification; this is not infrastructure isolation. Draft pending authorization for the application's shared DB range-check migration, rollout and live rehearsal seed. No live seed has run.