Six places the interface says one thing and does another verifiedimportant

Collected in one place because they shape how much a MailerQ node can be trusted to report its own state, and because each is a reason our own interface exists. The DKIM checkbox does nothing. "Only use this key if it matches the public key found in DNS" is overwritten on save; enforce is derived from the algorithm choice instead. Its label is not even bound to the input. The config screen prints the console password. Database and broker credentials are masked; www-auth is not. Lists do not refresh after a save. The record is in the database and not on the screen. A DKIM key without a pattern signs nothing, and the list shows it as complete. DNS overrides have no menu entry — the screen opens only from a remote address card. Deleting a pool leaves its membership rows, so pool_ips accumulates rows pointing nowhere. None of them is fatal and all of them are quiet, which is the pattern: this console reports success for things that did not happen. An audit of a MailerQ node has to read the database, not the interface — and our own screens should show the database.