Manifest entries now carry the CalVer release. An entry with no version,
or one that will not parse, is fetched unconditionally as before, so an
older bridge still updates a node.

@@ -1062,1 +1065,4 @@
 
+`version` is the image's CalVer release as `YYYY.MM.<counter>`, the same release
+the firmware reports in section 8.1. **The image is fetched only when that
+version is greater than the one the node is running**, comparing the packed

@@ -1063,0 +1070,4 @@
+not fetched: nothing is erased or written, the session reports no failure, and
+the node stays in state 2 until the radio idles out its timeout.
+
+An entry whose `version` is absent, is not a string, or is not three decimal

@@ -1063,0 +1072,4 @@
+
+An entry whose `version` is absent, is not a string, or is not three decimal
+fields within the ranges of section 8.1 is fetched unconditionally, whatever the
+node is running. A manifest written before this member existed therefore still

@@ -25,6 +28,28 @@ bool hexValue(char c, uint8_t& out) {
 	return false;
 }
 
+// Anything that is not three decimal fields in range reads as a development

@@ -28,0 +39,4 @@
+		if (i > 0 && (at >= end || *at++ != '.')) return can::version::development;
+
+		uint8_t digits = 0;
+		while (at < end && *at >= '0' && *at <= '9' && digits < versionFieldDigits) {

@@ -28,0 +43,4 @@
+			fields[i] = fields[i] * 10 + static_cast<uint32_t>(*at++ - '0');
+			++digits;
+		}
+		if (digits == 0) return can::version::development;

@@ -78,1 +79,4 @@
 
+constexpr uint16_t runningRelease = can::version::pack(2026, 9, 7);
+
+// The same manifest naming the release the node is already running.

@@ -25,6 +28,28 @@ bool hexValue(char c, uint8_t& out) {
 	return false;
 }
 
+// The CalVer release string of spec section 11.1. A field longer than its digit

@@ -207,0 +231,4 @@
+	TEST_ASSERT_TRUE(parse(versioned("2026.01.1"), bathroom, image));
+	TEST_ASSERT_EQUAL_HEX16(can::version::pack(2026, 1, 1), image.version);
+
+	TEST_ASSERT_TRUE(parse(versioned("2057.12.127"), bathroom, image));