Set up Cursor Cloud dev environment (pnpm) and correct AGENTS.md#9
Open
ceccec wants to merge 1 commit into
Open
Set up Cursor Cloud dev environment (pnpm) and correct AGENTS.md#9ceccec wants to merge 1 commit into
ceccec wants to merge 1 commit into
Conversation
… caveats Co-authored-by: Tsvetan Rouschev <ceccec@users.noreply.github.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.
What
Sets up and verifies the development environment for this VitePress v2 (alpha) pnpm-workspace site, and corrects
AGENTS.md, whose Cursor Cloud instructions said the project uses npm when it actually uses pnpm (pnpm-lock.yaml,pnpm-workspace.yaml,packageManager: pnpm@11.6.0, and CI'spnpm install --frozen-lockfile).Environment setup
corepack enable pnpm+pnpm install --frozen-lockfile.vitepress buildstep also run on the login-shell default (nvm Node 22.x).AGENTS.md corrections (only clearly-incorrect / durable items)
npm→pnpmacross the quick-reference table and notes (npm ciwould fail — there is nopackage-lock.json).docs:buildis heavy and currently red:vitepress buildrenders ~400 pages in ~3 min and works, but theenforcement-trinityfoldwave (modelSealover the ~2.3 MBsrc/quantum/mind/index.ts) is single-threaded, takes ~50 min, and currently fails with open gates (quantify.gates,dimensions.emerge.within) — reproduced identically in CI (.github/workflows/deploy.yml), i.e. a pre-existing model/seal issue, not an environment problem. The dev server is the practical way to develop/preview.check:types(tsc) can't run because TypeScript is not a declared dependency (CI doesn't run it).PATH/exec-daemon/nodeshadow over nvm.weavewave fails the build if it's removed).Verification
pnpm install --frozen-lockfile✅pnpm run docs:build→vitepress buildproduced 417 HTML pages ✅ (full seal pre-existing red — see above)pnpm run docs:dev✅ — exercised the Quantum Console: ranconcept.self.address,ls, andhelpand saw computed results.quantum_console_dev_demo.mp4
Running
concept.self.addressin the dev server's Quantum Console:concept.self.address computed output
Real-time search for "torus":
search results for torus
To show artifacts inline, enable in settings.