Repository navigation
Close hackathon entries and clarify verified reward claims - #94
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 184036ce19
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| export async function runSubmit(_options: SubmitOptions): Promise<never> { | ||
| throw new Error(HACKATHON_CLOSED_MESSAGE); |
There was a problem hiding this comment.
When a maintainer updates an existing archived project, the revised skill directs them to follow submissions/README.md, whose required-files table still advertises the repository version of xagt-plugin submit as a way to generate submission.json. This unconditional exception makes that documented option fail for every input, including archive-maintenance inputs that the change explicitly continues to support. Remove the obsolete instruction from the archived contract or preserve a clearly scoped generation-only path for existing entries.
AGENTS.md reference: AGENTS.md:L9-L12
Useful? React with 👍 / 👎.
The 2026 hackathon has concluded, but the CLI still generated entries and PR instructions and automated receipts promised future results.
xagt-plugin submitnow fails before prompts or file writes; the submission skill and template announce closure. The trusted validator rejects new competition directories before fetching source or contacting deployments, so they cannot reach automatic archival. Maintenance and sealing of existing archived projects remain available.Receipts now post one closure notice with published results and the admin Telegram contact, including once when an open PR has a legacy receipt. Ordinary PRs and closed historical PRs are untouched; the receipt workflow uses current official main code.
The English, Chinese, and Japanese READMEs and permanent winners page now use the same three-step reward claim process: the original PR creator confirms their Telegram on that PR, contacts admin from that account with the PR link, then shares wallet/network privately after verification. admin must verify the comment author against the original PR creator and open the exact Telegram username/link from that comment to confirm the account; display names or screenshots alone are insufficient. The public comment authorizes contact and is not a secret passphrase. A separate literal example and safety reminder replace the old X-reply/direct-wallet guidance. Winners, award amounts, historical source, and ordinary contribution flows are preserved.
Validation:
npm run lint,npm test(98 tests), andnpm run buildpassed.npm audit --audit-level=moderate: 0 vulnerabilities; locked dependencies installed without lifecycle scripts.@YOUR_USERNAME, and admin naming throughout.git diff --checkand lifecycle syntax check passed.Based on freshly fetched main
ff82476b61fbf024b3fd5491593d473a552574f0, including #92 and #93. No payment or award changes.