server.knot: remove duplicate pruneExpired block comment
The pruneExpired section had two near-identical block comments
(lines 877-884 restated 894-898). Remove the redundant first copy.
Fourth deep server audit. No new correctness bugs found via active
runtime testing (real Ed25519 handshake, malformed input fuzzing,
long-poll behavior). Confirmed released Knot binaries ignore
--serverHost/--listenPort at runtime (divergent runtime tree from
local source at same tag) — existing startup warnings are correct.
commit8d304b5910bb662b7f2eca550e875c99c6ba3a42
authoriko <mail@iko.soy>
dateSun 12 Jul 2026, 04:04 (3 months ago)
parent9118bb4
server.knot−3
@@ -885,9 +885,6 @@ refreshLocalPresence = \pubkey expiry -> do
885885-- ============================================
886886-- Pruning
887887-- ============================================
888−-- Single sweep that drops expired entries from every state ref in one atomic
889−-- block. Returns the locally-expired presence rows whose pubkey has no other
890−-- live local session, so the caller can broadcast offline gossip for them.
891888
892889-- One sweep over every state ref: drops expired rows in a single atomic block.
893890-- Returns the locally-expired presence rows whose pubkey has no other live