Repository navigation
0.7: Polish Python SDK for the image runtime #303
Description
Activity
Prepared an isolated Python existing-session handle draft as local commit
54191c8c0a959b93b144aa0feafe1c0ecb76fd72(not pushed or integrated).The reviewed interface is
Hypervisor.vm(*, id=None, name=None) -> VM. It reuses the existing selector and shared authenticated transport. Attachment sends no HTTP request; names resolve once on the first operation. Closing a handle preserves its parent connection and session, and closing the parent prevents further requests from borrowed handles.Evidence on the draft:
- 14 actual RED failures for the missing method, followed by all 14 passing against the implementation.
- Complete Python SDK owner: 338 passed, zero skips or deselections, 98.92% branch-aware coverage against the unchanged 90% floor.
- Configured Ruff, strict cross-platform Ty, generated-contract check, wheel/sdist build and 64 relevant Citadel checks passed.
Separate clean installation of the exact wheel and sdist is now being verified. Existing package metadata remains 0.6.3; this is preparation, not final 0.7 package or publication proof.
This issue remains open. Integration is held on runtime qualification and the service/OAuth dependencies. Image/cache/credential/discovery APIs, managed ownership, real-gateway lifecycle acceptance and final release/fresh-install proof remain required.
Parent: #289. Inspect source: #291.
Work boundary 5/13 from the approved 0.7 → clients → Inspect sequence.
Dependencies: #301, #302.
Retain PyPI capsem. Provide friendly typed images/cache/session/credentials APIs, existing-session handles and managed ephemeral ownership. Centralize discovery, paths and typed errors for Inspect reuse.
Acceptance criteria:
Planned PR boundaries: Python SDK polish separate from regenerated contracts and Inspect.
Implementation progress and evidence: Sprinty in the isolated
integration/0.7-clients-inspectworktree. Focused tests during development; fast checks/Citadel per PR; relevant black-box proof for runtime, credential or image boundaries. Respect the active release and machine locks.