chore: add Cloud Agent development environment config

[runnabro]

What

Adds a repository-managed Cloud Agent environment config at .cursor/environment.json so Cursor Cloud Agents boot rdme with a fully prepared development environment.

{
  "name": "rdme",
  "install": "npm ci && npm run build"
}

• npm ci installs dependencies from the committed package-lock.json (deterministic).
• npm run build compiles TypeScript to dist/ so the production entrypoint (bin/run.js) works immediately.

No custom Dockerfile is needed — the default image already provides Node (>=20.10.0 engine requirement is satisfied). No start/terminals are needed because rdme is a CLI, not a long-running service. No secrets are required for install, build, test, or offline command runs (tests mock network via nock).

Validation

All commands run from a clean checkout on the default VM Node (v22.14.0):

Check	Result
npm ci && npm run build	Exit 0 (idempotent — ran twice)
bin/run.js --version	rdme/10.10.0-next.4 linux-x64 node-v22.14.0
bin/run.js openapi validate (fixture)	Valid OpenAPI definition
bin/dev.js openapi validate (via tsx)	Valid OpenAPI definition
npm test (vitest + coverage)	37 files, 698 passed, ~98% statements
Fresh Cloud Agent draft build	SUCCEEDED (npm ci + npm run build exit 0, snapshot ready)

Notes

• npm run lint's oxlint step loads a TypeScript config (oxlint.config.ts), which requires Node ^20.19.0 || >=22.18.0. The Cloud Agent's pinned default node is v22.14.0, so bare npm run lint fails at that step. Under a CI-matching Node (CI uses lts/*; the VM has v22.22.2 / v24.15.0 via nvm), knip, oxlint, and oxfmt all pass clean. This is a Node-version detail, not caused by this config.
• npm run lint's schemas:check step reports the committed test/helpers/github-workflow-schema.json is outdated vs. the upstream JSON Schema Store (fixed by maintainers with npm run schemas:write). This is pre-existing repo content drift, unrelated to environment setup.

  

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge because the new environment configuration matches the repository’s build requirements and was validated in a fresh Cloud Agent environment.

_{Reviews (1) · Last reviewed commit: "chore: add Cloud Agent environment confi..."}