docs: correct data0 sibling-checkout note in Cursor Cloud instructions - #17
Draft
sskyy wants to merge 1 commit into
Draft
docs: correct data0 sibling-checkout note in Cursor Cloud instructions#17sskyy wants to merge 1 commit into
sskyy wants to merge 1 commit into
Conversation
Co-authored-by: Zhenyu Hou <skyking_H@hotmail.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
While setting up the Cloud Agent development environment, I found one now-inaccurate statement in
AGENTS.md's## Cursor Cloud specific instructions.The old note claimed
data0has "no sibling checkout present here" and referencedvite.config.ts. In this multi-repo workspace the sibling../data0repo is checked out, and it'svitest.config.ts(notvite.config.ts) that aliasesdata0to../data0/srcwhen the sibling exists. Updated the bullet to describe the actual resolution behavior for both the test suite (sibling../data0/src) and the production build (npm-installeddata0for externalized code + bundled types).No code changes — documentation only.
Verification
npm install+npx playwright install chromium+npm run build(emitsdist/)npx vitest run— 398 browser tests pass (Vitest + Playwright chromium, headless)npx vitest run --config vitest.node.config.ts— 6 node tests passaxii-benchmarkapp runs against the freshly builtdist/axii.jsand a benchmark scenario executes end to end.