[codex] generate sync python platform client

[calvin-archastro]

What changed

This updates the Python SDK generator for the sync/async client split and Python naming conventions.

• PlatformClient is the synchronous REST client backed by SyncHttpClient from [codex] add sync Python HTTP client archastro-python#14.
• AsyncPlatformClient remains the async REST client backed by HttpClient.
• Async generated resources are prefixed with Async, for example AsyncTeamResource and AsyncV1.
• Sync generated resources use the unprefixed names, for example TeamResource and V1.
• Auth follows the same convention: AsyncAuthClient for async and AuthClient for sync.
• REST contract tests instantiate PlatformClient, call methods without await, and close each sync client.
• The generator version is bumped to 0.4.0 because the generated Python public surface changes.

Channel generation remains async-only because Phoenix channel/socket workflows are async.

Diagrams

sequenceDiagram
  participant User as Python user
  participant Sync as PlatformClient
  participant Resource as TeamResource
  participant Http as SyncHttpClient
  participant API as Platform API
  participant Async as AsyncPlatformClient
  participant AsyncResource as AsyncTeamResource

  User->>Sync: create client
  Sync->>Resource: bind unprefixed resources
  User->>Resource: teams.list
  Resource->>Http: request
  Http->>API: HTTPS request
  API-->>Http: JSON response
  Http-->>Resource: decoded data
  Resource-->>User: sync return value
  User->>Async: create async client
  Async->>AsyncResource: bind Async resources

Loading

classDiagram
  class PlatformClient {
    V1 v1
    AuthClient auth
    close()
    with_credentials()
  }
  class AsyncPlatformClient {
    AsyncV1 v1
    AsyncAuthClient auth
    async close()
    async with_credentials()
  }
  class V1 {
    TeamResource teams
  }
  class AsyncV1 {
    AsyncTeamResource teams
  }
  class TeamResource {
    list()
    get(team)
  }
  class AsyncTeamResource {
    async list()
    async get(team)
  }
  PlatformClient --> V1
  AsyncPlatformClient --> AsyncV1
  V1 --> TeamResource
  AsyncV1 --> AsyncTeamResource

Loading

Scope

Backend/tooling only: SDK generator and generated Python contract-test templates.

Risk assessment

Medium. This changes generated Python SDK class names and client lifecycle behavior. The change is scoped to Python generation; TypeScript SDK generation and channel runtime behavior are unchanged.

User impact

Generated sync usage:

from archastro.platform import PlatformClient

with PlatformClient(access_token="sat_...") as client:
    user = client.users.me()

Generated async usage:

from archastro.platform import AsyncPlatformClient

async with AsyncPlatformClient(access_token="sat_...") as client:
    user = await client.users.me()

Testing

Passed locally:

• npm test -w @archastro/sdk-generator -- --run __tests__/backends/python.test.ts
• npm run build -w @archastro/sdk-generator
• git diff --check

Follow-ups and known issues

• Depends on [codex] add sync Python HTTP client archastro-python#14 for the hand-maintained SyncHttpClient runtime before regenerated Python SDK output is merged.
• Publish @archastro/sdk-generator@0.4.0 before downstream SDK repos update generated Python output to this surface.

[archastro]

✅ Clean PR, @calvin-archastro! No blocking findings on 9789009 — a few nice things I clocked:

• Clean removal of the old generic dynamic proxy in favor of typed sync wrappers — the not.toContain("class _SyncResourceProxy:") assertion locks that the sync surface keeps concrete signatures. ✨
• Nice lifecycle discipline on the sync client — exception-safe _SyncRunner teardown in with_credentials plus _extra_http_clients tracking so the refresh HttpClient gets closed. 🎯
• Followed the repo's TDD-across-layers convention — sync wrappers land with red-green coverage in resource, auth, client, namespace, and contract-test emitters simultaneously. 🙌

---

_{Reply @archastro <verb>: review · do <pattern> · don't <pattern> · forget <slug> · list}