HTTP transport scaffolds (FastAPI vendor + plane apps) — Phase γ

[Faux16]

Context

The sdk-python README lists this under "Does NOT implement yet (Phase 1+)":

HTTP client / server scaffolds (FastAPI vendor + plane apps)

The launch announcement frames this as "Phase γ" — HTTP transport scaffolds. Until they exist, integrating AGP into a real service means hand-rolling the HTTP wiring around the SDK's sign/verify primitives.

Goal

Ship a vendor-side and plane-side HTTP scaffold as a thin, optional module of the SDK:

• openagp.transport.vendor — a FastAPI router (or framework-agnostic ASGI helper) that exposes the discovery endpoint, accepts event-pull requests, and serves the actor's public-key bundle.
• openagp.transport.plane — a FastAPI router that accepts pushed events, verifies them, and offers a hook for downstream storage.

Scope

• Thin: no business logic, just transport. Apps wire in their own persistence.
• FastAPI is the reference; design so the core helpers don't require it (so Flask / Starlette / others can use them).
• Documented examples/mock-vendor and mock-plane (tracked in openagp/examples) use this module.
• Test against agp-cts validate-vendor / validate-plane (tracked in openagp/cts).

Pointers

• SDK current shape: openagp/sdk-python
• Sibling work in TypeScript: openagp/sdk-typescript HTTP scaffolds (filed separately)
• Spec §4.2 Phase 1 build order: concept-and-spec.md