Repository navigation
docs: checks a judge can run without a browser or an API key - #336
Merged
Merged
Conversation
A read of the README as a screening agent would do it found four gaps:
- NearBlocks answers curl with 403, so the transaction links cannot be
opened by a script. Added one public archival RPC command.
- docs/openapi.json has 64 operations; the README and the docs site said
63, and the README table missed GET /v1/minds/{mindId}/payments.xlsx.
- "Run locally" had no bun install for apps/fe.
- The tests line did not say which tests need no API key.
Tests, in a clean checkout with no .env and no keys: engine test:unit
198 pass; apps/be test 165 pass, 1 skipped (local Postgres, fake
engine); apps/fe test 280 pass. The RPC command and the xlsx route were
run against testnet and the hosted demo. Mintlify validate and
broken-links pass. cargo test in sc/ was not run here (CI covers it).
No load test: only documentation changed.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q5ZrzK8une3S2YyhDG746e
Contributor
Author
|
Merged as @Lin1er @AncungAulia @Nabil-Aufa for your information: the README and JUDGE.md now say which tests run with no API key and no |
Contributor
|
Live on the hosted demo:
|
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.
A read of the README the way a screening agent would do it (every link, every command, every number) found four gaps. Everything else matched: 22 linked transactions exist and succeeded, the RPC commands print the code hashes in the tables, and steps 1 to 6 of "Through the API" work on the hosted demo.
What changed
curlwith403, so a script cannot open the transaction links. Added one command against a public archival RPC, with what it prints.apps/docs/api.mdx:docs/openapi.jsonhas 64 operations, not 63. The README table now hasGET /v1/minds/{mindId}/payments.xlsx.bun installforapps/fe..env, and which need a NEAR AI Cloud key.Tests
.env, no keys:enginetest:unit198 pass;apps/betest165 pass, 1 skipped (local Postgres, fake engine);apps/fetest280 pass.SuccessValue, from the Mind wallet tolin1er.testnet, aTransferof 0.01 NEAR.payments.xlsxon the hosted demo with a guest session: 200, Excel content type.validateandbroken-links --check-anchors: pass.cargo testinsc/andsc/swarm/(CIsccovers them). No load test: only documentation changed.🤖 Generated with Claude Code
https://claude.ai/code/session_01Q5ZrzK8une3S2YyhDG746e