IG Comment validity follows subscription end_date (Billing V1/V3)

Jira: BIF-8718 · Epic: BIF-8695

Overview

• Before: IG Comment has its own valid_until.
• After: IG Comment always follows the component_code from Mekari Billing, with valid_until = the organization's subscription end_date.

Component: QONTAKCHAT-IGComment — https://billing.mekari.com/admin/components/197

Scope Changes

• Backend — billing subscription-update sync for the IG Comment component.

Out of scope

• Mid-term component removal is not handled — the feature remains active until end_date even if the component is dropped from a later billing update (decision: off at end_date only).

8. User Stories + Acceptance Criteria

User Story	Importance	Mockup / Technical Notes	Acceptance Criteria
[IGCM-S01] — IG Comment follows subscription end_date As the billing sync system, I want the IG Comment feature's validity to follow the organization's subscription end_date instead of its own valid_until, so that IG Comment stays consistent with the customer's Mekari Billing subscription.	Should Have	Component 197: QONTAKCHAT-IGComment. Applies to billing V1 and V3.	— Happy Path — • AC-1: Given a CID receives a subscription update from Mekari Billing and the CID is billing V1 or V3, when the update contains the IG Comment component (QONTAKCHAT-IGComment), then enable IG Comment with valid_until = the organization's subscription end_date. • AC-2: Given IG Comment is enabled, when the organization's subscription end_date passes, then IG Comment is disabled (expires at end_date).

Open questions

1. Existing CIDs that currently have their own valid_until — migrate on the next billing update, or one-off backfill?
2. Behaviour if the subscription end_date is null/absent in the update.