v3.0.0

Every business topic now has a dead letter shadow. A record whose handler keeps failing is retried in place with exponential backoff and is then published to <topic>.dlq with its original coordinates and the exception in headers, so the partition moves on instead of stalling behind it. POST /admin/dlq/{topic}/replay reads dead letters back onto their source topic with a dedicated consumer group and commits only after the republish, and the consumers that had already applied the event ignore the replay by event id. A replay count travels with the record, so once it has used up ledgermesh.dlq.max-replays the replayer parks it instead of starting another lap. Consumer lag and dead letter depth are recomputed from broker offsets into gauges, and every failed delivery is counted per topic.