[liguochuan00]

What

Set up the Cloud Agent development environment for this repository and documented durable, non-obvious startup/run caveats for future cloud agents.

This PR only adds a ## Cursor Cloud specific instructions section to the root AGENTS.md. No product code was changed.

Environment setup performed

Node v22.14.0 is already available (satisfies engines.node >=16; website needs >=22.12.0).

• Root workspace (packages/core + packages/cli): npm ci --ignore-scripts
• Docs site (website/, Astro — not part of npm workspaces): npm --prefix website ci

The update script (run on VM startup) is configured to these two commands, matching the CI workflow.

Verification

Product	Lint	Test	Build	Run
CLI / Core (root workspace)	no lint tooling in repo — kb check (part of npm test) acts as static check	npm test ✅ (17 topics, routing drift: no, all scripts/test-*.js pass) + npm run test:core ✅	none (pure JS)	node cli.js init cursor --yes --locale en-US scaffolded .Knowledge/ + .cursor/ in a temp repo ✅
Docs site (website/)	n/a	n/a	npm --prefix website run build ✅ (20 pages)	astro dev serving http://127.0.0.1:4321/Flow2Spec/ → HTTP 200 ✅

Hello-world (core functionality): initialized a Flow2Spec scaffold in a fresh temp git repo via the CLI, producing .Knowledge/, .cursor/rules, .cursor/skills, and flow2spec.config.json.

Website dev server rendered and navigated correctly:

flow2spec_website_running.mp4

Notes

• The site uses base path /Flow2Spec; the root path / returns 404 by design.
• website/ is not in the workspaces array, so it needs a separate install.
• Root AGENTS.md is regenerated from templates/{locale}/AGENTS.md by sync:agents/init, which does not preserve custom sections. This section is repo-specific and intentionally not placed in templates/; a future re-distribution would overwrite it. VM startup only runs the update script (dependency install), not sync:agents, so the section remains visible to future cloud agents.

_{To show artifacts inline, enable in settings.}