@threadbase-sh/streamer 1.47.3 → 1.49.0

package/dist/index.d.cts

@@ -1706,6 +1706,13 @@ type ApiDeps = {
     cacheMonitor: () => CacheIntegrityMonitor | null;
     /** Push registration + delivery state (C7). Null when the cache DB is unavailable. */
     pushRepo: () => PushRepository | null;
+    /**
+     * Whether Live Activity push is actually running on this server — the same
+     * fact the boot log reports as `live_activity.enabled`. Asked of the server
+     * rather than re-derived from the environment, because APNs credentials alone
+     * do not enable it: the sender is only wired when the token store opened too.
+     */
+    liveActivityPushEnabled: () => boolean;
     /** Paired-device registry (C5). Null when the cache DB is unavailable. */
     devicesRepo: () => DevicesRepository | null;
     projectsRepo: () => ProjectsRepository | null;
@@ -1954,6 +1961,7 @@ declare class StreamerServer {
     private apnsClient;
     private liveActivityNotifier;
     private liveActivityRenewal;
+    private waitingInputNotifier;
     private discoveryCache;
     private discoveryInFlight;
     private cacheDir;
@@ -2008,6 +2016,18 @@ declare class StreamerServer {
      * on disk; neither it nor any device token is ever logged.
      */
     private initLiveActivityPush;
+    /**
+     * Bring up "your turn" notifications over Expo's relay (#528).
+     *
+     * Unconditional, unlike Live Activity push: Expo holds the app's APNs and FCM
+     * credentials, so a self-hosted streamer needs no credential of its own. The
+     * access token is optional and only relevant if the Expo project has enhanced
+     * security enabled — requiring one would lock out every self-hoster, since
+     * they do not own the project. It is never logged.
+     */
+    private initWaitingInputPush;
+    /** Whether any live socket is subscribed to this session — "someone is looking". */
+    private hasSessionSubscriber;
     /**
      * Classify sessions left behind by previous streamer runs (C1 Phase 3a).
      *

package/dist/index.d.ts

@@ -1706,6 +1706,13 @@ type ApiDeps = {
     cacheMonitor: () => CacheIntegrityMonitor | null;
     /** Push registration + delivery state (C7). Null when the cache DB is unavailable. */
     pushRepo: () => PushRepository | null;
+    /**
+     * Whether Live Activity push is actually running on this server — the same
+     * fact the boot log reports as `live_activity.enabled`. Asked of the server
+     * rather than re-derived from the environment, because APNs credentials alone
+     * do not enable it: the sender is only wired when the token store opened too.
+     */
+    liveActivityPushEnabled: () => boolean;
     /** Paired-device registry (C5). Null when the cache DB is unavailable. */
     devicesRepo: () => DevicesRepository | null;
     projectsRepo: () => ProjectsRepository | null;
@@ -1954,6 +1961,7 @@ declare class StreamerServer {
     private apnsClient;
     private liveActivityNotifier;
     private liveActivityRenewal;
+    private waitingInputNotifier;
     private discoveryCache;
     private discoveryInFlight;
     private cacheDir;
@@ -2008,6 +2016,18 @@ declare class StreamerServer {
      * on disk; neither it nor any device token is ever logged.
      */
     private initLiveActivityPush;
+    /**
+     * Bring up "your turn" notifications over Expo's relay (#528).
+     *
+     * Unconditional, unlike Live Activity push: Expo holds the app's APNs and FCM
+     * credentials, so a self-hosted streamer needs no credential of its own. The
+     * access token is optional and only relevant if the Expo project has enhanced
+     * security enabled — requiring one would lock out every self-hoster, since
+     * they do not own the project. It is never logged.
+     */
+    private initWaitingInputPush;
+    /** Whether any live socket is subscribed to this session — "someone is looking". */
+    private hasSessionSubscriber;
     /**
      * Classify sessions left behind by previous streamer runs (C1 Phase 3a).
      *