Record what a node is actually configured to do verifiedimportant
Six readings that capture everything a node's behaviour depends on — and the baseline to restore it from.
In detail
A MailerQ node's behaviour lives in four places, and a configuration file alone describes one of them. The tables carry the limits, the interceptions and the keys; the broker carries the topology and the backlog; the plugin directory carries code. This is also our own safety rule made concrete: every experiment in this catalogue started with this capture and ended with a comparison against it. The stand was left with a configuration file whose checksum matched the one taken before the work began, and with every table we had written to back at zero rows.