orchestrate-submission-reviewlisted

# Orchestrate Submission Review This is the last gate, and it exists because a meaningful fraction of lost points in any timeboxed contest are **mechanical, not intellectual** — a malformed CSV, a missing file, a zip with the wrong structure, a README that doesn't explain how to run the thing. None of that reflects your agent's quality, and all of it is 100% preventable with a checklist run at a fixed point before the deadline, not "whenever there's time." ## Do this with time to spare, not at the deadline Run this pass **at least 45–60 minutes before the actual deadline.** Submission portals fail, uploads time out, and a discovered problem at T-minus-10-minutes is a crisis; the same problem at T-minus-60 is a fix. ## Mechanical checks **The code zip:** - Does it actually contain everything needed to run the agent, or does it reference local files/paths that only exist on your machine? - Does a fresh clone/extract + the documented setup steps actually work? (Test this literally — don't assume.) - Are secrets/API keys excluded, and is there a clear `.env.example` or equivalent instead of a hardcoded key? - Is there a README, and does it explain **design decisions**, not just run commands? (See `orchestrate-agent-architecture` — this is scored, not cosmetic.) - Is the zip structured the way the submission instructions ask, or did you guess? **The output CSV:** - Does it parse cleanly with a standard CSV reader — no broken quoting, no stray delimiters from unescaped commas