chore: release v0.26.2

internal/lookup/lookup.go

@@ -45,6 +45,17 @@ type Result struct {
 	// and nothing used to read it — and since no live activation feed exists for
 	// IOTA the way it does for POTA, the callbook record is the practical source.
 	IOTA string `json:"iota,omitempty"`
+	// RDA is the Russian District Award reference (KE-29). HamQTH publishes it
+	// as <oblast>, described in their own documentation as "something like
+	// district (Russian stations)"; QRZ.com has no equivalent — its county and
+	// state fields are USA-only.
+	//
+	// It is the CURRENT district, which is why it may only ever be applied to a
+	// contact being made now. A Russian station can move, and stamping today's
+	// district on a three-year-old QSO rewrites a correct contact into a wrong
+	// one. DXLab solves the general case with dated activity records; we solve
+	// the case that matters by never dating anything but the present.
+	RDA string `json:"rda,omitempty"`
 	// Zip is the postal code. HamQTH and QRZ both send one.
 	Zip       string    `json:"zip,omitempty"`
 	ImageURL  string    `json:"image_url,omitempty"` // profile picture URL