Document final tournament results#27
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a08b79c937
ℹ️ 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".
| | Runtime health | [Inspect network, credentials and data-licence state](https://pulseproof-production-06fa.up.railway.app/api/health) | | ||
| | Devnet program | [Open Solana Explorer](https://explorer.solana.com/address/74cvsTMZpcgrzVT7ufSjtjy8gqU2m1q3jy3n1UGxRMkn?cluster=devnet) | | ||
| | Final CI | [154 tests, lint, build and native contract tests](https://github.com/cryptovuive/pulseproof/actions) | | ||
| | Final CI | [156 tests, lint, build and native contract tests](https://github.com/cryptovuive/pulseproof/actions) | |
There was a problem hiding this comment.
Keep the Judge Room CI count aligned
After this documentation update, visitors following the public submission path will see contradictory evidence: the README reports 156 tests, but the committed Judge Room still renders 154 tests in app/submission/page.tsx:217. Update that user-facing card as part of the evidence refresh so judges do not have to reconcile two different CI totals.
Useful? React with 👍 / 👎.
Summary
Validation
The unrelated local docs/YOUTUBE.md working-tree state is intentionally excluded.