@marinoscar/platform-web 0.1.0-next.3 → 0.1.0-next.5

package/dist/notifications/headless/useNotificationEvents.d.ts

@@ -0,0 +1,49 @@
+/**
+ * The notification event registry, read from the API.
+ *
+ * Issue #126, epic #109. Deliberately a plain fetch hook in the shape of
+ * `useEmailSettings` / `useSystemSettings` — same `isMounted` discipline, same
+ * "error is a string the page renders" contract — because that is all this is:
+ * one GET of a static, per-deployment list.
+ *
+ * WHY THIS IS FETCHED AT ALL, RATHER THAN IMPORTED FROM A CONSTANT
+ * ----------------------------------------------------------------
+ * The registry lives once, in `apps/api/src/notifications/notification-events.ts`,
+ * and the web app reads the server's answer instead of keeping a copy. Two
+ * things follow, and both are the point:
+ *
+ *   1. An event added to the API registry appears on `/settings/notifications`
+ *      with NO web change — epic #109's promise that a notification costs one
+ *      registry entry.
+ *   2. `mandatory` — a security flag — has exactly one declaration. A mirrored
+ *      copy is a second place for it to be wrong, and the wrong direction is an
+ *      enabled toggle on a security alert.
+ *
+ * The cost is a second request on this one page and a real loading state, which
+ * is why the page renders a spinner rather than an empty matrix: an empty
+ * matrix is indistinguishable from "this app notifies you about nothing".
+ *
+ * NOT CACHED ACROSS MOUNTS, on purpose. The list is small and this page is
+ * rarely visited; a module-level cache would be one more thing that can serve a
+ * stale `mandatory` after a deploy, for a saving nobody can perceive.
+ */
+import type { NotificationEventDef } from './types.js';
+interface UseNotificationEventsReturn {
+    /**
+     * The registry, IN SERVER ORDER — that order is meaningful (it is the order
+     * the preferences matrix renders) and is never re-sorted here.
+     *
+     * `null` until the first read resolves, which is NOT the same as `[]`. An
+     * empty array is a real answer ("this deployment declares no events") and the
+     * page says so; `null` means "we do not know yet" and the page shows a
+     * spinner. Collapsing the two would render "nothing to configure" during
+     * every load.
+     */
+    events: NotificationEventDef[] | null;
+    isLoading: boolean;
+    error: string | null;
+    refresh: () => Promise<void>;
+}
+export declare function useNotificationEvents(): UseNotificationEventsReturn;
+export {};
+//# sourceMappingURL=useNotificationEvents.d.ts.map

package/dist/notifications/headless/useNotificationEvents.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"useNotificationEvents.d.ts","sourceRoot":"","sources":["../../../src/notifications/headless/useNotificationEvents.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAIH,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,YAAY,CAAC;AAGvD,UAAU,2BAA2B;IACnC;;;;;;;;;OASG;IACH,MAAM,EAAE,oBAAoB,EAAE,GAAG,IAAI,CAAC;IACtC,SAAS,EAAE,OAAO,CAAC;IACnB,KAAK,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,OAAO,EAAE,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC;CAC9B;AAED,wBAAgB,qBAAqB,IAAI,2BAA2B,CAgCnE"}

package/dist/notifications/headless/useNotificationEvents.js

@@ -0,0 +1,64 @@
+/**
+ * The notification event registry, read from the API.
+ *
+ * Issue #126, epic #109. Deliberately a plain fetch hook in the shape of
+ * `useEmailSettings` / `useSystemSettings` — same `isMounted` discipline, same
+ * "error is a string the page renders" contract — because that is all this is:
+ * one GET of a static, per-deployment list.
+ *
+ * WHY THIS IS FETCHED AT ALL, RATHER THAN IMPORTED FROM A CONSTANT
+ * ----------------------------------------------------------------
+ * The registry lives once, in `apps/api/src/notifications/notification-events.ts`,
+ * and the web app reads the server's answer instead of keeping a copy. Two
+ * things follow, and both are the point:
+ *
+ *   1. An event added to the API registry appears on `/settings/notifications`
+ *      with NO web change — epic #109's promise that a notification costs one
+ *      registry entry.
+ *   2. `mandatory` — a security flag — has exactly one declaration. A mirrored
+ *      copy is a second place for it to be wrong, and the wrong direction is an
+ *      enabled toggle on a security alert.
+ *
+ * The cost is a second request on this one page and a real loading state, which
+ * is why the page renders a spinner rather than an empty matrix: an empty
+ * matrix is indistinguishable from "this app notifies you about nothing".
+ *
+ * NOT CACHED ACROSS MOUNTS, on purpose. The list is small and this page is
+ * rarely visited; a module-level cache would be one more thing that can serve a
+ * stale `mandatory` after a deploy, for a saving nobody can perceive.
+ */
+import { useCallback, useEffect, useState } from 'react';
+import { ApiError, getNotificationEvents } from './api.js';
+import { useIsMounted } from './useIsMounted.js';
+export function useNotificationEvents() {
+    const [events, setEvents] = useState(null);
+    const [isLoading, setIsLoading] = useState(true);
+    const [error, setError] = useState(null);
+    // Every `setState` past an `await` is guarded: a request that settles after
+    // the component is gone must not schedule an update on it. Same rule as the
+    // other fetch hooks in this directory.
+    const isMounted = useIsMounted();
+    const fetchEvents = useCallback(async () => {
+        try {
+            setIsLoading(true);
+            setError(null);
+            const data = await getNotificationEvents();
+            if (isMounted())
+                setEvents(data);
+        }
+        catch (err) {
+            if (isMounted()) {
+                setError(err instanceof ApiError ? err.message : 'Failed to load notification events');
+            }
+        }
+        finally {
+            if (isMounted())
+                setIsLoading(false);
+        }
+    }, [isMounted]);
+    useEffect(() => {
+        void fetchEvents();
+    }, [fetchEvents]);
+    return { events, isLoading, error, refresh: fetchEvents };
+}
+//# sourceMappingURL=useNotificationEvents.js.map

package/dist/notifications/headless/useNotificationEvents.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"useNotificationEvents.js","sourceRoot":"","sources":["../../../src/notifications/headless/useNotificationEvents.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAEH,OAAO,EAAE,WAAW,EAAE,SAAS,EAAE,QAAQ,EAAE,MAAM,OAAO,CAAC;AACzD,OAAO,EAAE,QAAQ,EAAE,qBAAqB,EAAE,MAAM,UAAU,CAAC;AAE3D,OAAO,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AAmBjD,MAAM,UAAU,qBAAqB;IACnC,MAAM,CAAC,MAAM,EAAE,SAAS,CAAC,GAAG,QAAQ,CAAgC,IAAI,CAAC,CAAC;IAC1E,MAAM,CAAC,SAAS,EAAE,YAAY,CAAC,GAAG,QAAQ,CAAC,IAAI,CAAC,CAAC;IACjD,MAAM,CAAC,KAAK,EAAE,QAAQ,CAAC,GAAG,QAAQ,CAAgB,IAAI,CAAC,CAAC;IAExD,4EAA4E;IAC5E,4EAA4E;IAC5E,uCAAuC;IACvC,MAAM,SAAS,GAAG,YAAY,EAAE,CAAC;IAEjC,MAAM,WAAW,GAAG,WAAW,CAAC,KAAK,IAAI,EAAE;QACzC,IAAI,CAAC;YACH,YAAY,CAAC,IAAI,CAAC,CAAC;YACnB,QAAQ,CAAC,IAAI,CAAC,CAAC;YACf,MAAM,IAAI,GAAG,MAAM,qBAAqB,EAAE,CAAC;YAC3C,IAAI,SAAS,EAAE;gBAAE,SAAS,CAAC,IAAI,CAAC,CAAC;QACnC,CAAC;QAAC,OAAO,GAAG,EAAE,CAAC;YACb,IAAI,SAAS,EAAE,EAAE,CAAC;gBAChB,QAAQ,CACN,GAAG,YAAY,QAAQ,CAAC,CAAC,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,oCAAoC,CAC7E,CAAC;YACJ,CAAC;QACH,CAAC;gBAAS,CAAC;YACT,IAAI,SAAS,EAAE;gBAAE,YAAY,CAAC,KAAK,CAAC,CAAC;QACvC,CAAC;IACH,CAAC,EAAE,CAAC,SAAS,CAAC,CAAC,CAAC;IAEhB,SAAS,CAAC,GAAG,EAAE;QACb,KAAK,WAAW,EAAE,CAAC;IACrB,CAAC,EAAE,CAAC,WAAW,CAAC,CAAC,CAAC;IAElB,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,KAAK,EAAE,OAAO,EAAE,WAAW,EAAE,CAAC;AAC5D,CAAC"}

package/dist/notifications/headless/usePushConfig.d.ts

@@ -0,0 +1,50 @@
+/**
+ * Load, save, generate, rotate and remove the deployment's Web Push (VAPID)
+ * configuration. Issue #355.
+ *
+ * TWO SEPARATE FLAG GROUPS, on purpose. `save` (the enable/disable switch
+ * plus the subject field) is a routine, non-destructive edit — shaped after
+ * `useEmailSettings`'s `save`, including the same `If-Match` / 409 handling.
+ * `generate` / `rotate` / `remove` share one `isActing` / `actionError` pair
+ * instead — shaped after `useDbBackupActions` — because they are triggered
+ * from the same confirmation dialog and only one of them is ever "in
+ * flight" for this page at a time; collapsing them into `save`'s flags would
+ * make the ordinary Save button spin while a rotation is confirmed, or vice
+ * versa.
+ *
+ * Every write RESOLVES `true`/`false` rather than throwing, for the same
+ * reason `useEmailSettings.save` does: every caller is a click handler that
+ * needs to branch, and the error has already been captured for rendering.
+ *
+ * THE RESPONSE IS ALWAYS THE NEW BASELINE. Every one of these five calls
+ * returns the full `PushConfigAdminView`, and this hook adopts it every
+ * time — including after `remove`, which comes back `configured: false` and
+ * is what flips the page back to its empty state with no reload.
+ */
+import type { PushConfigAdminView, PushConfigSubjectInput, UpdatePushConfigInput } from './pushConfig.js';
+interface UsePushConfigReturn {
+    config: PushConfigAdminView | null;
+    isLoading: boolean;
+    /** Failure to LOAD. Distinct from the write errors below: "nothing to show" vs. "your change did not stick". */
+    loadError: string | null;
+    isSaving: boolean;
+    saveError: string | null;
+    /** `PUT` — enable/disable and the subject. Non-destructive; keys are retained either way. */
+    save: (input: UpdatePushConfigInput) => Promise<boolean>;
+    clearSaveError: () => void;
+    /** True while generate, rotate or remove is in flight. */
+    isActing: boolean;
+    /** The last failure from generate/rotate/remove, or `null`. */
+    actionError: string | null;
+    clearActionError: () => void;
+    /** First-time setup. `409` if already configured. */
+    generate: (input?: PushConfigSubjectInput) => Promise<boolean>;
+    /** DESTRUCTIVE — every existing subscriber goes dark until it re-subscribes. */
+    rotate: (input?: PushConfigSubjectInput) => Promise<boolean>;
+    /** DESTRUCTIVE — deletes the key pair entirely. */
+    remove: () => Promise<boolean>;
+    refresh: () => Promise<void>;
+}
+export declare function usePushConfig(): UsePushConfigReturn;
+export {};
+//# sourceMappingURL=usePushConfig.d.ts.map

package/dist/notifications/headless/usePushConfig.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"usePushConfig.d.ts","sourceRoot":"","sources":["../../../src/notifications/headless/usePushConfig.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AAWH,OAAO,KAAK,EAAE,mBAAmB,EAAE,sBAAsB,EAAE,qBAAqB,EAAE,MAAM,iBAAiB,CAAC;AAY1G,UAAU,mBAAmB;IAC3B,MAAM,EAAE,mBAAmB,GAAG,IAAI,CAAC;IACnC,SAAS,EAAE,OAAO,CAAC;IACnB,gHAAgH;IAChH,SAAS,EAAE,MAAM,GAAG,IAAI,CAAC;IAEzB,QAAQ,EAAE,OAAO,CAAC;IAClB,SAAS,EAAE,MAAM,GAAG,IAAI,CAAC;IACzB,6FAA6F;IAC7F,IAAI,EAAE,CAAC,KAAK,EAAE,qBAAqB,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;IACzD,cAAc,EAAE,MAAM,IAAI,CAAC;IAE3B,0DAA0D;IAC1D,QAAQ,EAAE,OAAO,CAAC;IAClB,+DAA+D;IAC/D,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,gBAAgB,EAAE,MAAM,IAAI,CAAC;IAC7B,qDAAqD;IACrD,QAAQ,EAAE,CAAC,KAAK,CAAC,EAAE,sBAAsB,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;IAC/D,gFAAgF;IAChF,MAAM,EAAE,CAAC,KAAK,CAAC,EAAE,sBAAsB,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;IAC7D,mDAAmD;IACnD,MAAM,EAAE,MAAM,OAAO,CAAC,OAAO,CAAC,CAAC;IAE/B,OAAO,EAAE,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC;CAC9B;AAED,wBAAgB,aAAa,IAAI,mBAAmB,CAuHnD"}

package/dist/notifications/headless/usePushConfig.js

@@ -0,0 +1,143 @@
+/**
+ * Load, save, generate, rotate and remove the deployment's Web Push (VAPID)
+ * configuration. Issue #355.
+ *
+ * TWO SEPARATE FLAG GROUPS, on purpose. `save` (the enable/disable switch
+ * plus the subject field) is a routine, non-destructive edit — shaped after
+ * `useEmailSettings`'s `save`, including the same `If-Match` / 409 handling.
+ * `generate` / `rotate` / `remove` share one `isActing` / `actionError` pair
+ * instead — shaped after `useDbBackupActions` — because they are triggered
+ * from the same confirmation dialog and only one of them is ever "in
+ * flight" for this page at a time; collapsing them into `save`'s flags would
+ * make the ordinary Save button spin while a rotation is confirmed, or vice
+ * versa.
+ *
+ * Every write RESOLVES `true`/`false` rather than throwing, for the same
+ * reason `useEmailSettings.save` does: every caller is a click handler that
+ * needs to branch, and the error has already been captured for rendering.
+ *
+ * THE RESPONSE IS ALWAYS THE NEW BASELINE. Every one of these five calls
+ * returns the full `PushConfigAdminView`, and this hook adopts it every
+ * time — including after `remove`, which comes back `configured: false` and
+ * is what flips the page back to its empty state with no reload.
+ */
+import { useCallback, useEffect, useState } from 'react';
+import { ApiError } from './api.js';
+import { generatePushConfig, getPushConfig, removePushConfig, rotatePushConfig, updatePushConfig, } from './pushConfig.js';
+import { useIsMounted } from './useIsMounted.js';
+/** 403 is named explicitly — it is the one failure an admin can act on themselves. */
+function messageFor(err, fallback) {
+    if (err instanceof ApiError) {
+        if (err.status === 403)
+            return 'You do not have permission to manage web push configuration';
+        return err.message || fallback;
+    }
+    return fallback;
+}
+export function usePushConfig() {
+    const [config, setConfig] = useState(null);
+    const [isLoading, setIsLoading] = useState(true);
+    const [loadError, setLoadError] = useState(null);
+    const [isSaving, setIsSaving] = useState(false);
+    const [saveError, setSaveError] = useState(null);
+    const [isActing, setIsActing] = useState(false);
+    const [actionError, setActionError] = useState(null);
+    const isMounted = useIsMounted();
+    const fetchConfig = useCallback(async () => {
+        try {
+            setIsLoading(true);
+            setLoadError(null);
+            const data = await getPushConfig();
+            if (isMounted())
+                setConfig(data);
+        }
+        catch (err) {
+            if (isMounted())
+                setLoadError(messageFor(err, 'Failed to load web push configuration'));
+        }
+        finally {
+            if (isMounted())
+                setIsLoading(false);
+        }
+    }, [isMounted]);
+    useEffect(() => {
+        void fetchConfig();
+    }, [fetchConfig]);
+    /**
+     * `PUT`, adopting whatever the server says the config now is.
+     *
+     * A `409` means someone else saved between this page's load and this
+     * click (or a stale `version` from before a generate/rotate/remove that
+     * happened in another tab) — reload rather than retry, exactly as
+     * `useEmailSettings.save` does, so the next save is asserted against the
+     * row that is actually live.
+     */
+    const save = useCallback(async (input) => {
+        try {
+            setIsSaving(true);
+            setSaveError(null);
+            const data = await updatePushConfig(input, config?.version ?? 0);
+            if (isMounted())
+                setConfig(data);
+            return true;
+        }
+        catch (err) {
+            if (err instanceof ApiError && err.status === 409) {
+                await fetchConfig();
+                if (isMounted()) {
+                    setSaveError('Someone else changed the web push configuration while you were editing. ' +
+                        'The form has been reloaded with the current configuration — review it and save again.');
+                }
+                return false;
+            }
+            if (isMounted())
+                setSaveError(messageFor(err, 'Failed to save web push configuration'));
+            return false;
+        }
+        finally {
+            if (isMounted())
+                setIsSaving(false);
+        }
+    }, [config, fetchConfig, isMounted]);
+    const runAction = useCallback(async (operation, fallback) => {
+        try {
+            setIsActing(true);
+            setActionError(null);
+            const data = await operation();
+            if (isMounted())
+                setConfig(data);
+            return true;
+        }
+        catch (err) {
+            if (isMounted())
+                setActionError(messageFor(err, fallback));
+            return false;
+        }
+        finally {
+            if (isMounted())
+                setIsActing(false);
+        }
+    }, [isMounted]);
+    const generate = useCallback((input = {}) => runAction(() => generatePushConfig(input), 'Failed to generate a key pair'), [runAction]);
+    const rotate = useCallback((input = {}) => runAction(() => rotatePushConfig(input), 'Failed to rotate the key pair'), [runAction]);
+    const remove = useCallback(() => runAction(() => removePushConfig(), 'Failed to remove the web push configuration'), [runAction]);
+    const clearSaveError = useCallback(() => setSaveError(null), []);
+    const clearActionError = useCallback(() => setActionError(null), []);
+    return {
+        config,
+        isLoading,
+        loadError,
+        isSaving,
+        saveError,
+        save,
+        clearSaveError,
+        isActing,
+        actionError,
+        clearActionError,
+        generate,
+        rotate,
+        remove,
+        refresh: fetchConfig,
+    };
+}
+//# sourceMappingURL=usePushConfig.js.map

package/dist/notifications/headless/usePushConfig.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"usePushConfig.js","sourceRoot":"","sources":["../../../src/notifications/headless/usePushConfig.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AAEH,OAAO,EAAE,WAAW,EAAE,SAAS,EAAE,QAAQ,EAAE,MAAM,OAAO,CAAC;AACzD,OAAO,EAAE,QAAQ,EAAE,MAAM,UAAU,CAAC;AACpC,OAAO,EACL,kBAAkB,EAClB,aAAa,EACb,gBAAgB,EAChB,gBAAgB,EAChB,gBAAgB,GACjB,MAAM,iBAAiB,CAAC;AAEzB,OAAO,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AAEjD,sFAAsF;AACtF,SAAS,UAAU,CAAC,GAAY,EAAE,QAAgB;IAChD,IAAI,GAAG,YAAY,QAAQ,EAAE,CAAC;QAC5B,IAAI,GAAG,CAAC,MAAM,KAAK,GAAG;YAAE,OAAO,6DAA6D,CAAC;QAC7F,OAAO,GAAG,CAAC,OAAO,IAAI,QAAQ,CAAC;IACjC,CAAC;IACD,OAAO,QAAQ,CAAC;AAClB,CAAC;AA6BD,MAAM,UAAU,aAAa;IAC3B,MAAM,CAAC,MAAM,EAAE,SAAS,CAAC,GAAG,QAAQ,CAA6B,IAAI,CAAC,CAAC;IACvE,MAAM,CAAC,SAAS,EAAE,YAAY,CAAC,GAAG,QAAQ,CAAC,IAAI,CAAC,CAAC;IACjD,MAAM,CAAC,SAAS,EAAE,YAAY,CAAC,GAAG,QAAQ,CAAgB,IAAI,CAAC,CAAC;IAChE,MAAM,CAAC,QAAQ,EAAE,WAAW,CAAC,GAAG,QAAQ,CAAC,KAAK,CAAC,CAAC;IAChD,MAAM,CAAC,SAAS,EAAE,YAAY,CAAC,GAAG,QAAQ,CAAgB,IAAI,CAAC,CAAC;IAChE,MAAM,CAAC,QAAQ,EAAE,WAAW,CAAC,GAAG,QAAQ,CAAC,KAAK,CAAC,CAAC;IAChD,MAAM,CAAC,WAAW,EAAE,cAAc,CAAC,GAAG,QAAQ,CAAgB,IAAI,CAAC,CAAC;IAEpE,MAAM,SAAS,GAAG,YAAY,EAAE,CAAC;IAEjC,MAAM,WAAW,GAAG,WAAW,CAAC,KAAK,IAAI,EAAE;QACzC,IAAI,CAAC;YACH,YAAY,CAAC,IAAI,CAAC,CAAC;YACnB,YAAY,CAAC,IAAI,CAAC,CAAC;YACnB,MAAM,IAAI,GAAG,MAAM,aAAa,EAAE,CAAC;YACnC,IAAI,SAAS,EAAE;gBAAE,SAAS,CAAC,IAAI,CAAC,CAAC;QACnC,CAAC;QAAC,OAAO,GAAG,EAAE,CAAC;YACb,IAAI,SAAS,EAAE;gBAAE,YAAY,CAAC,UAAU,CAAC,GAAG,EAAE,uCAAuC,CAAC,CAAC,CAAC;QAC1F,CAAC;gBAAS,CAAC;YACT,IAAI,SAAS,EAAE;gBAAE,YAAY,CAAC,KAAK,CAAC,CAAC;QACvC,CAAC;IACH,CAAC,EAAE,CAAC,SAAS,CAAC,CAAC,CAAC;IAEhB,SAAS,CAAC,GAAG,EAAE;QACb,KAAK,WAAW,EAAE,CAAC;IACrB,CAAC,EAAE,CAAC,WAAW,CAAC,CAAC,CAAC;IAElB;;;;;;;;OAQG;IACH,MAAM,IAAI,GAAG,WAAW,CACtB,KAAK,EAAE,KAA4B,EAAoB,EAAE;QACvD,IAAI,CAAC;YACH,WAAW,CAAC,IAAI,CAAC,CAAC;YAClB,YAAY,CAAC,IAAI,CAAC,CAAC;YACnB,MAAM,IAAI,GAAG,MAAM,gBAAgB,CAAC,KAAK,EAAE,MAAM,EAAE,OAAO,IAAI,CAAC,CAAC,CAAC;YACjE,IAAI,SAAS,EAAE;gBAAE,SAAS,CAAC,IAAI,CAAC,CAAC;YACjC,OAAO,IAAI,CAAC;QACd,CAAC;QAAC,OAAO,GAAG,EAAE,CAAC;YACb,IAAI,GAAG,YAAY,QAAQ,IAAI,GAAG,CAAC,MAAM,KAAK,GAAG,EAAE,CAAC;gBAClD,MAAM,WAAW,EAAE,CAAC;gBACpB,IAAI,SAAS,EAAE,EAAE,CAAC;oBAChB,YAAY,CACV,0EAA0E;wBACxE,uFAAuF,CAC1F,CAAC;gBACJ,CAAC;gBACD,OAAO,KAAK,CAAC;YACf,CAAC;YACD,IAAI,SAAS,EAAE;gBAAE,YAAY,CAAC,UAAU,CAAC,GAAG,EAAE,uCAAuC,CAAC,CAAC,CAAC;YACxF,OAAO,KAAK,CAAC;QACf,CAAC;gBAAS,CAAC;YACT,IAAI,SAAS,EAAE;gBAAE,WAAW,CAAC,KAAK,CAAC,CAAC;QACtC,CAAC;IACH,CAAC,EACD,CAAC,MAAM,EAAE,WAAW,EAAE,SAAS,CAAC,CACjC,CAAC;IAEF,MAAM,SAAS,GAAG,WAAW,CAC3B,KAAK,EAAE,SAA6C,EAAE,QAAgB,EAAoB,EAAE;QAC1F,IAAI,CAAC;YACH,WAAW,CAAC,IAAI,CAAC,CAAC;YAClB,cAAc,CAAC,IAAI,CAAC,CAAC;YACrB,MAAM,IAAI,GAAG,MAAM,SAAS,EAAE,CAAC;YAC/B,IAAI,SAAS,EAAE;gBAAE,SAAS,CAAC,IAAI,CAAC,CAAC;YACjC,OAAO,IAAI,CAAC;QACd,CAAC;QAAC,OAAO,GAAG,EAAE,CAAC;YACb,IAAI,SAAS,EAAE;gBAAE,cAAc,CAAC,UAAU,CAAC,GAAG,EAAE,QAAQ,CAAC,CAAC,CAAC;YAC3D,OAAO,KAAK,CAAC;QACf,CAAC;gBAAS,CAAC;YACT,IAAI,SAAS,EAAE;gBAAE,WAAW,CAAC,KAAK,CAAC,CAAC;QACtC,CAAC;IACH,CAAC,EACD,CAAC,SAAS,CAAC,CACZ,CAAC;IAEF,MAAM,QAAQ,GAAG,WAAW,CAC1B,CAAC,QAAgC,EAAE,EAAE,EAAE,CACrC,SAAS,CAAC,GAAG,EAAE,CAAC,kBAAkB,CAAC,KAAK,CAAC,EAAE,+BAA+B,CAAC,EAC7E,CAAC,SAAS,CAAC,CACZ,CAAC;IAEF,MAAM,MAAM,GAAG,WAAW,CACxB,CAAC,QAAgC,EAAE,EAAE,EAAE,CACrC,SAAS,CAAC,GAAG,EAAE,CAAC,gBAAgB,CAAC,KAAK,CAAC,EAAE,+BAA+B,CAAC,EAC3E,CAAC,SAAS,CAAC,CACZ,CAAC;IAEF,MAAM,MAAM,GAAG,WAAW,CACxB,GAAG,EAAE,CAAC,SAAS,CAAC,GAAG,EAAE,CAAC,gBAAgB,EAAE,EAAE,6CAA6C,CAAC,EACxF,CAAC,SAAS,CAAC,CACZ,CAAC;IAEF,MAAM,cAAc,GAAG,WAAW,CAAC,GAAG,EAAE,CAAC,YAAY,CAAC,IAAI,CAAC,EAAE,EAAE,CAAC,CAAC;IACjE,MAAM,gBAAgB,GAAG,WAAW,CAAC,GAAG,EAAE,CAAC,cAAc,CAAC,IAAI,CAAC,EAAE,EAAE,CAAC,CAAC;IAErE,OAAO;QACL,MAAM;QACN,SAAS;QACT,SAAS;QACT,QAAQ;QACR,SAAS;QACT,IAAI;QACJ,cAAc;QACd,QAAQ;QACR,WAAW;QACX,gBAAgB;QAChB,QAAQ;QACR,MAAM;QACN,MAAM;QACN,OAAO,EAAE,WAAW;KACrB,CAAC;AACJ,CAAC"}

package/dist/notifications/headless/usePushSubscriptionSync.d.ts

@@ -0,0 +1,54 @@
+/**
+ * Keep this device's Web Push subscription alive — issue #365, epic #215.
+ *
+ * MOUNTED ONCE, in `components/common/Layout.tsx`, which only renders for an
+ * authenticated user. It owns two automatic behaviours and one shared action:
+ *
+ *   1. THE AUTO-PROMPT. When the deployment offers push (and has not switched
+ *      browser notifications off) and this device has never been asked, the
+ *      permission prompt is requested as soon as the shell loads — at most once
+ *      per page load (`claimAutoPermissionPrompt`). A product decision that
+ *      replaces the earlier "only ever from a click" rule. Firefox and Safari
+ *      ignore a gestureless request and Chrome may quiet it, which is why the
+ *      app-wide `NotificationPermissionBanner` still offers a button.
+ *   2. THE BOOT SYNC. Whenever permission is `granted` and push is enabled,
+ *      subscribe if needed and POST the subscription (an idempotent upsert).
+ *      Runs on every load and again the moment permission becomes `granted`.
+ *   3. `requestPermission` — ask, then sync. The banner's button uses it.
+ */
+import { type NotificationCapability } from './useNotificationCapability.js';
+import type { NotificationConfigResponse } from './types.js';
+/**
+ * What {@link usePushSubscriptionSync} returns, for the permission banner.
+ *
+ * @stability experimental
+ */
+export interface UsePushSubscriptionSyncResult {
+    /** `null` until `GET /api/notifications/config` resolves. */
+    config: NotificationConfigResponse | null;
+    /** What this device can do about browser notifications. */
+    capability: NotificationCapability;
+    /** Ask for permission (from a click), then subscribe and sync if granted. */
+    requestPermission: () => Promise<void>;
+    /** Whether the permission prompt is open. */
+    isRequestingPermission: boolean;
+}
+/**
+ * The shell's once-per-load push sync (#365): reads the deployment's
+ * notification config, re-syncs this browser's Web Push subscription when
+ * permission is granted, and offers the permission request the app-wide
+ * banner shows. Call it once, from the app shell.
+ *
+ * @returns the config, the device capability and the request action.
+ *
+ * @example
+ * ```tsx
+ * const push = usePushSubscriptionSync();
+ * <NotificationPermissionBanner config={push.config} capability={push.capability} onRequestPermission={push.requestPermission} />
+ * ```
+ *
+ * @extensionPoint hook
+ * @stability experimental
+ */
+export declare function usePushSubscriptionSync(): UsePushSubscriptionSyncResult;
+//# sourceMappingURL=usePushSubscriptionSync.d.ts.map

package/dist/notifications/headless/usePushSubscriptionSync.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"usePushSubscriptionSync.d.ts","sourceRoot":"","sources":["../../../src/notifications/headless/usePushSubscriptionSync.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAIH,OAAO,EAA6B,KAAK,sBAAsB,EAAE,MAAM,gCAAgC,CAAC;AAOxG,OAAO,KAAK,EAAE,0BAA0B,EAAE,MAAM,YAAY,CAAC;AAE7D;;;;GAIG;AACH,MAAM,WAAW,6BAA6B;IAC5C,6DAA6D;IAC7D,MAAM,EAAE,0BAA0B,GAAG,IAAI,CAAC;IAC1C,2DAA2D;IAC3D,UAAU,EAAE,sBAAsB,CAAC;IACnC,6EAA6E;IAC7E,iBAAiB,EAAE,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC;IACvC,6CAA6C;IAC7C,sBAAsB,EAAE,OAAO,CAAC;CACjC;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,uBAAuB,IAAI,6BAA6B,CAyCvE"}

package/dist/notifications/headless/usePushSubscriptionSync.js

@@ -0,0 +1,83 @@
+/**
+ * Keep this device's Web Push subscription alive — issue #365, epic #215.
+ *
+ * MOUNTED ONCE, in `components/common/Layout.tsx`, which only renders for an
+ * authenticated user. It owns two automatic behaviours and one shared action:
+ *
+ *   1. THE AUTO-PROMPT. When the deployment offers push (and has not switched
+ *      browser notifications off) and this device has never been asked, the
+ *      permission prompt is requested as soon as the shell loads — at most once
+ *      per page load (`claimAutoPermissionPrompt`). A product decision that
+ *      replaces the earlier "only ever from a click" rule. Firefox and Safari
+ *      ignore a gestureless request and Chrome may quiet it, which is why the
+ *      app-wide `NotificationPermissionBanner` still offers a button.
+ *   2. THE BOOT SYNC. Whenever permission is `granted` and push is enabled,
+ *      subscribe if needed and POST the subscription (an idempotent upsert).
+ *      Runs on every load and again the moment permission becomes `granted`.
+ *   3. `requestPermission` — ask, then sync. The banner's button uses it.
+ */
+import { useCallback, useEffect, useState } from 'react';
+import { useIsMounted } from './useIsMounted.js';
+import { useNotificationCapability } from './useNotificationCapability.js';
+import { useNotificationConfig } from './useNotificationConfig.js';
+import { claimAutoPermissionPrompt, requestPermissionAndSyncPush, syncPushSubscription, } from './pushSubscription.js';
+/**
+ * The shell's once-per-load push sync (#365): reads the deployment's
+ * notification config, re-syncs this browser's Web Push subscription when
+ * permission is granted, and offers the permission request the app-wide
+ * banner shows. Call it once, from the app shell.
+ *
+ * @returns the config, the device capability and the request action.
+ *
+ * @example
+ * ```tsx
+ * const push = usePushSubscriptionSync();
+ * <NotificationPermissionBanner config={push.config} capability={push.capability} onRequestPermission={push.requestPermission} />
+ * ```
+ *
+ * @extensionPoint hook
+ * @stability experimental
+ */
+export function usePushSubscriptionSync() {
+    const { config } = useNotificationConfig();
+    // `=== false`, never `!browserEnabled`: a `null` config is "not known yet".
+    const { capability, permission, refresh } = useNotificationCapability({
+        adminDisabled: config?.browserEnabled === false,
+    });
+    const isMounted = useIsMounted();
+    const [isRequestingPermission, setIsRequestingPermission] = useState(false);
+    const requestPermission = useCallback(async () => {
+        setIsRequestingPermission(true);
+        try {
+            await requestPermissionAndSyncPush(config);
+        }
+        finally {
+            if (isMounted()) {
+                setIsRequestingPermission(false);
+                refresh();
+            }
+        }
+    }, [config, isMounted, refresh]);
+    // 1. The auto-prompt. `capability === 'default'` already excludes every
+    //    state where asking is impossible or pointless (admin-disabled,
+    //    insecure, unsupported, iOS tab, denied, granted).
+    useEffect(() => {
+        if (!config?.pushEnabled || config.browserEnabled === false)
+            return;
+        if (capability !== 'default')
+            return;
+        if (!claimAutoPermissionPrompt())
+            return;
+        void requestPermission();
+    }, [config, capability, requestPermission]);
+    // 2. The boot sync. Keyed on the primitives, so a config refetch returning
+    //    the same values does not re-POST; a rotated key does.
+    const vapidPublicKey = config?.pushEnabled ? config.vapidPublicKey : null;
+    useEffect(() => {
+        if (permission !== 'granted' || !vapidPublicKey)
+            return;
+        void syncPushSubscription(vapidPublicKey);
+    }, [permission, vapidPublicKey]);
+    return { config, capability, requestPermission, isRequestingPermission };
+}
+//# sourceMappingURL=usePushSubscriptionSync.js.map

package/dist/notifications/headless/usePushSubscriptionSync.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"usePushSubscriptionSync.js","sourceRoot":"","sources":["../../../src/notifications/headless/usePushSubscriptionSync.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,OAAO,EAAE,WAAW,EAAE,SAAS,EAAE,QAAQ,EAAE,MAAM,OAAO,CAAC;AACzD,OAAO,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AACjD,OAAO,EAAE,yBAAyB,EAA+B,MAAM,gCAAgC,CAAC;AACxG,OAAO,EAAE,qBAAqB,EAAE,MAAM,4BAA4B,CAAC;AACnE,OAAO,EACL,yBAAyB,EACzB,4BAA4B,EAC5B,oBAAoB,GACrB,MAAM,uBAAuB,CAAC;AAmB/B;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,UAAU,uBAAuB;IACrC,MAAM,EAAE,MAAM,EAAE,GAAG,qBAAqB,EAAE,CAAC;IAC3C,4EAA4E;IAC5E,MAAM,EAAE,UAAU,EAAE,UAAU,EAAE,OAAO,EAAE,GAAG,yBAAyB,CAAC;QACpE,aAAa,EAAE,MAAM,EAAE,cAAc,KAAK,KAAK;KAChD,CAAC,CAAC;IAEH,MAAM,SAAS,GAAG,YAAY,EAAE,CAAC;IACjC,MAAM,CAAC,sBAAsB,EAAE,yBAAyB,CAAC,GAAG,QAAQ,CAAC,KAAK,CAAC,CAAC;IAE5E,MAAM,iBAAiB,GAAG,WAAW,CAAC,KAAK,IAAI,EAAE;QAC/C,yBAAyB,CAAC,IAAI,CAAC,CAAC;QAChC,IAAI,CAAC;YACH,MAAM,4BAA4B,CAAC,MAAM,CAAC,CAAC;QAC7C,CAAC;gBAAS,CAAC;YACT,IAAI,SAAS,EAAE,EAAE,CAAC;gBAChB,yBAAyB,CAAC,KAAK,CAAC,CAAC;gBACjC,OAAO,EAAE,CAAC;YACZ,CAAC;QACH,CAAC;IACH,CAAC,EAAE,CAAC,MAAM,EAAE,SAAS,EAAE,OAAO,CAAC,CAAC,CAAC;IAEjC,wEAAwE;IACxE,oEAAoE;IACpE,uDAAuD;IACvD,SAAS,CAAC,GAAG,EAAE;QACb,IAAI,CAAC,MAAM,EAAE,WAAW,IAAI,MAAM,CAAC,cAAc,KAAK,KAAK;YAAE,OAAO;QACpE,IAAI,UAAU,KAAK,SAAS;YAAE,OAAO;QACrC,IAAI,CAAC,yBAAyB,EAAE;YAAE,OAAO;QACzC,KAAK,iBAAiB,EAAE,CAAC;IAC3B,CAAC,EAAE,CAAC,MAAM,EAAE,UAAU,EAAE,iBAAiB,CAAC,CAAC,CAAC;IAE5C,2EAA2E;IAC3E,2DAA2D;IAC3D,MAAM,cAAc,GAAG,MAAM,EAAE,WAAW,CAAC,CAAC,CAAC,MAAM,CAAC,cAAc,CAAC,CAAC,CAAC,IAAI,CAAC;IAC1E,SAAS,CAAC,GAAG,EAAE;QACb,IAAI,UAAU,KAAK,SAAS,IAAI,CAAC,cAAc;YAAE,OAAO;QACxD,KAAK,oBAAoB,CAAC,cAAc,CAAC,CAAC;IAC5C,CAAC,EAAE,CAAC,UAAU,EAAE,cAAc,CAAC,CAAC,CAAC;IAEjC,OAAO,EAAE,MAAM,EAAE,UAAU,EAAE,iBAAiB,EAAE,sBAAsB,EAAE,CAAC;AAC3E,CAAC"}

package/dist/notifications/headless/useVisiblePolling.d.ts

@@ -0,0 +1,55 @@
+/**
+ * `useVisiblePolling` — an interval that stops with the tab.
+ *
+ * Introduced by issue #266 for the jobs page and EXTRACTED here by #271, when
+ * the worker-fleet page needed the same behaviour. Extracted rather than
+ * copied, and the distinction is the whole point of this file existing: two
+ * implementations of "poll, but not in a background tab" would be two places
+ * the `visibilitychange` teardown could be got subtly wrong, and the second
+ * one would be discovered the way the first would have been — by a dashboard
+ * left open overnight, months later, in somebody's database load graph.
+ *
+ * `hooks/useJobs.ts` and `hooks/useWorkerNodes.ts` both RE-EXPORT this so each
+ * page keeps importing its polling from the hook module it already depends on
+ * (and so a page test that mocks that module still intercepts the poll). The
+ * re-exports are aliases of this one function; there is exactly one
+ * implementation, and this is it.
+ *
+ * =============================================================================
+ * WHY THE INTERVAL STOPS WITH THE TAB
+ * =============================================================================
+ *
+ * These pages poll because their contents change with nobody touching them: a
+ * queue drains, a worker stops heartbeating. An operator watching either needs
+ * the numbers to move, and a manual refresh button turns "is it recovering"
+ * into a clicking exercise.
+ *
+ * A bare `setInterval` keeps firing in a background tab, and that is not a
+ * micro-optimisation to skip. A dashboard left open on a second monitor
+ * overnight is ~2,900 requests at a 10-second poll — each one a real query
+ * against the same database the workers are competing for — and every response
+ * is discarded, because nobody is looking. Browsers throttle background timers
+ * but do not stop them, and the throttling is neither uniform nor something a
+ * server capacity plan can rely on.
+ *
+ * So the interval is torn down on `visibilitychange` to hidden and rebuilt on
+ * the way back, with ONE IMMEDIATE FETCH on return. The immediate fetch is the
+ * half that makes the pause invisible to the operator: without it, a tab
+ * restored after an hour would show hour-old numbers for up to a full interval,
+ * which is worse than not pausing at all — stale data that looks live.
+ */
+/**
+ * Call `callback` every `intervalMs` — but only while the document is visible.
+ *
+ * `callback` is held in a ref rather than being an effect dependency: a page
+ * naturally passes a fresh closure on every render (it reads the current
+ * filters), and depending on it directly would tear down and rebuild the
+ * interval on every keystroke, so the timer would never actually reach its
+ * period. The ref is updated on each render, so a tick always calls the
+ * LATEST closure while the timer itself survives.
+ *
+ * `intervalMs <= 0` disables polling entirely, which is what a test — or a
+ * caller with no reason to poll — passes.
+ */
+export declare function useVisiblePolling(callback: () => void, intervalMs: number): void;
+//# sourceMappingURL=useVisiblePolling.d.ts.map

package/dist/notifications/headless/useVisiblePolling.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"useVisiblePolling.d.ts","sourceRoot":"","sources":["../../../src/notifications/headless/useVisiblePolling.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuCG;AAIH;;;;;;;;;;;;GAYG;AACH,wBAAgB,iBAAiB,CAAC,QAAQ,EAAE,MAAM,IAAI,EAAE,UAAU,EAAE,MAAM,GAAG,IAAI,CA4ChF"}

package/dist/notifications/headless/useVisiblePolling.js

@@ -0,0 +1,96 @@
+/**
+ * `useVisiblePolling` — an interval that stops with the tab.
+ *
+ * Introduced by issue #266 for the jobs page and EXTRACTED here by #271, when
+ * the worker-fleet page needed the same behaviour. Extracted rather than
+ * copied, and the distinction is the whole point of this file existing: two
+ * implementations of "poll, but not in a background tab" would be two places
+ * the `visibilitychange` teardown could be got subtly wrong, and the second
+ * one would be discovered the way the first would have been — by a dashboard
+ * left open overnight, months later, in somebody's database load graph.
+ *
+ * `hooks/useJobs.ts` and `hooks/useWorkerNodes.ts` both RE-EXPORT this so each
+ * page keeps importing its polling from the hook module it already depends on
+ * (and so a page test that mocks that module still intercepts the poll). The
+ * re-exports are aliases of this one function; there is exactly one
+ * implementation, and this is it.
+ *
+ * =============================================================================
+ * WHY THE INTERVAL STOPS WITH THE TAB
+ * =============================================================================
+ *
+ * These pages poll because their contents change with nobody touching them: a
+ * queue drains, a worker stops heartbeating. An operator watching either needs
+ * the numbers to move, and a manual refresh button turns "is it recovering"
+ * into a clicking exercise.
+ *
+ * A bare `setInterval` keeps firing in a background tab, and that is not a
+ * micro-optimisation to skip. A dashboard left open on a second monitor
+ * overnight is ~2,900 requests at a 10-second poll — each one a real query
+ * against the same database the workers are competing for — and every response
+ * is discarded, because nobody is looking. Browsers throttle background timers
+ * but do not stop them, and the throttling is neither uniform nor something a
+ * server capacity plan can rely on.
+ *
+ * So the interval is torn down on `visibilitychange` to hidden and rebuilt on
+ * the way back, with ONE IMMEDIATE FETCH on return. The immediate fetch is the
+ * half that makes the pause invisible to the operator: without it, a tab
+ * restored after an hour would show hour-old numbers for up to a full interval,
+ * which is worse than not pausing at all — stale data that looks live.
+ */
+import { useEffect, useRef } from 'react';
+/**
+ * Call `callback` every `intervalMs` — but only while the document is visible.
+ *
+ * `callback` is held in a ref rather than being an effect dependency: a page
+ * naturally passes a fresh closure on every render (it reads the current
+ * filters), and depending on it directly would tear down and rebuild the
+ * interval on every keystroke, so the timer would never actually reach its
+ * period. The ref is updated on each render, so a tick always calls the
+ * LATEST closure while the timer itself survives.
+ *
+ * `intervalMs <= 0` disables polling entirely, which is what a test — or a
+ * caller with no reason to poll — passes.
+ */
+export function useVisiblePolling(callback, intervalMs) {
+    const callbackRef = useRef(callback);
+    callbackRef.current = callback;
+    useEffect(() => {
+        if (intervalMs <= 0)
+            return;
+        let timer = null;
+        const stop = () => {
+            if (timer !== null) {
+                clearInterval(timer);
+                timer = null;
+            }
+        };
+        const start = () => {
+            // Guarded rather than assumed: `visibilitychange` can fire more than
+            // once for the same effective state, and an unguarded `setInterval`
+            // would leak a second timer and double the request rate.
+            if (timer !== null)
+                return;
+            timer = setInterval(() => callbackRef.current(), intervalMs);
+        };
+        const onVisibilityChange = () => {
+            if (document.hidden) {
+                stop();
+                return;
+            }
+            // Catch up FIRST, then resume — see the file header on why a resumed
+            // poll that waits out a full interval is worse than never pausing.
+            callbackRef.current();
+            start();
+        };
+        // A tab that is already hidden at mount never starts one.
+        if (!document.hidden)
+            start();
+        document.addEventListener('visibilitychange', onVisibilityChange);
+        return () => {
+            stop();
+            document.removeEventListener('visibilitychange', onVisibilityChange);
+        };
+    }, [intervalMs]);
+}
+//# sourceMappingURL=useVisiblePolling.js.map

package/dist/notifications/headless/useVisiblePolling.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"useVisiblePolling.js","sourceRoot":"","sources":["../../../src/notifications/headless/useVisiblePolling.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuCG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,EAAE,MAAM,OAAO,CAAC;AAE1C;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,iBAAiB,CAAC,QAAoB,EAAE,UAAkB;IACxE,MAAM,WAAW,GAAG,MAAM,CAAC,QAAQ,CAAC,CAAC;IACrC,WAAW,CAAC,OAAO,GAAG,QAAQ,CAAC;IAE/B,SAAS,CAAC,GAAG,EAAE;QACb,IAAI,UAAU,IAAI,CAAC;YAAE,OAAO;QAE5B,IAAI,KAAK,GAA0C,IAAI,CAAC;QAExD,MAAM,IAAI,GAAG,GAAG,EAAE;YAChB,IAAI,KAAK,KAAK,IAAI,EAAE,CAAC;gBACnB,aAAa,CAAC,KAAK,CAAC,CAAC;gBACrB,KAAK,GAAG,IAAI,CAAC;YACf,CAAC;QACH,CAAC,CAAC;QAEF,MAAM,KAAK,GAAG,GAAG,EAAE;YACjB,qEAAqE;YACrE,oEAAoE;YACpE,yDAAyD;YACzD,IAAI,KAAK,KAAK,IAAI;gBAAE,OAAO;YAC3B,KAAK,GAAG,WAAW,CAAC,GAAG,EAAE,CAAC,WAAW,CAAC,OAAO,EAAE,EAAE,UAAU,CAAC,CAAC;QAC/D,CAAC,CAAC;QAEF,MAAM,kBAAkB,GAAG,GAAG,EAAE;YAC9B,IAAI,QAAQ,CAAC,MAAM,EAAE,CAAC;gBACpB,IAAI,EAAE,CAAC;gBACP,OAAO;YACT,CAAC;YACD,qEAAqE;YACrE,mEAAmE;YACnE,WAAW,CAAC,OAAO,EAAE,CAAC;YACtB,KAAK,EAAE,CAAC;QACV,CAAC,CAAC;QAEF,0DAA0D;QAC1D,IAAI,CAAC,QAAQ,CAAC,MAAM;YAAE,KAAK,EAAE,CAAC;QAC9B,QAAQ,CAAC,gBAAgB,CAAC,kBAAkB,EAAE,kBAAkB,CAAC,CAAC;QAElE,OAAO,GAAG,EAAE;YACV,IAAI,EAAE,CAAC;YACP,QAAQ,CAAC,mBAAmB,CAAC,kBAAkB,EAAE,kBAAkB,CAAC,CAAC;QACvE,CAAC,CAAC;IACJ,CAAC,EAAE,CAAC,UAAU,CAAC,CAAC,CAAC;AACnB,CAAC"}