@chatpanel/bridge 0.11.1 → 0.11.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chatpanel/bridge",
-  "version": "0.11.1",
+  "version": "0.11.3",
   "type": "module",
   "description": "Local bridge that exposes the AI coding agents installed on your machine \u2014 Claude Code (CLI), Codex (CLI), and Antigravity CLI (formerly Gemini CLI, which remains available for business/enterprise) \u2014 to the ChatPanel Chrome extension over a localhost SSE endpoint. Bring your own agent.",
   "keywords": [

package/src/channels/service.js

@@ -68,12 +68,15 @@ export function createChannelService({
   logger = console,
   fetchImpl = undefined,         // injected in tests
   now = () => Date.now(),
+  // The adapter is injectable for the same reason fetchImpl is: the thing worth asserting
+  // about the loop is WHAT it is handed, and a real Telegram long-poll cannot be asked.
+  startAdapter = startTelegram,
 } = {}) {
   const tokenFile = path.join(home, 'telegram-token');
   const configFile = path.join(dataDir, 'config.json');
   const pairingFile = path.join(dataDir, 'pairing.json');
 
-  let pairing = createPairingStore();
+  let pairing = null; // created by load(), then kept — see the note there
   let settings = { ...DEFAULT_SETTINGS };
   let appender = null;
   let bot = null;              // { id, username, name } once verified
@@ -83,7 +86,7 @@ export function createChannelService({
   let attempt = 0;
   let stopped = true;          // deliberate stop — suppresses the restart
 
-  const savePairing = () => writeJson(pairingFile, pairing.toJSON());
+  const savePairing = () => writeJson(pairingFile, pairing ? pairing.toJSON() : {});
   const saveSettings = () => writeJson(configFile, settings);
 
   async function readToken() {
@@ -100,7 +103,14 @@ export function createChannelService({
 
   async function load() {
     await mkdir(dataDir, { recursive: true });
-    pairing = createPairingStore(await readJson(pairingFile, {}), { now });
+    // Built ONCE and never replaced. spawnLoop() hands this exact object to the adapter, which
+    // holds it for the life of a polling loop — so rebuilding it here (as every service call
+    // used to) broke pairing in both directions at once: `pair()` minted the code into a fresh
+    // store the adapter could not see, so every redeem answered "unknown or expired code" no
+    // matter how many codes you generated; and `savePairing()` serialises whichever store this
+    // variable currently points at, so a redeem that DID land would have been persisted from
+    // the wrong object. Two aliases of one thing is the bug — there is only ever one store.
+    if (!pairing) pairing = createPairingStore(await readJson(pairingFile, {}), { now });
     settings = { ...DEFAULT_SETTINGS, ...(await readJson(configFile, {})) };
     if (!appender) appender = await createEventLog({ file: path.join(dataDir, 'events.jsonl'), host: 'channel' });
   }
@@ -110,7 +120,7 @@ export function createChannelService({
   function spawnLoop(botToken) {
     controller = new AbortController();
     running = true;
-    const done = startTelegram({
+    const done = startAdapter({
       botToken,
       baseUrl: bridge.baseUrl,
       token: bridge.token,

package/src/server.js

@@ -67,7 +67,7 @@ import {
 // Hardcoded (not read from package.json) so it survives Bun's single-file
 // --compile, where package.json isn't on a readable FS. CI fails the publish if
 // this drifts from package.json, so the two can't silently diverge.
-const VERSION = '0.11.1';
+const VERSION = '0.11.3';
 const HOST = process.env.CHATPANEL_BRIDGE_HOST || '127.0.0.1';
 const PORT = Number(process.env.CHATPANEL_BRIDGE_PORT) || 4319;
 

package/src/update.js

@@ -78,7 +78,20 @@ export async function checkForUpdate(current, { force = false } = {}) {
 
   let latest = null;
   let assetUrl = null;
+  // Whether `latest` is a real answer or yesterday's. GitHub's unauthenticated API is 60
+  // requests/hour per IP, and a developer machine burns that easily — so the fallback below
+  // is not rare, it fires regularly. Saying WHICH it is matters: acting on a stale "latest"
+  // is how a forced check reported "already on the latest version" minutes after a newer one
+  // was published, and how an earlier update landed on a version that was not the newest and
+  // called it a success.
+  let stale = false;
+  let error = '';
   const cache = await readCache();
+  const fallBackToCache = () => {
+    latest = cache?.latest || null;
+    assetUrl = cache?.assetUrl || null;
+    stale = true;
+  };
   if (!force && cache && Date.now() - cache.checkedAt < CHECK_EVERY_MS) {
     latest = cache.latest;
     assetUrl = cache.assetUrl;
@@ -91,12 +104,12 @@ export async function checkForUpdate(current, { force = false } = {}) {
         assetUrl = want ? (data.assets || []).find((a) => a.name === want)?.browser_download_url || null : null;
         await writeCache({ checkedAt: Date.now(), latest, assetUrl });
       } else {
-        latest = cache?.latest || null;
-        assetUrl = cache?.assetUrl || null;
+        error = res.status === 403 ? 'GitHub rate limit (60/hour per IP) — try again later' : `HTTP ${res.status}`;
+        fallBackToCache();
       }
-    } catch {
-      latest = cache?.latest || null;
-      assetUrl = cache?.assetUrl || null;
+    } catch (e) {
+      error = e?.message || String(e);
+      fallBackToCache();
     }
   }
   const updateAvailable = !!latest && cmp(latest, current) > 0;
@@ -110,6 +123,8 @@ export async function checkForUpdate(current, { force = false } = {}) {
     mode,
     canSelfUpdate,
     assetUrl,
+    stale,
+    error,
     npmCommand: mode === 'npm' ? 'npm i -g @chatpanel/bridge@latest' : null,
   };
 }
@@ -122,10 +137,16 @@ export async function selfUpdate(current) {
     throw new Error('Self-update applies only to the standalone binary. Update the npm/npx version with npm.');
   }
   const info = await checkForUpdate(current, { force: true });
-  if (!info.assetUrl) throw new Error('No downloadable build for this platform — use `npx @chatpanel/bridge`.');
-  if (!info.updateAvailable) {
-    throw new Error(info.latest ? `Already on the latest version (v${current}).` : 'Could not reach the update server.');
+  // A forced check that fell back to the cache has not checked anything. Acting on it is how
+  // an update reported success while installing a version that was already superseded, and how
+  // it later refused with "already on the latest version" while a newer one sat published.
+  // Say what actually happened and leave the binary alone.
+  if (info.stale) {
+    throw new Error(`Could not reach the update server${info.error ? ` (${info.error})` : ''}. `
+      + 'Refusing to act on a stale check — try again in a few minutes.');
   }
+  if (!info.assetUrl) throw new Error('No downloadable build for this platform — use `npx @chatpanel/bridge`.');
+  if (!info.updateAvailable) throw new Error(`Already on the latest version (v${current}).`);
 
   const target = process.execPath; // the running binary's own path
   const dir = path.dirname(target);