docs: add Cursor Cloud dev environment setup instructions - #1
Draft
qCanoe wants to merge 1 commit into
Draft
Conversation
Co-authored-by: CaNoe <yesterdayhorizon@outlook.com>
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
Sets up and documents the development environment for the Web3 Signature Decoder monorepo. No application code was changed — this only adds
AGENTS.mdwith durable, non-obvious setup guidance for future cloud agents. The startup update script (dependency install + workspace library builds) is configured separately.What was verified
npm install— installs all workspace deps (Node 22.14, npm 10.9).tscper package; snap viamm-snap build).npm run test: 25 Vitest harness tests + 1 Jest snap test all pass.test-api(:4000),test-web(:4173),site(:8000) all serve.decision: block/policyReason: high_riskvia fail-closed path.OPENAI_API_KEY) — benign SIWE login →decision: allow/llm.status: ok; phishing →block;POST /v2/fixtures/validate→pass: trueacross all 8 fixtures.Key non-obvious findings (captured in AGENTS.md)
dist/of@sd/*packages, so the library packages must be built beforedev/testwork.test-apidefaults to port 4005 in code, buttest-web/README default the API base tohttp://localhost:4000— run the API on 4000.OPENAI_API_KEYthe engine is fail-closed: benign requests returnerror, critical-signal requests stillblock;/v2/fixtures/validatereturnspass: false. With the key, benign requests returnallowand validation passes.lintscript / no committed ESLint/Prettier config — stricttscbuild is the effective static check.cleannpm scripts use PowerShell syntax and fail on Linux.Demo
Full LLM-powered flow (ALLOW / BLOCK / validate pass):
signature_decoder_llm_flow_demo.mp4
Benign SIWE login allowed via LLM
All fixtures validate pass:true
Deterministic fail-closed block (no key):
Phishing permit blocked
To show artifacts inline, enable in settings.