@aglyn/aglyn 1.0.0-beta.143

package/src/lib/app-utils/release-flags.js

@@ -0,0 +1,518 @@
+/**
+ * @license
+ * Copyright 2026 Aglyn LLC
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */ /**
+ * Release flags (AGL-227): platform-level "is this feature launched"
+ * gating backed by Firebase Remote Config. A separate axis from plan
+ * entitlements (`plan-entitlements.ts`) — entitlements ask whether the
+ * tenant's PLAN includes a feature, release flags ask whether the feature
+ * is released to the public at all (or partially, via percentage rollout).
+ * Staff bypass release flags everywhere but see a flagged warning.
+ */ /** Remote Config parameter keys for release-gated features. */ import { _ as _extends } from "@swc/helpers/_/_extends";
+import { PLAN_LABELS, SELF_SERVE_PLANS } from "./plan-entitlements.js";
+import { PLATFORM_BRAND_NAME } from "./platform-brand.js";
+/**
+ * The registry: one entry per gated feature. Adding a flag = add it here,
+ * seed it in the Remote Config template, and (optionally) wrap the page in
+ * `<FeatureGate>` — the staff admin editor and nav filtering pick it up
+ * from this list.
+ */ export const RELEASE_FLAGS = [
+    {
+        key: 'release_crm',
+        label: 'CRM',
+        description: 'The CRM: contacts, leads, companies, deals, tasks, reports and fields.',
+        defaultEnabled: true,
+        navTabId: 'nav-tab-contacts'
+    },
+    // Sequences (AGL-2974): the plugin's kill switch as well as its launch
+    // gate, like every first-party plugin's flag since AGL-422 — off, it is
+    // subtracted from the console loader and the API dispatcher for everyone
+    // but staff. OFF by default, because nothing behind it sends mail yet and
+    // no plan carries the `outreach` entitlement it also needs. The KEY stays
+    // `release_outreach`: it is persisted in Remote Config (AGL-3199).
+    {
+        key: 'release_outreach',
+        label: 'Sequences',
+        description: 'One-to-one, multi-step email sequences sent from a rep’s own ' + 'connected mailbox and logged in the CRM (AGL-2974). OFF by default ' + 'and staff preview only. An organization also needs the `outreach` ' + 'entitlement, which no plan carries, so a customer reaches it only ' + 'through a per-org entitlement override.',
+        defaultEnabled: false,
+        navTabId: 'nav-tab-org-outreach'
+    },
+    {
+        key: 'release_bookings',
+        label: 'Bookings',
+        description: 'Bookings & scheduling for host sites.',
+        defaultEnabled: true,
+        navTabId: 'nav-tab-bookings'
+    },
+    {
+        key: 'release_events',
+        label: 'Events',
+        description: 'Event calendar management (AGL-145 add-on surface).',
+        defaultEnabled: true,
+        navTabId: 'nav-tab-events'
+    },
+    {
+        key: 'release_data_store',
+        label: 'Data store',
+        description: 'Datasets, models and dynamic data bindings.',
+        defaultEnabled: true,
+        navTabId: 'nav-tab-data'
+    },
+    {
+        key: 'release_workflows',
+        label: 'Automation',
+        description: 'Workflows, actions, webhooks and their run history.',
+        defaultEnabled: true,
+        navTabId: 'nav-tab-workflows'
+    },
+    {
+        key: 'release_redirects',
+        label: 'Redirects',
+        description: 'Redirect manager with usage analytics.',
+        defaultEnabled: true,
+        navTabId: 'nav-tab-redirects'
+    },
+    {
+        key: 'release_commerce_v2',
+        label: 'Commerce v2',
+        description: 'Full ecommerce wave: catalog/variants, cart + checkout, digital ' + 'goods, reservations, POS, and the repriced commerce tiers ' + '(AGL-276..331).',
+        defaultEnabled: true
+    },
+    {
+        key: 'release_member_accounts',
+        label: 'User Accounts',
+        description: 'Visitor accounts on published sites: the /signin, /signup and ' + '/recover pages and the Members blocks (AGL-2486). Platform-wide ' + 'kill switch only — whether a given SITE serves those pages is the ' + 'per-site User Accounts toggle, which is off until a site opts in.',
+        defaultEnabled: true
+    },
+    {
+        key: 'release_marketplace',
+        label: 'Marketplace',
+        description: 'Marketplace browsing, publishing and plugin installs.',
+        defaultEnabled: true,
+        // AGL-1654: was 'nav-tab-marketplace', which matched no nav item, so
+        // `gateNavTabItems` never hid the tab. The org Marketplace tab is a
+        // console constant rather than a plugin nav item, so the id has to be
+        // kept in step with `org-nav-tabs.ts` by hand; the spec
+        // `release-flag-nav-tab-ids.spec.ts` is what holds it there.
+        //
+        // The second half of that comment — "the page behind it carries no
+        // `<FeatureGate>`" — was still true until AGL-2019 and is no longer.
+        // Flipping this flag off used to subtract the marketplace plugin from
+        // the loader and both API dispatchers while the page went on rendering
+        // in full, so the OFF state was itself broken and "just turn the flag
+        // off" was not an available answer for an operator who does not want a
+        // marketplace. The page is gated now, so off means off.
+        navTabId: 'nav-tab-org-marketplace'
+    },
+    // AGL-422: every first-party plugin is release-flagged — the flag now
+    // feeds the plugin LOADER (console, published sites, API dispatch), not
+    // just nav visibility, so staff can kill-switch a whole plugin platform-
+    // wide from the Feature Flags page.
+    {
+        key: 'release_marketing',
+        label: 'Marketing',
+        description: 'Overlays, campaigns at-a-glance, and A/B experiments.',
+        defaultEnabled: true,
+        navTabId: 'nav-tab-marketing'
+    },
+    {
+        key: 'release_email',
+        label: 'Email',
+        description: 'Designed emails, campaigns, and audience sending.',
+        defaultEnabled: true
+    },
+    {
+        key: 'release_inbox',
+        label: 'Inbox',
+        description: 'Form submissions, site members, and the lead inbox.',
+        defaultEnabled: true,
+        navTabId: 'nav-tab-inbox'
+    },
+    {
+        key: 'release_logic',
+        label: 'Logic',
+        description: 'Variables, no-code functions, and reference health.',
+        defaultEnabled: true,
+        navTabId: 'nav-tab-logic'
+    },
+    {
+        key: 'release_addon_store',
+        label: 'Add-on store',
+        description: 'Self-serve add-on purchases on the Billing page: seats, datasets, ' + 'extra sites, POS registers, Event Calendar (AGL-524..531).',
+        defaultEnabled: true
+    },
+    {
+        key: 'release_native_checkout',
+        label: 'In-page checkout',
+        description: 'Pay without leaving the page, instead of a redirect to ' + 'checkout.stripe.com. TWO surfaces: the console plan checkout uses ' + 'embedded Checkout (AGL-1132), and a merchant storefront uses the ' + 'Payment Element on the merchant\u2019s own domain (AGL-1944) \u2014 ' + 'which is the half that costs conversions, since leaving the store ' + 'mid-purchase is where carts get abandoned. Both keep the webhook as ' + 'the only thing that fulfils. OFF by default: the redirect is the ' + 'proven path, and neither surface can be verified without putting a ' + 'real card through it. Also gated on a publishable key being set, ' + 'per surface \u2014 so flipping this alone degrades to the redirect ' + 'rather than to a dead button.',
+        defaultEnabled: false
+    },
+    // Released to every site 2026-09-16 (AGL-3041). Still the whole surface's
+    // kill switch, globally or for one org by override: off, the tenant slot
+    // renders nothing, both token mints refuse, and `/api/edit-context` turns
+    // away every token already issued.
+    {
+        key: 'release_edit_bar',
+        label: 'Site admin bar',
+        description: 'Admin bar on published sites: a signed-in editor jumps from a live ' + 'page into the besigner for the screen serving it. Released ' + '2026-09-16 (AGL-3041) for every site; turning it off hides the bar ' + 'and revokes every outstanding edit token at the verify site.',
+        defaultEnabled: true
+    },
+    {
+        key: 'release_assist',
+        label: `${PLATFORM_BRAND_NAME} Assist`,
+        description: 'The in-console AI chat helper on every page (AGL-1860): docs-' + 'grounded answers with deep links, page-context guidance on Pro+. ' + 'OFF by default, and blocked on TWO published legal artifacts ' + '(AGL-1909), neither of which is a repo file — both are live besigner ' + 'pages, so publication is what satisfies them: (1) the privacy-policy ' + 'disclosure for stored Q&A, because the data loop records every ' + 'exchange org-scoped under orgs/{orgId}/assistExchanges; and (2) the ' + 'Anthropic row on /legal/subprocessors, which was deliberately ' + 'REMOVED on 2026-08-13 (subprocessorsV2a-20260813) on the premise ' + 'that no production key existed — so the page is not merely ' + 'incomplete without it, it is affirmatively wrong. NOTE the real ' + 'trigger is ANTHROPIC_API_KEY, not this flag: /api/ai/assist (the ' + 'besigner copy assistant, AGL-89/130/169) carries no release flag at ' + 'all and sends customer site content to Anthropic on the key plus a ' + 'Pro entitlement alone. Setting the key in production therefore makes ' + 'Anthropic a subprocessor whether or not this flag is ever flipped.',
+        defaultEnabled: false
+    },
+    // Ingress only, and with no staff preview on the server: a video a staff
+    // session uploads into a customer's library serves on that customer's pages
+    // like any other, so a grant goes to the org through its override.
+    // `apps/console/utils/server/video-uploads.ts` holds the gate.
+    {
+        key: 'release_video_uploads',
+        label: 'Video uploads',
+        description: 'New video in the media library, on every upload path (AGL-2830). ' + 'Off: refused with 403 video_uploads_paused, as DAM video delivery is ' + 'not yet metered or bounded per org (AGL-2810, AGL-2812). Images, ' + 'documents and stored videos are unaffected.',
+        defaultEnabled: false
+    },
+    // Delivery, not ingress: this flag decides whether a video already in the
+    // library is COPIED to the configured delivery provider and served from it
+    // through a short-lived signed redirect (AGL-2824). Per org, with no staff
+    // preview on the server — a copy is customer data at the provider, so a
+    // grant goes to the org through its override. Off, or with no provider
+    // configured, every video serves from this platform exactly as before.
+    // `media-delivery.ts` in `tenant-data-admin` holds the gate.
+    {
+        key: 'release_video_delivery',
+        label: 'Video delivery',
+        description: 'Serves library video from a configured delivery provider through ' + 'short-lived signed redirects, and copies each video to it (AGL-2824). ' + 'OFF by default: video serves from this platform as before. Also ' + "needs the provider's settings.",
+        defaultEnabled: false
+    },
+    // The generative doors share one runtime with Assist (AGL-2903) but not
+    // its flag: `release_assist` answers questions, this builds things, and
+    // the two are sold, metered and disclosed separately. The server-side
+    // gate lives in `aiGateLadder` (404 when off, staff preview).
+    // Labeled for what it switches — the generative doors — and not with the
+    // add-on's own name, which is sold and live whether or not the doors are
+    // released: the docs name the add-on, and a flag wearing the same words
+    // reads as documented when it is not.
+    {
+        key: 'release_ai_generative',
+        label: `${PLATFORM_BRAND_NAME} AI generation`,
+        description: 'Generative building and automation behind the AI add-on ' + '(AGL-2903): sections, pages and workflows written by a model from ' + 'a brief, on the shared Anthropic runtime. OFF by default and staff ' + 'preview only; every generative route answers 404 while it is off. ' + 'Turning it on sends customer briefs and site content to Anthropic ' + 'on the same ANTHROPIC_API_KEY and under the same subprocessor ' + 'disclosure as Assist (AGL-1909).',
+        defaultEnabled: false
+    }
+];
+export const RELEASE_FLAG_KEYS = RELEASE_FLAGS.map((definition)=>definition.key);
+export function isReleaseFlagKey(value) {
+    return RELEASE_FLAG_KEYS.includes(value);
+}
+export function getReleaseFlagDefinition(key) {
+    const definition = RELEASE_FLAGS.find((entry)=>entry.key === key);
+    if (!definition) throw new Error(`Unknown release flag: ${key}`);
+    return definition;
+}
+const clampPercent = (value)=>{
+    const percent = typeof value === 'number' && Number.isFinite(value) ? value : 0;
+    return Math.min(100, Math.max(0, Math.round(percent)));
+};
+/**
+ * Every plan a flag may target, cheapest first — `SELF_SERVE_PLANS` then
+ * `enterprise`, the same ladder `planGrantingFeature` walks and the same
+ * order the plan grid renders. Derived, never re-typed: pricing v3 inserted
+ * `scale` mid-ladder and added `agency`, and a second hand-written tier list
+ * here would have missed both.
+ */ export const RELEASE_FLAG_PLAN_LADDER = [
+    ...SELF_SERVE_PLANS,
+    'enterprise'
+];
+const isOrgPlan = (value)=>typeof value === 'string' && Object.prototype.hasOwnProperty.call(PLAN_LABELS, value);
+/**
+ * The tiers on the ladder at or above `plan` — what the console's "Pro and
+ * above" shortcut expands to before it is STORED as an explicit list.
+ *
+ * Deliberately a UI convenience and not a stored "minimum plan" mode: a
+ * stored threshold would silently re-aim every live flag the day a tier is
+ * inserted into the middle of the ladder (pricing v3 did exactly that with
+ * `scale`). An explicit list means the audience of a published flag only
+ * ever changes because a human changed it.
+ */ export function releaseFlagPlansAtOrAbove(plan) {
+    const index = RELEASE_FLAG_PLAN_LADDER.indexOf(plan);
+    return index < 0 ? [] : RELEASE_FLAG_PLAN_LADDER.slice(index);
+}
+/**
+ * Sanitises whatever is stored at `plans`, in ladder order.
+ *
+ * Returns `undefined` — not `[]` — for "no targeting declared", so the
+ * absence survives a round trip through the staff editor and cannot be
+ * written back as a list that means something else. Unknown tier names are
+ * dropped for the same reason `parseOrgReleaseFlagOverrides` drops unknown
+ * keys: a renamed or retired tier must never gate anything. A list that
+ * names ONLY unknown tiers collapses to `undefined` (every tier) rather than
+ * to an empty list, because a typo must inherit, never silently target.
+ */ export function parseReleaseFlagPlans(raw) {
+    if (!Array.isArray(raw)) return undefined;
+    const named = new Set(raw.filter(isOrgPlan));
+    if (named.size === 0) return undefined;
+    return RELEASE_FLAG_PLAN_LADDER.filter((plan)=>named.has(plan));
+}
+/**
+ * Parses a Remote Config parameter string into a `ReleaseFlagValue`.
+ * Tolerant by design — the template is hand-editable in the Firebase
+ * console, so plain "true"/"false" strings and malformed JSON must not
+ * crash gating: anything unreadable falls back to the registry default.
+ */ export function parseReleaseFlagValue(raw, fallbackEnabled) {
+    const text = raw == null ? void 0 : raw.trim();
+    if (!text) return {
+        enabled: fallbackEnabled
+    };
+    if (text === 'true') return {
+        enabled: true
+    };
+    if (text === 'false') return {
+        enabled: false
+    };
+    try {
+        const parsed = JSON.parse(text);
+        if (typeof parsed === 'boolean') return {
+            enabled: parsed
+        };
+        if (parsed && typeof parsed === 'object') {
+            const plans = parseReleaseFlagPlans(parsed.plans);
+            return _extends({
+                enabled: parsed.enabled === true,
+                rolloutPercent: clampPercent(parsed.rolloutPercent)
+            }, plans ? {
+                plans
+            } : {}, {
+                note: typeof parsed.note === 'string' ? parsed.note : undefined
+            });
+        }
+    } catch (unused) {
+    // fall through to the registry default
+    }
+    return {
+        enabled: fallbackEnabled
+    };
+}
+/**
+ * The longest parameter description Remote Config will publish (AGL-3048).
+ *
+ * One description past it refuses the WHOLE publish with
+ * `DESCRIPTION_EXCEEDS_MAXIMUM_SIZE`, which the staff flags route answered as
+ * a 500. Registry descriptions are written for the staff flags page, and
+ * several run far past the limit, so what the page shows and what a
+ * parameter carries cannot always be the same text.
+ *
+ * Counted in UTF-8 BYTES. Remote Config states the limit in characters
+ * without saying how it counts them, and a UTF-8 byte count is never smaller
+ * than the code-point or UTF-16 count, so text within 256 bytes is within the
+ * limit on every reading. The cost is a few characters of headroom on text
+ * with typographic punctuation.
+ */ export const REMOTE_CONFIG_DESCRIPTION_MAX_BYTES = 256;
+function utf8ByteLength(text) {
+    let bytes = 0;
+    for (const character of text){
+        var _character_codePointAt;
+        const codePoint = (_character_codePointAt = character.codePointAt(0)) != null ? _character_codePointAt : 0;
+        bytes += codePoint < 0x80 ? 1 : codePoint < 0x800 ? 2 : codePoint < 0x10000 ? 3 : 4;
+    }
+    return bytes;
+}
+/** Whether Remote Config accepts `text` as a parameter description. */ export function fitsRemoteConfigDescription(text) {
+    return utf8ByteLength(text) <= REMOTE_CONFIG_DESCRIPTION_MAX_BYTES;
+}
+const DESCRIPTION_ELLIPSIS = '…';
+/**
+ * `text` cut to a length Remote Config accepts, at a word boundary, with an
+ * ellipsis marking the cut. Text that already fits comes back unchanged.
+ *
+ * The cut takes whole code points, so a multi-byte character is never split.
+ * It backs up to the last space when it lands inside a word (only a single
+ * word longer than the whole budget is cut hard), and punctuation left
+ * dangling before the ellipsis is dropped.
+ */ export function clampRemoteConfigDescription(text) {
+    if (fitsRemoteConfigDescription(text)) return text;
+    const budget = REMOTE_CONFIG_DESCRIPTION_MAX_BYTES - utf8ByteLength(DESCRIPTION_ELLIPSIS);
+    let kept = '';
+    let bytes = 0;
+    for (const character of text){
+        const size = utf8ByteLength(character);
+        if (bytes + size > budget) break;
+        kept += character;
+        bytes += size;
+    }
+    const next = text.charAt(kept.length);
+    if (next && !/\s/.test(next)) {
+        const lastSpace = kept.search(/\s\S*$/);
+        if (lastSpace > 0) kept = kept.slice(0, lastSpace);
+    }
+    return `${kept.replace(/[\s.,;:(–—-]+$/, '')}${DESCRIPTION_ELLIPSIS}`;
+}
+/**
+ * The description to publish with a release flag's Remote Config parameter
+ * (AGL-3048). Always one Remote Config accepts:
+ *
+ * 1. The registry description, when it fits, so the flags page and the
+ *    parameter say the same thing.
+ * 2. Otherwise the LIVE parameter's description, when it has one that fits.
+ *    Remote Config has already accepted exactly that text, and someone chose
+ *    it for the Firebase console. The first 250 characters of a longer
+ *    paragraph would drop whatever the paragraph says last: for
+ *    `release_assist`, the `/legal/subprocessors` precondition that its
+ *    AGL-1909 suite wants in front of whoever reads the flag there. The full
+ *    registry text stays on the staff flags page either way.
+ * 3. Otherwise, as on a first publish with nothing live to keep, the
+ *    registry description clamped at a word boundary.
+ */ export function releaseFlagParameterDescription(registryDescription, liveDescription) {
+    if (fitsRemoteConfigDescription(registryDescription)) {
+        return registryDescription;
+    }
+    if (typeof liveDescription === 'string' && liveDescription.trim().length > 0 && fitsRemoteConfigDescription(liveDescription)) {
+        return liveDescription;
+    }
+    return clampRemoteConfigDescription(registryDescription);
+}
+/**
+ * FNV-1a 32-bit hash → 0–99 bucket. Deterministic so a subject keeps the
+ * same rollout verdict across sessions and surfaces, and seeded with the
+ * flag key so a subject doesn't land in the same bucket for every flag.
+ */ export function releaseFlagBucket(flagKey, subjectId) {
+    let hash = 0x811c9dc5;
+    const seed = `${flagKey}:${subjectId}`;
+    for(let index = 0; index < seed.length; index += 1){
+        hash ^= seed.charCodeAt(index);
+        hash = Math.imul(hash, 0x01000193);
+    }
+    return (hash >>> 0) % 100;
+}
+/**
+ * The gating verdict for one subject.
+ *
+ * `subjectId` is the ORG ID, or nothing. A rollout is a cohort of
+ * workspaces, so a whole workspace has to land on one side of the
+ * percentage: every surface that asks about an org must ask with the same
+ * string, or they answer differently about the same customer.
+ *
+ * This docstring used to sanction falling back to the uid, and the server
+ * gates fell back to a hostId. Since a hostId, a uid and an orgId hash to
+ * three different buckets, a mid-rollout flag could be on in the console
+ * and off on the published site for one workspace — stable per subject, so
+ * it never flickered, it just stayed wrong (AGL-1656).
+ *
+ * An empty subject only passes fully-enabled flags. That is the deliberate
+ * cost: a request with no resolvable org never joins a partial rollout,
+ * which is the conservative answer rather than a confidently wrong one.
+ */ export function isReleaseFlagOn(flagKey, value, subjectId, /**
+   * The subject org's plan, when the caller knows it (AGL-2486). Optional so
+   * every pre-existing call site compiles and answers unchanged: a flag that
+   * declares no tier targeting never reads this.
+   */ plan) {
+    if (!releaseFlagTargetsPlan(value, plan)) return false;
+    if (value.enabled) return true;
+    const percent = clampPercent(value.rolloutPercent);
+    if (percent <= 0 || !subjectId) return false;
+    if (percent >= 100) return true;
+    return releaseFlagBucket(flagKey, subjectId) < percent;
+}
+/**
+ * Does this flag's tier targeting admit `plan`? (AGL-2486)
+ *
+ * THE SEMANTICS, because an operator who cannot predict the audience will
+ * not stage a rollout at all:
+ *
+ *  - The tier list is a FILTER, applied before and independently of the
+ *    percentage. The percentage then picks a cohort WITHIN the admitted
+ *    tiers. "Pro and above at 50%" is therefore both "half of the Pro+
+ *    workspaces" and "the global 50% cohort, restricted to Pro+" — the two
+ *    readings name the same set, and they do so because
+ *    {@link releaseFlagBucket} hashes `flagKey:orgId` and NOTHING ELSE.
+ *  - Which is also why the bucket is stable. Adding, removing or reordering
+ *    tiers cannot reshuffle the bucket, so an org already inside a 50%
+ *    rollout keeps the feature when an unrelated tier joins the list. Had
+ *    the plan been mixed into the hash — the obvious way to write this — a
+ *    tier edit would have re-drawn the cohort under every customer already
+ *    in it, and a plan change would have re-rolled the dice for one.
+ *  - The filter binds the FULLY-ENABLED path too, not just the rollout.
+ *    "On, Enterprise + Agency" is how a launch to the top of the ladder is
+ *    expressed, and it is what was actually asked for. Untargeted flags are
+ *    unaffected: no list means every tier, so `enabled` still means everyone.
+ *  - An UNKNOWN plan fails a declared list. Same conservatism as a missing
+ *    subject on a percentage rollout: a caller that cannot say which
+ *    workspace it is asking about gets the safe answer rather than a
+ *    confidently wrong one. A per-org staff override still wins over all of
+ *    it — see {@link isReleaseFlagOnForOrg} — so a targeted flag can still be
+ *    handed to one org off-ladder.
+ */ export function releaseFlagTargetsPlan(value, plan) {
+    const plans = value.plans;
+    // `!plans` would be the idiom here, but `strictNullChecks` is off repo-wide
+    // and an empty array is truthy — both "absent" and "empty" have to be named
+    // for the every-tier reading to actually hold.
+    if (plans == null || plans.length === 0) return true;
+    if (!plan) return false;
+    return plans.includes(plan);
+}
+/**
+ * Sanitises whatever is actually stored at `org.releaseFlags`.
+ *
+ * Tolerant for the same reason `parseReleaseFlagValue` is: this map is
+ * hand-editable in the Firebase console and survives registry renames, so a
+ * retired flag key or a non-boolean must be dropped rather than allowed to
+ * gate anything. Unknown keys are discarded — a stale key can never grant a
+ * flag that no longer exists, and a typo silently inherits instead of
+ * silently forcing.
+ */ export function parseOrgReleaseFlagOverrides(raw) {
+    if (!raw || typeof raw !== 'object' || Array.isArray(raw)) return {};
+    const overrides = {};
+    for (const [key, value] of Object.entries(raw)){
+        if (typeof value === 'boolean' && isReleaseFlagKey(key)) {
+            overrides[key] = value;
+        }
+    }
+    return overrides;
+}
+/**
+ * The gating verdict with a per-org override applied on top of
+ * `isReleaseFlagOn`.
+ *
+ * The override is checked FIRST and short-circuits, so a forced-off flag
+ * stays off for an org even while the flag is globally enabled — the
+ * per-org kill switch is half the point, not just the per-org grant. Every
+ * release-flag gate resolves through here so the console, the tenant
+ * runtime and the API dispatchers cannot disagree about one org.
+ */ export function isReleaseFlagOnForOrg(flagKey, value, subjectId, overrides, /**
+   * The org's plan, for tier targeting (AGL-2486). Checked only AFTER the
+   * override: a staff grant is a decision about one named customer and
+   * outranks the tier filter exactly as it already outranks the rollout
+   * bucket. That ordering is what lets a Free org preview a
+   * Business-targeted flag without widening the flag for every Free org.
+   *
+   * REQUIRED, and `null` has to be typed out. It was optional for one
+   * release and that cost a silent revenue bug: `report-usage` held the org
+   * document, dropped the argument, and every `plans`-declaring flag read
+   * OFF — so the contacts overage went uninvoiced for exactly the orgs
+   * entitled to reach the feature, with nothing thrown and nothing logged.
+   * An unknown tier still refuses, which is the correct conservatism; what
+   * cannot be allowed is a caller MANUFACTURING an unknown out of a tier it
+   * already has in hand. Spelling `null` makes that a statement rather than
+   * an omission, and makes the next call site that forgets fail to compile
+   * instead of failing to bill. `getOrgReleaseFlagTargeting` returns the
+   * plan beside the overrides from ONE document read precisely so that
+   * passing it costs nothing.
+   */ plan) {
+    const override = overrides == null ? void 0 : overrides[flagKey];
+    if (typeof override === 'boolean') return override;
+    return isReleaseFlagOn(flagKey, value, subjectId, plan);
+}
+
+//# sourceMappingURL=release-flags.js.map

package/src/lib/app-utils/release-flags.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../../../../libs/aglyn/src/lib/app-utils/release-flags.ts"],"sourcesContent":["/**\n * @license\n * Copyright 2026 Aglyn LLC\n *\n * Licensed under the Apache License, Version 2.0 (the \"License\");\n * you may not use this file except in compliance with the License.\n * You may obtain a copy of the License at\n *\n *   http://www.apache.org/licenses/LICENSE-2.0\n *\n * Unless required by applicable law or agreed to in writing, software\n * distributed under the License is distributed on an \"AS IS\" BASIS,\n * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n * See the License for the specific language governing permissions and\n * limitations under the License.\n */\n\n/**\n * Release flags (AGL-227): platform-level \"is this feature launched\"\n * gating backed by Firebase Remote Config. A separate axis from plan\n * entitlements (`plan-entitlements.ts`) — entitlements ask whether the\n * tenant's PLAN includes a feature, release flags ask whether the feature\n * is released to the public at all (or partially, via percentage rollout).\n * Staff bypass release flags everywhere but see a flagged warning.\n */\n\n/** Remote Config parameter keys for release-gated features. */\nimport type { OrgPlan } from '../foundation'\nimport { PLAN_LABELS, SELF_SERVE_PLANS } from './plan-entitlements'\nimport { PLATFORM_BRAND_NAME } from './platform-brand'\n\nexport type ReleaseFlagKey =\n  | 'release_crm'\n  | 'release_outreach'\n  | 'release_bookings'\n  | 'release_events'\n  | 'release_data_store'\n  | 'release_workflows'\n  | 'release_redirects'\n  | 'release_commerce_v2'\n  | 'release_member_accounts'\n  | 'release_marketplace'\n  | 'release_marketing'\n  | 'release_email'\n  | 'release_inbox'\n  | 'release_logic'\n  | 'release_addon_store'\n  | 'release_native_checkout'\n  | 'release_edit_bar'\n  | 'release_assist'\n  | 'release_video_uploads'\n  | 'release_video_delivery'\n  | 'release_ai_generative'\n\nexport interface ReleaseFlagDefinition {\n  key: ReleaseFlagKey\n  label: string\n  description: string\n  /**\n   * Fallback verdict when Remote Config is unreachable (offline, blocked,\n   * first paint before activate). MUST match the seeded value in\n   * cloud/firebase-remoteconfig.template.json so environments without a\n   * published template behave like the template intends.\n   */\n  defaultEnabled: boolean\n  /** Host dashboard tab id (host-nav-tabs.ts) this flag hides, if any. */\n  navTabId?: string\n}\n\n/**\n * The registry: one entry per gated feature. Adding a flag = add it here,\n * seed it in the Remote Config template, and (optionally) wrap the page in\n * `<FeatureGate>` — the staff admin editor and nav filtering pick it up\n * from this list.\n */\nexport const RELEASE_FLAGS: readonly ReleaseFlagDefinition[] = [\n  {\n    key: 'release_crm',\n    label: 'CRM',\n    description:\n      'The CRM: contacts, leads, companies, deals, tasks, reports and fields.',\n    defaultEnabled: true,\n    navTabId: 'nav-tab-contacts',\n  },\n  // Sequences (AGL-2974): the plugin's kill switch as well as its launch\n  // gate, like every first-party plugin's flag since AGL-422 — off, it is\n  // subtracted from the console loader and the API dispatcher for everyone\n  // but staff. OFF by default, because nothing behind it sends mail yet and\n  // no plan carries the `outreach` entitlement it also needs. The KEY stays\n  // `release_outreach`: it is persisted in Remote Config (AGL-3199).\n  {\n    key: 'release_outreach',\n    label: 'Sequences',\n    description:\n      'One-to-one, multi-step email sequences sent from a rep’s own ' +\n      'connected mailbox and logged in the CRM (AGL-2974). OFF by default ' +\n      'and staff preview only. An organization also needs the `outreach` ' +\n      'entitlement, which no plan carries, so a customer reaches it only ' +\n      'through a per-org entitlement override.',\n    defaultEnabled: false,\n    navTabId: 'nav-tab-org-outreach',\n  },\n  {\n    key: 'release_bookings',\n    label: 'Bookings',\n    description: 'Bookings & scheduling for host sites.',\n    defaultEnabled: true,\n    navTabId: 'nav-tab-bookings',\n  },\n  {\n    key: 'release_events',\n    label: 'Events',\n    description: 'Event calendar management (AGL-145 add-on surface).',\n    defaultEnabled: true,\n    navTabId: 'nav-tab-events',\n  },\n  {\n    key: 'release_data_store',\n    label: 'Data store',\n    description: 'Datasets, models and dynamic data bindings.',\n    defaultEnabled: true,\n    navTabId: 'nav-tab-data',\n  },\n  {\n    key: 'release_workflows',\n    label: 'Automation',\n    description: 'Workflows, actions, webhooks and their run history.',\n    defaultEnabled: true,\n    navTabId: 'nav-tab-workflows',\n  },\n  {\n    key: 'release_redirects',\n    label: 'Redirects',\n    description: 'Redirect manager with usage analytics.',\n    defaultEnabled: true,\n    navTabId: 'nav-tab-redirects',\n  },\n  {\n    key: 'release_commerce_v2',\n    label: 'Commerce v2',\n    description:\n      'Full ecommerce wave: catalog/variants, cart + checkout, digital ' +\n      'goods, reservations, POS, and the repriced commerce tiers ' +\n      '(AGL-276..331).',\n    defaultEnabled: true,\n  },\n  {\n    key: 'release_member_accounts',\n    label: 'User Accounts',\n    description:\n      'Visitor accounts on published sites: the /signin, /signup and ' +\n      '/recover pages and the Members blocks (AGL-2486). Platform-wide ' +\n      'kill switch only — whether a given SITE serves those pages is the ' +\n      'per-site User Accounts toggle, which is off until a site opts in.',\n    defaultEnabled: true,\n  },\n  {\n    key: 'release_marketplace',\n    label: 'Marketplace',\n    description: 'Marketplace browsing, publishing and plugin installs.',\n    defaultEnabled: true,\n    // AGL-1654: was 'nav-tab-marketplace', which matched no nav item, so\n    // `gateNavTabItems` never hid the tab. The org Marketplace tab is a\n    // console constant rather than a plugin nav item, so the id has to be\n    // kept in step with `org-nav-tabs.ts` by hand; the spec\n    // `release-flag-nav-tab-ids.spec.ts` is what holds it there.\n    //\n    // The second half of that comment — \"the page behind it carries no\n    // `<FeatureGate>`\" — was still true until AGL-2019 and is no longer.\n    // Flipping this flag off used to subtract the marketplace plugin from\n    // the loader and both API dispatchers while the page went on rendering\n    // in full, so the OFF state was itself broken and \"just turn the flag\n    // off\" was not an available answer for an operator who does not want a\n    // marketplace. The page is gated now, so off means off.\n    navTabId: 'nav-tab-org-marketplace',\n  },\n  // AGL-422: every first-party plugin is release-flagged — the flag now\n  // feeds the plugin LOADER (console, published sites, API dispatch), not\n  // just nav visibility, so staff can kill-switch a whole plugin platform-\n  // wide from the Feature Flags page.\n  {\n    key: 'release_marketing',\n    label: 'Marketing',\n    description: 'Overlays, campaigns at-a-glance, and A/B experiments.',\n    defaultEnabled: true,\n    navTabId: 'nav-tab-marketing',\n  },\n  {\n    key: 'release_email',\n    label: 'Email',\n    description: 'Designed emails, campaigns, and audience sending.',\n    defaultEnabled: true,\n  },\n  {\n    key: 'release_inbox',\n    label: 'Inbox',\n    description: 'Form submissions, site members, and the lead inbox.',\n    defaultEnabled: true,\n    navTabId: 'nav-tab-inbox',\n  },\n  {\n    key: 'release_logic',\n    label: 'Logic',\n    description: 'Variables, no-code functions, and reference health.',\n    defaultEnabled: true,\n    navTabId: 'nav-tab-logic',\n  },\n  {\n    key: 'release_addon_store',\n    label: 'Add-on store',\n    description:\n      'Self-serve add-on purchases on the Billing page: seats, datasets, ' +\n      'extra sites, POS registers, Event Calendar (AGL-524..531).',\n    defaultEnabled: true,\n  },\n  {\n    key: 'release_native_checkout',\n    label: 'In-page checkout',\n    description:\n      'Pay without leaving the page, instead of a redirect to ' +\n      'checkout.stripe.com. TWO surfaces: the console plan checkout uses ' +\n      'embedded Checkout (AGL-1132), and a merchant storefront uses the ' +\n      'Payment Element on the merchant\\u2019s own domain (AGL-1944) \\u2014 ' +\n      'which is the half that costs conversions, since leaving the store ' +\n      'mid-purchase is where carts get abandoned. Both keep the webhook as ' +\n      'the only thing that fulfils. OFF by default: the redirect is the ' +\n      'proven path, and neither surface can be verified without putting a ' +\n      'real card through it. Also gated on a publishable key being set, ' +\n      'per surface \\u2014 so flipping this alone degrades to the redirect ' +\n      'rather than to a dead button.',\n    defaultEnabled: false,\n  },\n  // Released to every site 2026-09-16 (AGL-3041). Still the whole surface's\n  // kill switch, globally or for one org by override: off, the tenant slot\n  // renders nothing, both token mints refuse, and `/api/edit-context` turns\n  // away every token already issued.\n  {\n    key: 'release_edit_bar',\n    label: 'Site admin bar',\n    description:\n      'Admin bar on published sites: a signed-in editor jumps from a live ' +\n      'page into the besigner for the screen serving it. Released ' +\n      '2026-09-16 (AGL-3041) for every site; turning it off hides the bar ' +\n      'and revokes every outstanding edit token at the verify site.',\n    defaultEnabled: true,\n  },\n  {\n    key: 'release_assist',\n    label: `${PLATFORM_BRAND_NAME} Assist`,\n    description:\n      'The in-console AI chat helper on every page (AGL-1860): docs-' +\n      'grounded answers with deep links, page-context guidance on Pro+. ' +\n      'OFF by default, and blocked on TWO published legal artifacts ' +\n      '(AGL-1909), neither of which is a repo file — both are live besigner ' +\n      'pages, so publication is what satisfies them: (1) the privacy-policy ' +\n      'disclosure for stored Q&A, because the data loop records every ' +\n      'exchange org-scoped under orgs/{orgId}/assistExchanges; and (2) the ' +\n      'Anthropic row on /legal/subprocessors, which was deliberately ' +\n      'REMOVED on 2026-08-13 (subprocessorsV2a-20260813) on the premise ' +\n      'that no production key existed — so the page is not merely ' +\n      'incomplete without it, it is affirmatively wrong. NOTE the real ' +\n      'trigger is ANTHROPIC_API_KEY, not this flag: /api/ai/assist (the ' +\n      'besigner copy assistant, AGL-89/130/169) carries no release flag at ' +\n      'all and sends customer site content to Anthropic on the key plus a ' +\n      'Pro entitlement alone. Setting the key in production therefore makes ' +\n      'Anthropic a subprocessor whether or not this flag is ever flipped.',\n    defaultEnabled: false,\n  },\n  // Ingress only, and with no staff preview on the server: a video a staff\n  // session uploads into a customer's library serves on that customer's pages\n  // like any other, so a grant goes to the org through its override.\n  // `apps/console/utils/server/video-uploads.ts` holds the gate.\n  {\n    key: 'release_video_uploads',\n    label: 'Video uploads',\n    description:\n      'New video in the media library, on every upload path (AGL-2830). ' +\n      'Off: refused with 403 video_uploads_paused, as DAM video delivery is ' +\n      'not yet metered or bounded per org (AGL-2810, AGL-2812). Images, ' +\n      'documents and stored videos are unaffected.',\n    defaultEnabled: false,\n  },\n  // Delivery, not ingress: this flag decides whether a video already in the\n  // library is COPIED to the configured delivery provider and served from it\n  // through a short-lived signed redirect (AGL-2824). Per org, with no staff\n  // preview on the server — a copy is customer data at the provider, so a\n  // grant goes to the org through its override. Off, or with no provider\n  // configured, every video serves from this platform exactly as before.\n  // `media-delivery.ts` in `tenant-data-admin` holds the gate.\n  {\n    key: 'release_video_delivery',\n    label: 'Video delivery',\n    description:\n      'Serves library video from a configured delivery provider through ' +\n      'short-lived signed redirects, and copies each video to it (AGL-2824). ' +\n      'OFF by default: video serves from this platform as before. Also ' +\n      \"needs the provider's settings.\",\n    defaultEnabled: false,\n  },\n  // The generative doors share one runtime with Assist (AGL-2903) but not\n  // its flag: `release_assist` answers questions, this builds things, and\n  // the two are sold, metered and disclosed separately. The server-side\n  // gate lives in `aiGateLadder` (404 when off, staff preview).\n  // Labeled for what it switches — the generative doors — and not with the\n  // add-on's own name, which is sold and live whether or not the doors are\n  // released: the docs name the add-on, and a flag wearing the same words\n  // reads as documented when it is not.\n  {\n    key: 'release_ai_generative',\n    label: `${PLATFORM_BRAND_NAME} AI generation`,\n    description:\n      'Generative building and automation behind the AI add-on ' +\n      '(AGL-2903): sections, pages and workflows written by a model from ' +\n      'a brief, on the shared Anthropic runtime. OFF by default and staff ' +\n      'preview only; every generative route answers 404 while it is off. ' +\n      'Turning it on sends customer briefs and site content to Anthropic ' +\n      'on the same ANTHROPIC_API_KEY and under the same subprocessor ' +\n      'disclosure as Assist (AGL-1909).',\n    defaultEnabled: false,\n  },\n]\n\nexport const RELEASE_FLAG_KEYS = RELEASE_FLAGS.map(\n  (definition) => definition.key,\n) as readonly ReleaseFlagKey[]\n\nexport function isReleaseFlagKey(value: string): value is ReleaseFlagKey {\n  return (RELEASE_FLAG_KEYS as readonly string[]).includes(value)\n}\n\nexport function getReleaseFlagDefinition(\n  key: ReleaseFlagKey,\n): ReleaseFlagDefinition {\n  const definition = RELEASE_FLAGS.find((entry) => entry.key === key)\n  if (!definition) throw new Error(`Unknown release flag: ${key}`)\n  return definition\n}\n\n/**\n * The JSON payload stored in each Remote Config parameter. `enabled: true`\n * turns the feature on for everyone; `enabled: false` with a positive\n * `rolloutPercent` enables it for that percentage of subjects (stable\n * per-tenant bucketing, GrowthBook-style); `plans` narrows either of those\n * to a set of tiers (AGL-2486).\n */\nexport interface ReleaseFlagValue {\n  enabled: boolean\n  /** 0–100; only consulted while `enabled` is false. */\n  rolloutPercent?: number\n  /**\n   * Plan/tier targeting (AGL-2486). The tiers this flag is being rolled out\n   * to, or ABSENT for \"every tier\".\n   *\n   * ABSENT AND EMPTY BOTH MEAN EVERY TIER, and that is load-bearing: every\n   * flag stored before this field existed parses to `undefined` here, and an\n   * operator who unticks every box has plainly not asked for a flag that\n   * reaches nobody. Reading an empty list as \"no tiers\" would dark-launch\n   * nothing while the console still said the flag was on — the inverted\n   * reading of this field is the whole hazard, so it is closed in the parser\n   * rather than left to each call site.\n   */\n  plans?: OrgPlan[]\n  /** Free-form staff note (\"waiting on AGL-199\", owner, etc.). */\n  note?: string\n}\n\nconst clampPercent = (value: unknown): number => {\n  const percent = typeof value === 'number' && Number.isFinite(value) ? value : 0\n  return Math.min(100, Math.max(0, Math.round(percent)))\n}\n\n/**\n * Every plan a flag may target, cheapest first — `SELF_SERVE_PLANS` then\n * `enterprise`, the same ladder `planGrantingFeature` walks and the same\n * order the plan grid renders. Derived, never re-typed: pricing v3 inserted\n * `scale` mid-ladder and added `agency`, and a second hand-written tier list\n * here would have missed both.\n */\nexport const RELEASE_FLAG_PLAN_LADDER: readonly OrgPlan[] = [\n  ...SELF_SERVE_PLANS,\n  'enterprise' as OrgPlan,\n]\n\nconst isOrgPlan = (value: unknown): value is OrgPlan =>\n  typeof value === 'string' &&\n  Object.prototype.hasOwnProperty.call(PLAN_LABELS, value)\n\n/**\n * The tiers on the ladder at or above `plan` — what the console's \"Pro and\n * above\" shortcut expands to before it is STORED as an explicit list.\n *\n * Deliberately a UI convenience and not a stored \"minimum plan\" mode: a\n * stored threshold would silently re-aim every live flag the day a tier is\n * inserted into the middle of the ladder (pricing v3 did exactly that with\n * `scale`). An explicit list means the audience of a published flag only\n * ever changes because a human changed it.\n */\nexport function releaseFlagPlansAtOrAbove(plan: OrgPlan): OrgPlan[] {\n  const index = RELEASE_FLAG_PLAN_LADDER.indexOf(plan)\n  return index < 0 ? [] : RELEASE_FLAG_PLAN_LADDER.slice(index)\n}\n\n/**\n * Sanitises whatever is stored at `plans`, in ladder order.\n *\n * Returns `undefined` — not `[]` — for \"no targeting declared\", so the\n * absence survives a round trip through the staff editor and cannot be\n * written back as a list that means something else. Unknown tier names are\n * dropped for the same reason `parseOrgReleaseFlagOverrides` drops unknown\n * keys: a renamed or retired tier must never gate anything. A list that\n * names ONLY unknown tiers collapses to `undefined` (every tier) rather than\n * to an empty list, because a typo must inherit, never silently target.\n */\nexport function parseReleaseFlagPlans(raw: unknown): OrgPlan[] | undefined {\n  if (!Array.isArray(raw)) return undefined\n  const named = new Set(raw.filter(isOrgPlan))\n  if (named.size === 0) return undefined\n  return RELEASE_FLAG_PLAN_LADDER.filter((plan) => named.has(plan))\n}\n\n/**\n * Parses a Remote Config parameter string into a `ReleaseFlagValue`.\n * Tolerant by design — the template is hand-editable in the Firebase\n * console, so plain \"true\"/\"false\" strings and malformed JSON must not\n * crash gating: anything unreadable falls back to the registry default.\n */\nexport function parseReleaseFlagValue(\n  raw: string | null | undefined,\n  fallbackEnabled: boolean,\n): ReleaseFlagValue {\n  const text = raw?.trim()\n  if (!text) return { enabled: fallbackEnabled }\n  if (text === 'true') return { enabled: true }\n  if (text === 'false') return { enabled: false }\n  try {\n    const parsed = JSON.parse(text)\n    if (typeof parsed === 'boolean') return { enabled: parsed }\n    if (parsed && typeof parsed === 'object') {\n      const plans = parseReleaseFlagPlans(parsed.plans)\n      return {\n        enabled: parsed.enabled === true,\n        rolloutPercent: clampPercent(parsed.rolloutPercent),\n        // Spread, so a flag stored before AGL-2486 has NO `plans` key at all\n        // rather than an explicit `undefined`. `JSON.stringify` drops both,\n        // but the two are not the same to `'plans' in value`, which is what\n        // the staff PUT uses to tell \"the operator cleared the targeting\"\n        // apart from \"this client never sent the field\".\n        ...(plans ? { plans } : {}),\n        note: typeof parsed.note === 'string' ? parsed.note : undefined,\n      }\n    }\n  } catch {\n    // fall through to the registry default\n  }\n  return { enabled: fallbackEnabled }\n}\n\n/**\n * The longest parameter description Remote Config will publish (AGL-3048).\n *\n * One description past it refuses the WHOLE publish with\n * `DESCRIPTION_EXCEEDS_MAXIMUM_SIZE`, which the staff flags route answered as\n * a 500. Registry descriptions are written for the staff flags page, and\n * several run far past the limit, so what the page shows and what a\n * parameter carries cannot always be the same text.\n *\n * Counted in UTF-8 BYTES. Remote Config states the limit in characters\n * without saying how it counts them, and a UTF-8 byte count is never smaller\n * than the code-point or UTF-16 count, so text within 256 bytes is within the\n * limit on every reading. The cost is a few characters of headroom on text\n * with typographic punctuation.\n */\nexport const REMOTE_CONFIG_DESCRIPTION_MAX_BYTES = 256\n\nfunction utf8ByteLength(text: string): number {\n  let bytes = 0\n  for (const character of text) {\n    const codePoint = character.codePointAt(0) ?? 0\n    bytes +=\n      codePoint < 0x80 ? 1 : codePoint < 0x800 ? 2 : codePoint < 0x10000 ? 3 : 4\n  }\n  return bytes\n}\n\n/** Whether Remote Config accepts `text` as a parameter description. */\nexport function fitsRemoteConfigDescription(text: string): boolean {\n  return utf8ByteLength(text) <= REMOTE_CONFIG_DESCRIPTION_MAX_BYTES\n}\n\nconst DESCRIPTION_ELLIPSIS = '…'\n\n/**\n * `text` cut to a length Remote Config accepts, at a word boundary, with an\n * ellipsis marking the cut. Text that already fits comes back unchanged.\n *\n * The cut takes whole code points, so a multi-byte character is never split.\n * It backs up to the last space when it lands inside a word (only a single\n * word longer than the whole budget is cut hard), and punctuation left\n * dangling before the ellipsis is dropped.\n */\nexport function clampRemoteConfigDescription(text: string): string {\n  if (fitsRemoteConfigDescription(text)) return text\n  const budget =\n    REMOTE_CONFIG_DESCRIPTION_MAX_BYTES - utf8ByteLength(DESCRIPTION_ELLIPSIS)\n  let kept = ''\n  let bytes = 0\n  for (const character of text) {\n    const size = utf8ByteLength(character)\n    if (bytes + size > budget) break\n    kept += character\n    bytes += size\n  }\n  const next = text.charAt(kept.length)\n  if (next && !/\\s/.test(next)) {\n    const lastSpace = kept.search(/\\s\\S*$/)\n    if (lastSpace > 0) kept = kept.slice(0, lastSpace)\n  }\n  return `${kept.replace(/[\\s.,;:(–—-]+$/, '')}${DESCRIPTION_ELLIPSIS}`\n}\n\n/**\n * The description to publish with a release flag's Remote Config parameter\n * (AGL-3048). Always one Remote Config accepts:\n *\n * 1. The registry description, when it fits, so the flags page and the\n *    parameter say the same thing.\n * 2. Otherwise the LIVE parameter's description, when it has one that fits.\n *    Remote Config has already accepted exactly that text, and someone chose\n *    it for the Firebase console. The first 250 characters of a longer\n *    paragraph would drop whatever the paragraph says last: for\n *    `release_assist`, the `/legal/subprocessors` precondition that its\n *    AGL-1909 suite wants in front of whoever reads the flag there. The full\n *    registry text stays on the staff flags page either way.\n * 3. Otherwise, as on a first publish with nothing live to keep, the\n *    registry description clamped at a word boundary.\n */\nexport function releaseFlagParameterDescription(\n  registryDescription: string,\n  liveDescription: string | null | undefined,\n): string {\n  if (fitsRemoteConfigDescription(registryDescription)) {\n    return registryDescription\n  }\n  if (\n    typeof liveDescription === 'string' &&\n    liveDescription.trim().length > 0 &&\n    fitsRemoteConfigDescription(liveDescription)\n  ) {\n    return liveDescription\n  }\n  return clampRemoteConfigDescription(registryDescription)\n}\n\n/**\n * FNV-1a 32-bit hash → 0–99 bucket. Deterministic so a subject keeps the\n * same rollout verdict across sessions and surfaces, and seeded with the\n * flag key so a subject doesn't land in the same bucket for every flag.\n */\nexport function releaseFlagBucket(flagKey: string, subjectId: string): number {\n  let hash = 0x811c9dc5\n  const seed = `${flagKey}:${subjectId}`\n  for (let index = 0; index < seed.length; index += 1) {\n    hash ^= seed.charCodeAt(index)\n    hash = Math.imul(hash, 0x01000193)\n  }\n  return (hash >>> 0) % 100\n}\n\n/**\n * The gating verdict for one subject.\n *\n * `subjectId` is the ORG ID, or nothing. A rollout is a cohort of\n * workspaces, so a whole workspace has to land on one side of the\n * percentage: every surface that asks about an org must ask with the same\n * string, or they answer differently about the same customer.\n *\n * This docstring used to sanction falling back to the uid, and the server\n * gates fell back to a hostId. Since a hostId, a uid and an orgId hash to\n * three different buckets, a mid-rollout flag could be on in the console\n * and off on the published site for one workspace — stable per subject, so\n * it never flickered, it just stayed wrong (AGL-1656).\n *\n * An empty subject only passes fully-enabled flags. That is the deliberate\n * cost: a request with no resolvable org never joins a partial rollout,\n * which is the conservative answer rather than a confidently wrong one.\n */\nexport function isReleaseFlagOn(\n  flagKey: ReleaseFlagKey,\n  value: ReleaseFlagValue,\n  subjectId: string | null | undefined,\n  /**\n   * The subject org's plan, when the caller knows it (AGL-2486). Optional so\n   * every pre-existing call site compiles and answers unchanged: a flag that\n   * declares no tier targeting never reads this.\n   */\n  plan?: OrgPlan | null,\n): boolean {\n  if (!releaseFlagTargetsPlan(value, plan)) return false\n  if (value.enabled) return true\n  const percent = clampPercent(value.rolloutPercent)\n  if (percent <= 0 || !subjectId) return false\n  if (percent >= 100) return true\n  return releaseFlagBucket(flagKey, subjectId) < percent\n}\n\n/**\n * Does this flag's tier targeting admit `plan`? (AGL-2486)\n *\n * THE SEMANTICS, because an operator who cannot predict the audience will\n * not stage a rollout at all:\n *\n *  - The tier list is a FILTER, applied before and independently of the\n *    percentage. The percentage then picks a cohort WITHIN the admitted\n *    tiers. \"Pro and above at 50%\" is therefore both \"half of the Pro+\n *    workspaces\" and \"the global 50% cohort, restricted to Pro+\" — the two\n *    readings name the same set, and they do so because\n *    {@link releaseFlagBucket} hashes `flagKey:orgId` and NOTHING ELSE.\n *  - Which is also why the bucket is stable. Adding, removing or reordering\n *    tiers cannot reshuffle the bucket, so an org already inside a 50%\n *    rollout keeps the feature when an unrelated tier joins the list. Had\n *    the plan been mixed into the hash — the obvious way to write this — a\n *    tier edit would have re-drawn the cohort under every customer already\n *    in it, and a plan change would have re-rolled the dice for one.\n *  - The filter binds the FULLY-ENABLED path too, not just the rollout.\n *    \"On, Enterprise + Agency\" is how a launch to the top of the ladder is\n *    expressed, and it is what was actually asked for. Untargeted flags are\n *    unaffected: no list means every tier, so `enabled` still means everyone.\n *  - An UNKNOWN plan fails a declared list. Same conservatism as a missing\n *    subject on a percentage rollout: a caller that cannot say which\n *    workspace it is asking about gets the safe answer rather than a\n *    confidently wrong one. A per-org staff override still wins over all of\n *    it — see {@link isReleaseFlagOnForOrg} — so a targeted flag can still be\n *    handed to one org off-ladder.\n */\nexport function releaseFlagTargetsPlan(\n  value: ReleaseFlagValue,\n  plan: OrgPlan | null | undefined,\n): boolean {\n  const plans = value.plans\n  // `!plans` would be the idiom here, but `strictNullChecks` is off repo-wide\n  // and an empty array is truthy — both \"absent\" and \"empty\" have to be named\n  // for the every-tier reading to actually hold.\n  if (plans == null || plans.length === 0) return true\n  if (!plan) return false\n  return plans.includes(plan)\n}\n\n/**\n * Per-org release-flag overrides (AGL-1635), stored on the org doc at\n * `releaseFlags`. A present key is a staff DECISION about one organization\n * and wins over both the Remote Config value and the rollout bucket; an\n * absent key inherits.\n *\n * A separate field from `entitlements.features` on purpose: those ask\n * whether the org's PLAN includes a feature, these ask whether a\n * not-yet-released feature is switched on for this one customer. Folding\n * them together would make \"granted by the deal\" and \"previewing an\n * unreleased build\" indistinguishable at the point a support question is\n * asked.\n *\n * Why the org doc and not a Remote Config condition: RC conditions are\n * template-global and would need one published condition per org, with a\n * template publish (a manual, separate deploy) for every grant.\n */\nexport type OrgReleaseFlagOverrides = Partial<Record<ReleaseFlagKey, boolean>>\n\n/**\n * Sanitises whatever is actually stored at `org.releaseFlags`.\n *\n * Tolerant for the same reason `parseReleaseFlagValue` is: this map is\n * hand-editable in the Firebase console and survives registry renames, so a\n * retired flag key or a non-boolean must be dropped rather than allowed to\n * gate anything. Unknown keys are discarded — a stale key can never grant a\n * flag that no longer exists, and a typo silently inherits instead of\n * silently forcing.\n */\nexport function parseOrgReleaseFlagOverrides(\n  raw: unknown,\n): OrgReleaseFlagOverrides {\n  if (!raw || typeof raw !== 'object' || Array.isArray(raw)) return {}\n  const overrides: OrgReleaseFlagOverrides = {}\n  for (const [key, value] of Object.entries(raw as Record<string, unknown>)) {\n    if (typeof value === 'boolean' && isReleaseFlagKey(key)) {\n      overrides[key] = value\n    }\n  }\n  return overrides\n}\n\n/**\n * The gating verdict with a per-org override applied on top of\n * `isReleaseFlagOn`.\n *\n * The override is checked FIRST and short-circuits, so a forced-off flag\n * stays off for an org even while the flag is globally enabled — the\n * per-org kill switch is half the point, not just the per-org grant. Every\n * release-flag gate resolves through here so the console, the tenant\n * runtime and the API dispatchers cannot disagree about one org.\n */\nexport function isReleaseFlagOnForOrg(\n  flagKey: ReleaseFlagKey,\n  value: ReleaseFlagValue,\n  subjectId: string | null | undefined,\n  overrides: OrgReleaseFlagOverrides | null | undefined,\n  /**\n   * The org's plan, for tier targeting (AGL-2486). Checked only AFTER the\n   * override: a staff grant is a decision about one named customer and\n   * outranks the tier filter exactly as it already outranks the rollout\n   * bucket. That ordering is what lets a Free org preview a\n   * Business-targeted flag without widening the flag for every Free org.\n   *\n   * REQUIRED, and `null` has to be typed out. It was optional for one\n   * release and that cost a silent revenue bug: `report-usage` held the org\n   * document, dropped the argument, and every `plans`-declaring flag read\n   * OFF — so the contacts overage went uninvoiced for exactly the orgs\n   * entitled to reach the feature, with nothing thrown and nothing logged.\n   * An unknown tier still refuses, which is the correct conservatism; what\n   * cannot be allowed is a caller MANUFACTURING an unknown out of a tier it\n   * already has in hand. Spelling `null` makes that a statement rather than\n   * an omission, and makes the next call site that forgets fail to compile\n   * instead of failing to bill. `getOrgReleaseFlagTargeting` returns the\n   * plan beside the overrides from ONE document read precisely so that\n   * passing it costs nothing.\n   */\n  plan: OrgPlan | null,\n): boolean {\n  const override = overrides?.[flagKey]\n  if (typeof override === 'boolean') return override\n  return isReleaseFlagOn(flagKey, value, subjectId, plan)\n}\n"],"names":["PLAN_LABELS","SELF_SERVE_PLANS","PLATFORM_BRAND_NAME","RELEASE_FLAGS","key","label","description","defaultEnabled","navTabId","RELEASE_FLAG_KEYS","map","definition","isReleaseFlagKey","value","includes","getReleaseFlagDefinition","find","entry","Error","clampPercent","percent","Number","isFinite","Math","min","max","round","RELEASE_FLAG_PLAN_LADDER","isOrgPlan","Object","prototype","hasOwnProperty","call","releaseFlagPlansAtOrAbove","plan","index","indexOf","slice","parseReleaseFlagPlans","raw","Array","isArray","undefined","named","Set","filter","size","has","parseReleaseFlagValue","fallbackEnabled","text","trim","enabled","parsed","JSON","parse","plans","rolloutPercent","note","REMOTE_CONFIG_DESCRIPTION_MAX_BYTES","utf8ByteLength","bytes","character","codePoint","codePointAt","fitsRemoteConfigDescription","DESCRIPTION_ELLIPSIS","clampRemoteConfigDescription","budget","kept","next","charAt","length","test","lastSpace","search","replace","releaseFlagParameterDescription","registryDescription","liveDescription","releaseFlagBucket","flagKey","subjectId","hash","seed","charCodeAt","imul","isReleaseFlagOn","releaseFlagTargetsPlan","parseOrgReleaseFlagOverrides","overrides","entries","isReleaseFlagOnForOrg","override"],"mappings":"AAAA;;;;;;;;;;;;;;;CAeC,GAED;;;;;;;CAOC,GAED,6DAA6D;AAE7D,SAASA,WAAW,EAAEC,gBAAgB,QAAQ,yBAAqB;AACnE,SAASC,mBAAmB,QAAQ,sBAAkB;AAwCtD;;;;;CAKC,GACD,OAAO,MAAMC,gBAAkD;IAC7D;QACEC,KAAK;QACLC,OAAO;QACPC,aACE;QACFC,gBAAgB;QAChBC,UAAU;IACZ;IACA,uEAAuE;IACvE,wEAAwE;IACxE,yEAAyE;IACzE,0EAA0E;IAC1E,0EAA0E;IAC1E,mEAAmE;IACnE;QACEJ,KAAK;QACLC,OAAO;QACPC,aACE,kEACA,wEACA,uEACA,uEACA;QACFC,gBAAgB;QAChBC,UAAU;IACZ;IACA;QACEJ,KAAK;QACLC,OAAO;QACPC,aAAa;QACbC,gBAAgB;QAChBC,UAAU;IACZ;IACA;QACEJ,KAAK;QACLC,OAAO;QACPC,aAAa;QACbC,gBAAgB;QAChBC,UAAU;IACZ;IACA;QACEJ,KAAK;QACLC,OAAO;QACPC,aAAa;QACbC,gBAAgB;QAChBC,UAAU;IACZ;IACA;QACEJ,KAAK;QACLC,OAAO;QACPC,aAAa;QACbC,gBAAgB;QAChBC,UAAU;IACZ;IACA;QACEJ,KAAK;QACLC,OAAO;QACPC,aAAa;QACbC,gBAAgB;QAChBC,UAAU;IACZ;IACA;QACEJ,KAAK;QACLC,OAAO;QACPC,aACE,qEACA,+DACA;QACFC,gBAAgB;IAClB;IACA;QACEH,KAAK;QACLC,OAAO;QACPC,aACE,mEACA,qEACA,uEACA;QACFC,gBAAgB;IAClB;IACA;QACEH,KAAK;QACLC,OAAO;QACPC,aAAa;QACbC,gBAAgB;QAChB,qEAAqE;QACrE,oEAAoE;QACpE,sEAAsE;QACtE,wDAAwD;QACxD,6DAA6D;QAC7D,EAAE;QACF,mEAAmE;QACnE,qEAAqE;QACrE,sEAAsE;QACtE,uEAAuE;QACvE,sEAAsE;QACtE,uEAAuE;QACvE,wDAAwD;QACxDC,UAAU;IACZ;IACA,sEAAsE;IACtE,wEAAwE;IACxE,yEAAyE;IACzE,oCAAoC;IACpC;QACEJ,KAAK;QACLC,OAAO;QACPC,aAAa;QACbC,gBAAgB;QAChBC,UAAU;IACZ;IACA;QACEJ,KAAK;QACLC,OAAO;QACPC,aAAa;QACbC,gBAAgB;IAClB;IACA;QACEH,KAAK;QACLC,OAAO;QACPC,aAAa;QACbC,gBAAgB;QAChBC,UAAU;IACZ;IACA;QACEJ,KAAK;QACLC,OAAO;QACPC,aAAa;QACbC,gBAAgB;QAChBC,UAAU;IACZ;IACA;QACEJ,KAAK;QACLC,OAAO;QACPC,aACE,uEACA;QACFC,gBAAgB;IAClB;IACA;QACEH,KAAK;QACLC,OAAO;QACPC,aACE,4DACA,uEACA,sEACA,yEACA,uEACA,yEACA,sEACA,wEACA,sEACA,wEACA;QACFC,gBAAgB;IAClB;IACA,0EAA0E;IAC1E,yEAAyE;IACzE,0EAA0E;IAC1E,mCAAmC;IACnC;QACEH,KAAK;QACLC,OAAO;QACPC,aACE,wEACA,gEACA,wEACA;QACFC,gBAAgB;IAClB;IACA;QACEH,KAAK;QACLC,OAAO,GAAGH,oBAAoB,OAAO,CAAC;QACtCI,aACE,kEACA,sEACA,kEACA,0EACA,0EACA,oEACA,yEACA,mEACA,sEACA,gEACA,qEACA,sEACA,yEACA,wEACA,0EACA;QACFC,gBAAgB;IAClB;IACA,yEAAyE;IACzE,4EAA4E;IAC5E,mEAAmE;IACnE,+DAA+D;IAC/D;QACEH,KAAK;QACLC,OAAO;QACPC,aACE,sEACA,0EACA,sEACA;QACFC,gBAAgB;IAClB;IACA,0EAA0E;IAC1E,2EAA2E;IAC3E,2EAA2E;IAC3E,wEAAwE;IACxE,uEAAuE;IACvE,uEAAuE;IACvE,6DAA6D;IAC7D;QACEH,KAAK;QACLC,OAAO;QACPC,aACE,sEACA,2EACA,qEACA;QACFC,gBAAgB;IAClB;IACA,wEAAwE;IACxE,wEAAwE;IACxE,sEAAsE;IACtE,8DAA8D;IAC9D,yEAAyE;IACzE,yEAAyE;IACzE,wEAAwE;IACxE,sCAAsC;IACtC;QACEH,KAAK;QACLC,OAAO,GAAGH,oBAAoB,cAAc,CAAC;QAC7CI,aACE,6DACA,uEACA,wEACA,uEACA,uEACA,mEACA;QACFC,gBAAgB;IAClB;CACD,CAAA;AAED,OAAO,MAAME,oBAAoBN,cAAcO,GAAG,CAChD,CAACC,aAAeA,WAAWP,GAAG,EACF;AAE9B,OAAO,SAASQ,iBAAiBC,KAAa;IAC5C,OAAO,AAACJ,kBAAwCK,QAAQ,CAACD;AAC3D;AAEA,OAAO,SAASE,yBACdX,GAAmB;IAEnB,MAAMO,aAAaR,cAAca,IAAI,CAAC,CAACC,QAAUA,MAAMb,GAAG,KAAKA;IAC/D,IAAI,CAACO,YAAY,MAAM,IAAIO,MAAM,CAAC,sBAAsB,EAAEd,KAAK;IAC/D,OAAOO;AACT;AA8BA,MAAMQ,eAAe,CAACN;IACpB,MAAMO,UAAU,OAAOP,UAAU,YAAYQ,OAAOC,QAAQ,CAACT,SAASA,QAAQ;IAC9E,OAAOU,KAAKC,GAAG,CAAC,KAAKD,KAAKE,GAAG,CAAC,GAAGF,KAAKG,KAAK,CAACN;AAC9C;AAEA;;;;;;CAMC,GACD,OAAO,MAAMO,2BAA+C;OACvD1B;IACH;CACD,CAAA;AAED,MAAM2B,YAAY,CAACf,QACjB,OAAOA,UAAU,YACjBgB,OAAOC,SAAS,CAACC,cAAc,CAACC,IAAI,CAAChC,aAAaa;AAEpD;;;;;;;;;CASC,GACD,OAAO,SAASoB,0BAA0BC,IAAa;IACrD,MAAMC,QAAQR,yBAAyBS,OAAO,CAACF;IAC/C,OAAOC,QAAQ,IAAI,EAAE,GAAGR,yBAAyBU,KAAK,CAACF;AACzD;AAEA;;;;;;;;;;CAUC,GACD,OAAO,SAASG,sBAAsBC,GAAY;IAChD,IAAI,CAACC,MAAMC,OAAO,CAACF,MAAM,OAAOG;IAChC,MAAMC,QAAQ,IAAIC,IAAIL,IAAIM,MAAM,CAACjB;IACjC,IAAIe,MAAMG,IAAI,KAAK,GAAG,OAAOJ;IAC7B,OAAOf,yBAAyBkB,MAAM,CAAC,CAACX,OAASS,MAAMI,GAAG,CAACb;AAC7D;AAEA;;;;;CAKC,GACD,OAAO,SAASc,sBACdT,GAA8B,EAC9BU,eAAwB;IAExB,MAAMC,OAAOX,uBAAAA,IAAKY,IAAI;IACtB,IAAI,CAACD,MAAM,OAAO;QAAEE,SAASH;IAAgB;IAC7C,IAAIC,SAAS,QAAQ,OAAO;QAAEE,SAAS;IAAK;IAC5C,IAAIF,SAAS,SAAS,OAAO;QAAEE,SAAS;IAAM;IAC9C,IAAI;QACF,MAAMC,SAASC,KAAKC,KAAK,CAACL;QAC1B,IAAI,OAAOG,WAAW,WAAW,OAAO;YAAED,SAASC;QAAO;QAC1D,IAAIA,UAAU,OAAOA,WAAW,UAAU;YACxC,MAAMG,QAAQlB,sBAAsBe,OAAOG,KAAK;YAChD,OAAO;gBACLJ,SAASC,OAAOD,OAAO,KAAK;gBAC5BK,gBAAgBtC,aAAakC,OAAOI,cAAc;eAM9CD,QAAQ;gBAAEA;YAAM,IAAI,CAAC;gBACzBE,MAAM,OAAOL,OAAOK,IAAI,KAAK,WAAWL,OAAOK,IAAI,GAAGhB;;QAE1D;IACF,EAAE,eAAM;IACN,uCAAuC;IACzC;IACA,OAAO;QAAEU,SAASH;IAAgB;AACpC;AAEA;;;;;;;;;;;;;;CAcC,GACD,OAAO,MAAMU,sCAAsC,IAAG;AAEtD,SAASC,eAAeV,IAAY;IAClC,IAAIW,QAAQ;IACZ,KAAK,MAAMC,aAAaZ,KAAM;YACVY;QAAlB,MAAMC,aAAYD,yBAAAA,UAAUE,WAAW,CAAC,cAAtBF,yBAA4B;QAC9CD,SACEE,YAAY,OAAO,IAAIA,YAAY,QAAQ,IAAIA,YAAY,UAAU,IAAI;IAC7E;IACA,OAAOF;AACT;AAEA,qEAAqE,GACrE,OAAO,SAASI,4BAA4Bf,IAAY;IACtD,OAAOU,eAAeV,SAASS;AACjC;AAEA,MAAMO,uBAAuB;AAE7B;;;;;;;;CAQC,GACD,OAAO,SAASC,6BAA6BjB,IAAY;IACvD,IAAIe,4BAA4Bf,OAAO,OAAOA;IAC9C,MAAMkB,SACJT,sCAAsCC,eAAeM;IACvD,IAAIG,OAAO;IACX,IAAIR,QAAQ;IACZ,KAAK,MAAMC,aAAaZ,KAAM;QAC5B,MAAMJ,OAAOc,eAAeE;QAC5B,IAAID,QAAQf,OAAOsB,QAAQ;QAC3BC,QAAQP;QACRD,SAASf;IACX;IACA,MAAMwB,OAAOpB,KAAKqB,MAAM,CAACF,KAAKG,MAAM;IACpC,IAAIF,QAAQ,CAAC,KAAKG,IAAI,CAACH,OAAO;QAC5B,MAAMI,YAAYL,KAAKM,MAAM,CAAC;QAC9B,IAAID,YAAY,GAAGL,OAAOA,KAAKhC,KAAK,CAAC,GAAGqC;IAC1C;IACA,OAAO,GAAGL,KAAKO,OAAO,CAAC,kBAAkB,MAAMV,sBAAsB;AACvE;AAEA;;;;;;;;;;;;;;;CAeC,GACD,OAAO,SAASW,gCACdC,mBAA2B,EAC3BC,eAA0C;IAE1C,IAAId,4BAA4Ba,sBAAsB;QACpD,OAAOA;IACT;IACA,IACE,OAAOC,oBAAoB,YAC3BA,gBAAgB5B,IAAI,GAAGqB,MAAM,GAAG,KAChCP,4BAA4Bc,kBAC5B;QACA,OAAOA;IACT;IACA,OAAOZ,6BAA6BW;AACtC;AAEA;;;;CAIC,GACD,OAAO,SAASE,kBAAkBC,OAAe,EAAEC,SAAiB;IAClE,IAAIC,OAAO;IACX,MAAMC,OAAO,GAAGH,QAAQ,CAAC,EAAEC,WAAW;IACtC,IAAK,IAAI/C,QAAQ,GAAGA,QAAQiD,KAAKZ,MAAM,EAAErC,SAAS,EAAG;QACnDgD,QAAQC,KAAKC,UAAU,CAAClD;QACxBgD,OAAO5D,KAAK+D,IAAI,CAACH,MAAM;IACzB;IACA,OAAO,AAACA,CAAAA,SAAS,CAAA,IAAK;AACxB;AAEA;;;;;;;;;;;;;;;;;CAiBC,GACD,OAAO,SAASI,gBACdN,OAAuB,EACvBpE,KAAuB,EACvBqE,SAAoC,EACpC;;;;GAIC,GACDhD,IAAqB;IAErB,IAAI,CAACsD,uBAAuB3E,OAAOqB,OAAO,OAAO;IACjD,IAAIrB,MAAMuC,OAAO,EAAE,OAAO;IAC1B,MAAMhC,UAAUD,aAAaN,MAAM4C,cAAc;IACjD,IAAIrC,WAAW,KAAK,CAAC8D,WAAW,OAAO;IACvC,IAAI9D,WAAW,KAAK,OAAO;IAC3B,OAAO4D,kBAAkBC,SAASC,aAAa9D;AACjD;AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4BC,GACD,OAAO,SAASoE,uBACd3E,KAAuB,EACvBqB,IAAgC;IAEhC,MAAMsB,QAAQ3C,MAAM2C,KAAK;IACzB,4EAA4E;IAC5E,4EAA4E;IAC5E,+CAA+C;IAC/C,IAAIA,SAAS,QAAQA,MAAMgB,MAAM,KAAK,GAAG,OAAO;IAChD,IAAI,CAACtC,MAAM,OAAO;IAClB,OAAOsB,MAAM1C,QAAQ,CAACoB;AACxB;AAqBA;;;;;;;;;CASC,GACD,OAAO,SAASuD,6BACdlD,GAAY;IAEZ,IAAI,CAACA,OAAO,OAAOA,QAAQ,YAAYC,MAAMC,OAAO,CAACF,MAAM,OAAO,CAAC;IACnE,MAAMmD,YAAqC,CAAC;IAC5C,KAAK,MAAM,CAACtF,KAAKS,MAAM,IAAIgB,OAAO8D,OAAO,CAACpD,KAAiC;QACzE,IAAI,OAAO1B,UAAU,aAAaD,iBAAiBR,MAAM;YACvDsF,SAAS,CAACtF,IAAI,GAAGS;QACnB;IACF;IACA,OAAO6E;AACT;AAEA;;;;;;;;;CASC,GACD,OAAO,SAASE,sBACdX,OAAuB,EACvBpE,KAAuB,EACvBqE,SAAoC,EACpCQ,SAAqD,EACrD;;;;;;;;;;;;;;;;;;;GAmBC,GACDxD,IAAoB;IAEpB,MAAM2D,WAAWH,6BAAAA,SAAW,CAACT,QAAQ;IACrC,IAAI,OAAOY,aAAa,WAAW,OAAOA;IAC1C,OAAON,gBAAgBN,SAASpE,OAAOqE,WAAWhD;AACpD"}