From 1e24f8ef86009fb1feef4fd4fc36be3305aa5dcc Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 2 Apr 2026 10:32:35 +0100 Subject: [PATCH] ax(ueps): replace prose ThreatScore comment with usage example AX Principle 2: comments must show usage with concrete values, not restate what the type signature already says. All other UEPSHeader field comments used assignment examples; ThreatScore was the outlier. Co-Authored-By: Charon --- pkg/ueps/packet.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkg/ueps/packet.go b/pkg/ueps/packet.go index a93c758..36cf0f3 100644 --- a/pkg/ueps/packet.go +++ b/pkg/ueps/packet.go @@ -34,7 +34,7 @@ type UEPSHeader struct { CurrentLayer uint8 // header.CurrentLayer = 5 // Application; 3 = Network, 4 = Transport TargetLayer uint8 // header.TargetLayer = 3 // Network; 5 = Application (loopback) IntentID uint8 // header.IntentID = 0x01 (ping), 0x02 (data), 0x03 (auth) - ThreatScore uint16 // 0–65535; elevated by integrity violations + ThreatScore uint16 // header.ThreatScore = 100 // elevated on HMAC mismatch; 0 = clean, 65535 = maximum threat } // builder := ueps.NewPacketBuilder(intentID, payload); frame, _ := builder.MarshalAndSign(secret)