feat: add runtime action SDK clients

[yazcaleb]

What changed

• Added TypeScript SDK helpers for the iOS runtime approval API:
  • createRuntimeAction(...) posts to /v1/runtime/actions
  • waitRuntimeAction(...) long-polls /v1/runtime/actions/:id/wait
  • RuntimeActionTimeoutError preserves the last observed pending action
• Added matching Python SDK helpers:
  • create_runtime_action(...)
  • wait_runtime_action(...)
  • RuntimeActionCreateRequest, RuntimeActionData, and RuntimeActionTimeoutError
• Exported the new runtime action types/errors from the SDK entrypoints.
• Added focused TS and Python tests for create, wait, and timeout behavior.
• Added a minor changeset for veto-sdk and @veto/python-release.

Why

The platform runtime API is now the canonical SDK release valve for the iOS approval wallet. Agents need a first-class client path to create a pending runtime action and block until the iOS biometric approval flow resolves it.

Validation

• PYTHONPATH=packages/sdk-python /opt/homebrew/bin/python3.11 -m pytest packages/sdk-python/tests/test_cloud_client.py -q → 3 passed
• pnpm --filter veto-sdk exec vitest run tests/cloud/client.test.ts → 17 passed
• pnpm --filter veto-sdk exec eslint src/cloud/client.ts src/cloud/types.ts src/index.ts tests/cloud/client.test.ts
• /opt/homebrew/bin/python3.11 -m ruff check packages/sdk-python/veto/cloud/client.py packages/sdk-python/veto/cloud/types.py packages/sdk-python/veto/cloud/__init__.py packages/sdk-python/veto/__init__.py packages/sdk-python/tests/test_cloud_client.py
• pnpm --filter veto-sdk exec tsc --noEmit -p tsconfig.json
• pnpm --filter veto-sdk build
• Live API smoke, unauthenticated: https://api.veto.so/health returns 200 and POST /v1/runtime/actions returns 401 invalid_api_key, proving the deployed route is present and protected.

Not covered here

A real production create/wait/resolve E2E requires a project-scoped VETO_API_KEY and an available iOS approval device. No VETO_API_KEY is present in the current environment.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None