Added: Cloud Agent development environment config

[rahulsainlll]

What & why

Adds a committed Cursor Cloud Agent environment so the repo becomes fully usable in Cloud Agents out of the box. Previously a fresh agent booted with nothing configured (no dependencies, no database). This provisions the whole local development experience — install, PostgreSQL, migrations, seed data, and the dev servers.

New files (all under .cursor/):

• environment.json — declares install, start, three dev-server terminals (api, web, dashboard), and exposes ports 3000/3001/3002.
• install.sh — one-time, idempotent setup: corepack + pnpm install --frozen-lockfile, installs PostgreSQL 16, prepares a local .env (generated ENCRYPTION_KEY/AUTH_SECRET, local DB URLs), symlinks per-app .env for the Next.js apps (they don't read the repo-root .env), runs Drizzle migrations, and seeds two demo capabilities so the gateway + catalog have something to serve.
• start.sh — per-boot reconciliation: starts PostgreSQL (idempotent), ensures .env/links exist, and applies any new migrations.

No application code is changed.

Type of change

• Feature
• Fix
• Refactor / chore
• Docs / tooling (developer environment)

Validation

All CI quality gates pass locally on this environment:

Check	Result
pnpm install --frozen-lockfile	Passed (and idempotent on re-run)
pnpm format:check	Passed
pnpm lint	Passed (warnings only)
pnpm typecheck	Passed (14 workspaces)
pnpm test	Passed (7 suites)
pnpm build	Passed (11 tasks)

End-to-end product flow verified against the running stack:

• GET /health → {"status":"ok","service":"tael-api"}
• GET /capabilities → serves the seeded capabilities from PostgreSQL
• POST /c/fx-rates (no payment) → HTTP 402 Payment Required with a valid x402 challenge (price, payTo, USDC asset, network) — the core product interaction
• Web /capabilities page renders the seeded capabilities fetched live from the local API:

Tael capabilities page served from the local API + Postgres

Environment build validation: a draft Cloud Agent environment build of this exact config succeeded — .cursor/install.sh ran cleanly in the build pipeline (dependencies installed, PostgreSQL started, migrations applied, seed idempotent, exit code 0).

Fresh Cloud Agent validation: a brand-new agent booted from that tested build passed all checks — node v22.14.0 / pnpm 11.5.2, dependencies present, 12 tables + both seeded capabilities in Postgres, .env + per-app symlinks in place, API /health + /capabilities + the 402 x402 challenge all correct, and pnpm test 7/7 suites passing.

Checklist

• pnpm lint && pnpm typecheck && pnpm test && pnpm build pass locally
• Added/updated tests for the change (N/A — environment tooling only)
• Added a changeset (N/A — no published @tael/* package changed)
• Updated docs (N/A — no boundary/public API changes)

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

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tael-dashboard	Ready	Preview	Aug 10, 2026 6:01am
tael-protocol-dashboard	Ready	Preview	Aug 10, 2026 6:01am

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.