AeroNyx Node Health and Relay-Smoke Verification

Relay-smoke verification boundary

Source implemented

The reviewed candidate source provides a local-only, explicitly confirmed relay-smoke workflow. Its preflight requires healthy service checks, no active sessions, ready peer quorum and route pool, at least two receipt-capable peers, ChatRelay runtime readiness, and strong-enough custody durability. The run creates ephemeral sender and receiver state, performs the real encrypted UDP handshake, sends end-to-end ciphertext through the selected multi-hop path, verifies the terminal receipt, pulls and acknowledges the mailbox item, closes sessions, and emits an aggregate-only result.

Automated tests verified

On the commander integration worktree, the server now compiles and three privacy-diagnostic relay-smoke tests passed. The socket-bound end-to-end smoke could not complete because the validation environment denied UDP binding. Therefore the diagnostic test scope is verified, while authenticated end-to-end relay-smoke remains not verified.

Current fleet verified

No 2026-08-31 release-specific r7 relay-smoke output has been supplied. The public aggregate snapshot is useful health context, but it cannot substitute for a successful smoke run with a verified terminal receipt, mailbox acknowledgement, and cleanup. Current-fleet relay-smoke status is therefore awaiting verification.

Operator acceptance rule

Accept a smoke result only when every preflight passes, the result is fresh, the expected terminal receipt verifies, mailbox pull and acknowledgement succeed, sessions close, and the report contains aggregate fields only. Any missing gate, stale receipt, cleanup failure, or privacy-redaction failure is a failed verification—not a degraded success.

Do not confuse this authenticated relay-smoke round trip with the operator script's synthetic fleet-smoke. The synthetic check sends a random opaque probe to test path mechanics; it is not user traffic and does not prove mailbox delivery.

Do not publish node addresses, SSH details, credentials, configuration paths, identities, routes, payloads, mailbox items, client addresses, DNS, or per-user history. Share only the bounded aggregate report and its timestamp.