@cello-protocol/daemon 0.0.184 → 0.0.185

package/dist/session-node-manager.js

@@ -9162,7 +9162,22 @@ export class SessionNodeManager {
                     "because sealing on a record the counterparty cannot match produces a receipt only one " +
                     "side can verify.",
             });
-            return { placed: true, leafIndex };
+            /**
+             * ─── `016-RELAYLOSS`: CARRIED TO THE CALLER, because the log is not a consumer ────────────
+             *
+             * Measured with a real relay black-holed mid-conversation: the send stalls for the submit
+             * timeout, then returns `{ok: true, sequence_number: N, delivered: true}` — BYTE-IDENTICAL to
+             * the witnessed send that preceded it. The error above is correct, complete, and read by
+             * nobody the operator can ask.
+             *
+             * Its two siblings twenty lines below already do this: `diverged` and the held case both
+             * refuse to return an ordinary success, on the stated grounds that doing so "reports a
+             * healthy send on a conversation that has silently lost the one thing the protocol exists to
+             * produce." This branch is where that loss OCCURS — `position_behind_frontier`'s own comment
+             * says the seal "was already lost at the unwitnessed append, not here" — so it is the branch
+             * that most needed to say so, and it was the one that said nothing.
+             */
+            return { placed: true, leafIndex, unwitnessed: true };
         }
         if (assignedSeq === nextExpected) {
             const { leafIndex } = this.appendSessionLeaf(agentName, sessionId, kind, contentHashHex, correlationId);