Add challenge solver withdrawal continuity guard#370
Open
haki203 wants to merge 1 commit into
Open
Conversation
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.
Summary
challenge-solver-withdrawal-continuity-guard/slice for Scientific Bounty System issue Scientific Bounty System #18.Non-overlap
This is not another intake, rubric readiness, submission privacy, solver prequalification, data-room access, scoring/arbitration, appeals, anti-collusion, escrow settlement, payout eligibility, sponsor reliability, amendment consent, reviewer consensus, IP redaction, milestone progress, evidence freeze, clarification freeze, award transparency, benchmark leakage, deliverable acceptance, reproducibility environment, license/dependency, human-subjects, or cancellation/no-award slice. It focuses specifically on solver withdrawal and replacement continuity after work has started.
Validation
node --test challenge-solver-withdrawal-continuity-guard/test.js-> 3 tests passedFFMPEG_PATH=<local ffmpeg-static binary> node challenge-solver-withdrawal-continuity-guard/demo.js-> generated JSON/Markdown/SVG/MP4 reviewer artifactsnode --check challenge-solver-withdrawal-continuity-guard/index.jsnode --check challenge-solver-withdrawal-continuity-guard/sample-data.jsnode --check challenge-solver-withdrawal-continuity-guard/demo.jsnode --check challenge-solver-withdrawal-continuity-guard/test.jsffmpeg -v error -i challenge-solver-withdrawal-continuity-guard/reports/demo.mp4 -f null --> decoded without errorsgit diff --cached --checkSynthetic data only. No credentials, private challenge files, payment processor calls, bank/ACH/wallet actions, KYC, payout systems, sponsor data rooms, live workspaces, or external APIs are used.
/claim #18