Billing Expired Handling

Initiative owned by the Bifrost team. Introduces a limited-access mode for expired Qontak One accounts (unified_app = true), replacing the current hard-lockout with controlled permission-key-based restrictions that preserve access to essential data and a clear renewal path via the existing subscription-end banner.

Scope Changes

• Backend — billing_status expiry event handling; billing_expired_limited_access flag enforcement; permission key evaluation against show_when_billing_expired column
• Frontend — Subscription-end banner trigger on billing_status = expired; hide/disable UI elements per permission key evaluation
• Mobile — Permission key enforcement on mobile via existing Chat and CRM permission key implementation

Initiatives

• prds/prd-qontak-one-billing-expired-handling.md — PRD: Qontak One Billing Expired Handling
• rfcs/billing-expired-handling.md — RFC: backend show_when_billing_expired gate (moderator-be + qontak-launchpad + hub_core); FE banner/UI restriction is a deferred, separate RFC

QA Lane

Lane B — keeps a human QA gate. Money-critical: drives billing-expiry and subscription-state transitions, and Mobile is in scope (out of automation reach). No E2E test specs exist for this initiative yet, so the Lane-A entry bar (100% E2E, spec-mapped coverage) is unmet regardless. Classified by Yoddi, Izzul (QA), 2026-06-26.