Skip to content

feat(sdk): implement Phase 1 generated Python core - #3

Draft
hyperSuperCube wants to merge 1 commit into
tokencanopy:mainfrom
hyperSuperCube:agent/python-sdk-implementation
Draft

feat(sdk): implement Phase 1 generated Python core#3
hyperSuperCube wants to merge 1 commit into
tokencanopy:mainfrom
hyperSuperCube:agent/python-sdk-implementation

Conversation

@hyperSuperCube

Copy link
Copy Markdown

Summary

  • import the reviewed AgentDrive Phase 1 contract from server commit 31cd35c8e12aef1cbee228e965289107cb51092c (27 paths, 42 operations, 38 component schemas)
  • generate isolated Python sync (urllib3) and async (httpx) cores under agentdrive_sdk.generated
  • add deterministic model and transport postprocessing, exact sync/async contract gates, direction-aware compatibility checks, generated manifest/reference drift checks, and release-version integrity
  • generate the detailed Python API reference from OpenAPI plus committed generated source, including every callable variant, status/model/header map, and recursively documented anonymous error schemas
  • reuse the same full acceptance workflow for PRs and publishing; restrict publishing to approved main history

Companion SDK design: tokencanopy/agentdrive#431.

Compatibility

This is the reviewed one-time Phase 1 reset from the pre-Phase 1 110-operation 0.0.1 client contract to the supported 42-operation machine API. The reset is bound to the exact old/new contract digests and source commit. Normal directional compatibility enforcement applies after this contract becomes the base.

Validation

  • 46/46 contract and generation helper tests
  • 14/14 Python conformance/model-policy tests on Python 3.10, 3.12, and 3.14
  • exact 42-operation sync/async callable, parameter, request, response, auth, and header parity
  • Python sdist/wheel build and twine check
  • TypeScript npm ci + build; Go go test ./...
  • pinned full regeneration run twice; committed worktree remains byte-clean
  • independent final audit approved with no blockers

Release safety

No package was published and no release or Go tag was created. Before approving the first 0.1.0 publish, verify PyPI and npm trusted-publisher OIDC ownership after the GitHub repository transfer.

The ergonomic Phase 2 Python facade remains a separate follow-up; this PR intentionally delivers the complete generated core first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant