jschoubben
71a56d4606
mesh/delivery merged: source.main moved to novox/mesh-delivery@a37ee99b41d5
mesh/check pass 71a56d4606c9 on b73315ffe05c | carried from a37ee99b41d5 | unit 495 run, 947 kept | integration 494 run, 1014 kept | composition passe…
Both were published with the JetStream acknowledgement awaited, a request and response, for ten seconds each, and manifest-accepted once more on failure. On a bus refusing the subject (the old grants do not grant the new indexer mesh.seat.mesh-catalog.event.manifest-accepted) no acknowledgement ever came, so each judging pass took about twenty seconds a manifest and the indexer never reached the forge's messages nor the seat definitions: the take-in stood still. Now both are published plainly on their subject with the dedup id in Nats-Msg-Id, as an event is (the operator, 2026-11-07: everything is event-driven); the stream that keeps the subject drops a duplicate by its id, and a refusal is said on the connection's error handler, as the journal already shows. An error of the publish itself (no connection) still goes to the caller, which retries once and writes the unsaid finding. Quick vs thorough: thorough for these two events (every publish of a seat event by the indexer is now an event); sayTakeIn keeps its acknowledged publish, said in the issue for 47/G. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i