@threadbase-sh/streamer 1.55.4 → 1.56.0

package/dist/index.d.cts

@@ -145,6 +145,11 @@ declare const FEATURE_FLAGS: readonly [{
     readonly description: string;
     readonly default: false;
     readonly env: "THREADBASE_FEATURE_LIVE_ACTIVITY_PUSH";
+}, {
+    readonly id: "e2ee";
+    readonly description: string;
+    readonly default: false;
+    readonly env: "THREADBASE_FEATURE_E2EE";
 }, {
     readonly id: "ptyHost";
     readonly description: string;

package/dist/index.d.ts

@@ -145,6 +145,11 @@ declare const FEATURE_FLAGS: readonly [{
     readonly description: string;
     readonly default: false;
     readonly env: "THREADBASE_FEATURE_LIVE_ACTIVITY_PUSH";
+}, {
+    readonly id: "e2ee";
+    readonly description: string;
+    readonly default: false;
+    readonly env: "THREADBASE_FEATURE_E2EE";
 }, {
     readonly id: "ptyHost";
     readonly description: string;

package/dist/index.js

@@ -464,6 +464,12 @@ var FEATURE_FLAGS = [
     default: false,
     env: "THREADBASE_FEATURE_LIVE_ACTIVITY_PUSH"
   },
+  {
+    id: "e2ee",
+    description: "Application-layer encryption between a paired device and this server, independent of TLS, so a tunnel or a LAN observer on the path carries ciphertext. Off by default: it is negotiated per device, never forced, because released mobile builds cannot be force-updated and a server that demanded it would break every one of them.",
+    default: false,
+    env: "THREADBASE_FEATURE_E2EE"
+  },
   {
     id: "ptyHost",
     description: "Keep live PTYs in a separate host process so a streamer restart can reconnect without restarting the agents. Off by default until cross-platform behavior is qualified.",
@@ -5734,6 +5740,25 @@ function describePushCapability(liveActivityEnabled, env = process.env) {
     liveActivityReason: describeMissingApnsCredentials(env) ?? "APNs credentials are set but the push token store is unavailable, so Live Activity push is disabled."
   };
 }
+var E2EE_PROTOCOL_VERSION = 1;
+var E2EE_SUPPORTED = false;
+function describeE2eeCapability(flagEnabled) {
+  const enabled = E2EE_SUPPORTED && flagEnabled;
+  const base = {
+    supported: E2EE_SUPPORTED,
+    enabled,
+    version: E2EE_PROTOCOL_VERSION,
+    required: false
+  };
+  if (enabled) return base;
+  return {
+    ...base,
+    // Always says why, including when `supported` is false. An operator who set
+    // the flag and saw nothing happen has exactly one question, and a field that
+    // goes absent in the case they hit is the field not answering it.
+    reason: E2EE_SUPPORTED ? "disabled by the e2ee feature flag \u2014 set THREADBASE_FEATURE_E2EE=1, --feature e2ee=true, or feature_flags: in server.yaml" : "this build carries the capability negotiation but not yet the handshake it gates"
+  };
+}
 var identityKeyFailureLogged = false;
 function describeServerIdentityKey() {
   try {
@@ -5788,7 +5813,11 @@ var createMiscRoutes = (deps) => {
       // learn it without re-scanning. Additive: absent means a server with no
       // readable identity key, which a client must read as "cannot verify this
       // server" — never as a reason to fail the rest of this response.
-      serverIdentityKey: describeServerIdentityKey()
+      serverIdentityKey: describeServerIdentityKey(),
+      // Whether to encrypt to this server. Additive, same contract as `push`:
+      // absent means an older server, which a client must read as "unknown" and
+      // resolve as today's plaintext path — never as a reason to fail.
+      e2ee: describeE2eeCapability(deps.featureFlagsConfig().values.e2ee)
     });
   });
   app.get("/api/profiles", (c) => c.json([]));