Jean d2a8d0ef05 Stamp a traceable incident id into every kick and kill ... A single choke-point in handle() gives each outgoing Kick / KillUser a short id, appends it to the reason the user sees ([#3F]), and records a searchable summary in a bounded per-node incident ring on the live network view. So a bot flood-kick, a fantasy kick, a votekick, and an operator KICK are all logged the same way, and the id in a kick reason ties back to the log entry. Exposed via NetView::search_incidents (id-exact or summary substring, newest first) for the LOGSEARCH command to come.		2026-07-14 02:09:45 +00:00
..
engine	Stamp a traceable incident id into every kick and kill	2026-07-14 02:09:45 +00:00
config.rs	OperServ: per-IP session limiting with exceptions	2026-07-14 01:46:09 +00:00
gossip.rs	Clippy sweep: clean across the workspace	2026-07-13 23:30:51 +00:00
grpc.rs	OperServ: per-IP session limiting with exceptions	2026-07-14 01:46:09 +00:00
jsonrpc.rs	jsonrpc: optional TLS termination (HTTP/2)	2026-07-13 21:10:26 +00:00
link.rs	email: HTML templates and multipart messages	2026-07-12 15:57:34 +00:00
main.rs	OperServ: per-IP session limiting with exceptions	2026-07-14 01:46:09 +00:00
proto.rs	modules: split services and the ircd link into external crates	2026-07-13 01:33:56 +00:00