let-them-talk 5.5.3 → 5.5.4

package/README.md

@@ -310,7 +310,7 @@ The verify suite doesn't claim to cover every provider or runtime matrix, and do
 - **Rate-limited** API endpoints on non-localhost requests.
 - **No telemetry, no cloud.** Everything runs locally.
 - **Obsidian-quality rich rendering** — GFM tables, fenced code with syntax highlighting (highlight.js), Obsidian-style callouts (`> [!NOTE]`, `> [!WARNING]`, `> [!SUMMARY]-` collapsible), Mermaid diagrams, KaTeX math, clickable image lightbox, copy-code buttons. Every shipping lib is bundled locally under `vendor/` so the dashboard works offline.
-- **0 known vulnerabilities** in the shipped tarball as of v5.5.3.
+- **0 known vulnerabilities** in the shipped tarball as of v5.5.4.
 - **Sensitive-path blocks** on file-share: `.env`, `.pem`, `.key`, `.lan-token`, `mcp.json`, and the agent-bridge data directory cannot be shared.
 - See [`SECURITY.md`](SECURITY.md) for the disclosure policy.
 

package/USAGE.md

@@ -1,6 +1,6 @@
 <!-- Generated from ../USAGE.md by scripts/sync-packaged-docs.js for published package consumers. -->
 
-# Let Them Talk Usage Guide v5.5.3
+# Let Them Talk Usage Guide v5.5.4
 
 This guide is the short operator view of the current runtime. For normative architecture details, use the docs under `docs/architecture/`.
 

package/cli.js

@@ -9,7 +9,7 @@ const { createCanonicalState } = require('./state/canonical');
 
 function printUsage() {
   console.log(`
-  Let Them Talk — Agent Bridge v5.5.3
+  Let Them Talk — Agent Bridge v5.5.4
   MCP message broker for inter-agent communication
   Supports: Claude Code, Gemini CLI, Codex CLI, Ollama
 

package/dashboard.js

@@ -3445,7 +3445,7 @@ server.listen(PORT, LAN_MODE ? '0.0.0.0' : '127.0.0.1', () => {
   const dataDir = resolveDataDir();
   const lanIP = getLanIP();
   console.log('');
-  console.log('  Let Them Talk - Agent Bridge Dashboard v5.5.3');
+  console.log('  Let Them Talk - Agent Bridge Dashboard v5.5.4');
   console.log('  ============================================');
   console.log('  Dashboard:  http://localhost:' + PORT);
   if (LAN_MODE && lanIP) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "let-them-talk",
-  "version": "5.5.3",
+  "version": "5.5.4",
   "description": "MCP message broker + web dashboard for inter-agent communication. Let AI CLI agents talk to each other.",
   "main": "server.js",
   "bin": {

package/scripts/repair-canonical-events.js

@@ -65,13 +65,27 @@ function repairBranch(branchDir, opts) {
 
   const kept = [];
   const orphans = [];
+  const duplicateRedactions = [];
+  const seenRedactedIds = new Set();
   for (const ev of events) {
     if (ev && (ev.type === 'message.redacted' || ev.type === 'message.corrected')) {
       const msgId = ev.payload && ev.payload.message_id;
+      // Orphan: no corresponding message.sent ancestor.
       if (msgId && !sentIds.has(msgId)) {
         orphans.push(ev);
         continue;
       }
+      // Duplicate redaction: same message_id already redacted earlier in the
+      // stream. Keep the first, drop subsequent ones. Pre-v5.5.4 the replay
+      // threw on the second redaction; now it tolerates duplicates, but we
+      // still want to prune the log so it's clean.
+      if (ev.type === 'message.redacted' && msgId) {
+        if (seenRedactedIds.has(msgId)) {
+          duplicateRedactions.push(ev);
+          continue;
+        }
+        seenRedactedIds.add(msgId);
+      }
     }
     kept.push(ev);
   }
@@ -82,6 +96,7 @@ function repairBranch(branchDir, opts) {
     message_sent_events: sentIds.size,
     orphan_redacted: orphans.filter((o) => o.type === 'message.redacted').length,
     orphan_corrected: orphans.filter((o) => o.type === 'message.corrected').length,
+    duplicate_redacted: duplicateRedactions.length,
     kept_events: kept.length,
   };
 
@@ -90,9 +105,9 @@ function repairBranch(branchDir, opts) {
     return result;
   }
 
-  if (orphans.length === 0) {
+  if (orphans.length === 0 && duplicateRedactions.length === 0) {
     result.skipped = true;
-    result.reason = 'no orphan events';
+    result.reason = 'no orphan or duplicate events';
     return result;
   }
 
@@ -151,13 +166,14 @@ function main(argv) {
       console.log('    skipped — ' + r.reason);
     } else {
       console.log(`    ${r.total_events} total events, ${r.message_sent_events} sent messages`);
-      console.log(`    orphan redactions: ${r.orphan_redacted}, orphan corrections: ${r.orphan_corrected}`);
+      console.log(`    orphan redactions: ${r.orphan_redacted}, orphan corrections: ${r.orphan_corrected}, duplicate redactions: ${r.duplicate_redacted}`);
       if (!dryRun) {
         console.log('    [ok] rewrote events.jsonl (' + r.kept_events + ' events kept)');
         console.log('    [ok] backup: ' + r.backup);
         console.log('    [ok] projections cleared — will rebuild on next read');
       } else {
-        console.log('    [dry-run] would drop ' + (r.orphan_redacted + r.orphan_corrected) + ' orphan event(s) and back up the original');
+        const drops = r.orphan_redacted + r.orphan_corrected + r.duplicate_redacted;
+        console.log('    [dry-run] would drop ' + drops + ' bad event(s) and back up the original');
       }
     }
   }

package/server.js

@@ -3708,7 +3708,7 @@ function buildListenGroupResponse(batch, consumed, agentName, listenStart) {
     return new Date(a.timestamp) - new Date(b.timestamp);
   });
 
-  // LEAN RESPONSE (v5.5.3+): the agent already has every prior message in its
+  // LEAN RESPONSE (v5.5.4+): the agent already has every prior message in its
   // own LLM context, plus the full rule set from get_guide() + AGENTS.md. We
   // only send the NEW messages + the managed-mode signals needed for
   // turn-taking. No repeated reminders, no agent rosters, no "next_action"
@@ -8136,7 +8136,7 @@ function toolToggleRule(ruleId) {
 // --- MCP Server setup ---
 
 const server = new Server(
-  { name: 'agent-bridge', version: '5.5.3' },
+  { name: 'agent-bridge', version: '5.5.4' },
   { capabilities: { tools: {} } }
 );
 
@@ -9265,7 +9265,7 @@ async function main() {
   try {
     const transport = new StdioServerTransport();
     await server.connect(transport);
-    console.error('Agent Bridge MCP server v5.5.3 running (65 tools)');
+    console.error('Agent Bridge MCP server v5.5.4 running (65 tools)');
   } catch (e) {
     console.error('ERROR: MCP server failed to start: ' + e.message);
     console.error('Fix: Run "npx let-them-talk doctor" to check your setup.');

package/state/messages.js

@@ -397,18 +397,15 @@ function createMessagesState(options = {}) {
       case 'message.redacted': {
         const redaction = validateCanonicalMessageRedactionPayload(event);
         const record = findProjectedMessageRecord(projection, redaction.messageId);
-        if (!record) {
-          throw createCanonicalReplayError(
-            CANONICAL_REPLAY_ERROR_CODES.INVALID_SEQUENCE,
-            `Canonical message replay cannot apply ${describeReplayEvent(event)} because message ${redaction.messageId} does not exist in the current branch projection.`,
-            {
-              event_type: event.type,
-              seq: event.seq,
-              branch_id: event.branch_id,
-              message_id: redaction.messageId,
-            }
-          );
-        }
+        // Redaction is idempotent: if the message is already gone from the
+        // projection (e.g. a prior message.redacted for the same id already
+        // ran during this replay), the second redaction is a no-op rather
+        // than a fatal error. The canonical log can legitimately carry
+        // multiple redaction events per id — operators running Clear
+        // Messages repeatedly on the same branch would produce that shape,
+        // and aborting the whole replay over it is worse than ignoring the
+        // duplicate.
+        if (!record) return projection;
 
         if (record.messageIndex >= 0) {
           record.conversation.messages.splice(record.messageIndex, 1);