Set up Cursor Cloud dev environment + document run/test workflow

[jpt4]

Summary

Sets up the development environment for the Strait of Hormuz tower-defense project (Node self-play tooling + single-file browser game) and documents the non-obvious run/test workflow for future cloud agents. No application code was modified.

• Added a ## Cursor Cloud specific instructions section to AGENTS.md covering: no build step / empty lockfile, the npm test / npm run test:extended commands, how to serve and play hormuz-game.html, and gotchas (browser placement zones, no window game API, self-play/run.js balance auto-commits, shared headless/browser game logic).
• Update script (startup dependency refresh): npm ci.

Verification

Environment validated end-to-end:

• npm ci — clean, 0 vulnerabilities (no runtime deps).
• npm test — 23/23 pass (5 suites).
• npm run test:extended — headless game smoke passes; engine places units and runs a full ~7300-tick game.
• Browser game served via python3 -m http.server 8000; loaded hormuz-game.html, in-browser regression suite auto-ran (132/136; the 4 failures are pre-existing ADR-0005 adaptive-difficulty checks unrelated to setup), and completed the hello-world action of placing defensive units (FUNDS drops $500M→$250M for ASCM Battery, then by $45M for Drone Swarm) which then engage enemy waves.

Hello-world play (unit placement)

hormuz_unit_placement_demo-2.mp4

ASCM Battery placed: FUNDS dropped to $250M, unit inspection panel + range ring
In-browser regression suite results in console

test_output.log

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