docs: add Cursor Cloud specific instructions for env setup

[code-yeongyu]

What

Sets up the Cloud Agent development environment for the senpi monorepo and records the durable, non-obvious caveats for future cloud agents under a new ## Cursor Cloud specific instructions section in AGENTS.md.

This PR contains a single docs change (AGENTS.md). No runtime source is touched, so the changelog gate passes. The remaining setup lives in the VM update script (Node 24 provisioning + npm install --ignore-scripts + node scripts/devenv-setup.mjs), not in the repo.

Environment findings

• Node runtime gotcha: the VM's ambient node (/exec-daemon/node) is v22, but package.json#engines requires >=24. Node 24 is installed via nvm and symlinked into /usr/local/cargo/bin (first, writable PATH entry) so bare node/npm/npx resolve to v24 for every shell. /exec-daemon is read-only sandbox infra and is never modified.
• No provider keys configured: the CLI boots but shows "No models available". The full agent loop is exercised with zero tokens via the senpi-qa mock-loop channel (local fake model server).

Verification

Step	Command	Result
Install	node scripts/devenv-setup.mjs	508 pkgs + skill deps, exit 0
Lint / static	npm run check	exit 0 (biome, pinned-deps, ts-imports, shrinkwrap/install-lock, tsc --noEmit, browser-smoke)
Tests	npm test	exit 0 (all workspaces, e.g. tui + sqlite-node 87/87)
QA self-tests	common / cli-smoke / rpc-drive / mock-loop	9/9, 8/8, 4/4, 48/48
Hello-world	mock-loop.mjs --with-tool	4/4 — full agent turn (model → bash tool → final text)
App run	./pi-test.sh (TUI)	boots, renders header + extensions, accepts composer input

Demo

Full agent turn (executes a bash tool end-to-end) then the real interactive TUI booting from source:

senpi_agent_turn_and_tui_demo.mp4

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

  

---

Summary by cubic

Adds a "Cursor Cloud specific instructions" section to AGENTS.md to document Cloud Agent environment setup and prevent common pitfalls. Previously the docs lacked cloud-specific guidance; now they cover Node 24 setup, running without provider keys, and tooling behavior.

Cursor Cloud caveats

• Node runtime: the VM’s ambient node is v22 but package.json#engines requires >=24. Use nvm-installed Node 24 symlinked in /usr/local/cargo/bin; if node shows v22, rerun the VM update script or recreate symlinks. Do not modify /exec-daemon.
• Provider keys: none are configured by default. Use the senpi-qa mock loop (.agents/skills/senpi-qa/scripts/mock-loop.mjs --with-tool) for full agent turns without credentials; add real keys (e.g., ANTHROPIC_API_KEY) to .env.local only if needed.
• Run from source: launch the TUI via ./pi-test.sh; no build step required.
• Lint/tests: npm run check formats files and may leave the tree dirty; npm test runs the full workspace and is slow—scope to a single package during iteration.

^{Written for commit 19f0a1f. Summary will update on new commits.}