Jumbo in the size mix (MTU 9000 + module jumbo pinned), check-first module config trusting GET reads, cable diag async at startup through the reset path, MODULES table dissolved into SETTINGS/LINKS, per-driver NIC counter sets, comment cleanup

counters.go

@@ -33,11 +33,8 @@ var nicTxFields = []string{
 // bad frame check twice. Named individually per driver, so nothing contains
 // anything else in its list.
 var nicRxStatsByDriver = map[string][]string{
-	// The reference set (E810). Below the frame: illegal_bytes is a 64b/66b
-	// block that decoded to no legal symbol, and the faults are the ordered
-	// sets the pcs sends when it loses sync. A cable going marginal moves
-	// these while every frame still arrives intact, which is as close to a
-	// bit error rate as this link will report.
+	// The reference set: illegal_bytes and the faults move while every frame
+	// still arrives intact — as close to a bit error rate as the link reports.
 	"ice": {
 		"rx_crc_errors.nic",
 		"rx_jabber.nic",
@@ -50,8 +47,7 @@ var nicRxStatsByDriver = map[string][]string{
 		"mac_remote_faults.nic",
 	},
 	// The 82599 exposes no jabber, fragment, illegal-byte or fault counters
-	// through ethtool — this is the closest bench set, and one of the X520
-	// divergences listed in docs/open-questions.md.
+	// (divergence: docs/open-questions.md).
 	"ixgbe": {
 		"rx_crc_errors",
 		"rx_missed_errors",