test: guard Cursor status polling SDK path

[cursor]

Risky behavior now covered

• Cursor status polling uses durable Agent.get(agentId, { apiKey }) metadata instead of the streaming listRuns/getRun path that previously emitted uncaught TransformErrors.
• SDK status and summary are normalized, with missing status defaulting to running.

Tests added

• test/cursor-port.test.ts

Regression value

These tests exercise the real port boundary rather than the adapter's fake port, so reverting the production polling fix or dropping the status fallback fails deterministically. A mutation to the streaming API path made both focused tests fail.

Validation

• npm test — 37/37 passed
• npm run build — passed
• npx prettier --check test/cursor-port.test.ts — passed

  

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
polyagent	Ready	Preview	Jul 30, 2026 10:07am