Problem
No ongoing (post-checkout) account-settings/billing-management UI surface is specced anywhere. Exhaustive search across "billing", "checkout", "account settings", "customer portal", "manage subscription", "invoice history", "payment method" turned up nothing. #4930 covers only the one-time signup/checkout/plan-selector flow (initial purchase); #4920 is the backend data model only. Nothing tracks an ongoing self-service page for updating a payment method, viewing invoice history, or changing/canceling a plan.
Area
apps/loopover-ui/, hosted-product onboarding cluster (#4926/#4930/#4931/#4932).
Proposal
Define, at spec level: what an ongoing account-settings surface needs to expose (payment method update, invoice/receipt history, plan change/cancellation) — this is the natural sibling to #4930's one-time checkout flow, currently missing from the tracker entirely.
Deliverables
Resources
Boundaries
Spec only — depends on #4919/#4920/#4930 landing first for the underlying billing system to manage.
maintainer-only — product spec, depends on unbuilt billing infrastructure.
Problem
No ongoing (post-checkout) account-settings/billing-management UI surface is specced anywhere. Exhaustive search across "billing", "checkout", "account settings", "customer portal", "manage subscription", "invoice history", "payment method" turned up nothing. #4930 covers only the one-time signup/checkout/plan-selector flow (initial purchase); #4920 is the backend data model only. Nothing tracks an ongoing self-service page for updating a payment method, viewing invoice history, or changing/canceling a plan.
Area
apps/loopover-ui/, hosted-product onboarding cluster (#4926/#4930/#4931/#4932).Proposal
Define, at spec level: what an ongoing account-settings surface needs to expose (payment method update, invoice/receipt history, plan change/cancellation) — this is the natural sibling to #4930's one-time checkout flow, currently missing from the tracker entirely.
Deliverables
Resources
Boundaries
Spec only — depends on #4919/#4920/#4930 landing first for the underlying billing system to manage.
maintainer-only — product spec, depends on unbuilt billing infrastructure.