DL-337
Recovery after a publish-SIDE fabric failure (commit ok, publish fails — the loss mode the infallible bus never had) is triggered by a FABRIC-RECONNECT HOOK plus a minutes-scale PERIODIC FLOOR TICK, each running sweepAllLive + scanMissedMentions (OQ-3 part 2). This replaces the deleted sub.Lagged() bus-ring branch. The draft’s original mapping was falsified by the design-critic red-team: scanMissedMentions routes only mentions/ask-answers (never plain delivers) and NATS auto-reconnect (MaxReconnects(-1)) keeps the ConsumeContext alive so a “re-subscribe” trigger never fires across an outage — leaving a publish-failed plain deliver to an always-live agent silently undelivered until its next session restart. sweepAllLive (not just the scan) is the load-bearing plain-deliver recovery path; publisher-side bounded retry MAY be added but is not sufficient alone
Status: Active (Matt, 2026-09-05)