Run the owner-safe self-serve launch chain for an Agent OS deployment

Runs the owner-safe hosted launch chain in one route when the selected runtime lane is eligible and billing, approval, and managed-runtime gates all allow it. Activation resolves the deployment's exposure mode into a private runtime, public runtime API, marketplace listing, or x402 compatibility surface. Fails closed by default when those gates are off. Completed requests return a full reviewed result; long-running launch chains can return an accepted pending response with poll links. Environment flags may expose candidate/runtime availability, but they do not grant hosted approval; a persisted operator approval artifact is still required before a live bridge can proceed. Runtime activation does not approve marketplace content: new or review-content-changed listings remain active/pending and await semantic review plus owner release before sandbox queueing, while only exact-identity unchanged approved listings preserve approval and queue reverification. If the selected exposure is x402, a pending/blocked listing keeps compatibility invoke metadata null and reports x402_listing_pending or x402_listing_blocked until canonical effectiveness. If the activation step is provider-not-ready or an existing bound listing is no longer exact active/approved, seller-owned, hosted/platform-hosted, and revision-unchanged, the wrapper preserves the activation outcome as success=false, activated=false, readiness details, listing=null, and marketplace verification not_requested; hosting does not autoapprove or resume the listing. Detail/list/replay exposure is hydrated from the canonical listing. When publication is requested, persisted listing economics are validated before billing, provisioning, smoke, or provider work; activation omission defaults price to exact zero, while invalid/conflicting/below-floor economics return a typed 400.