@northguild/gmt 1.18.0 → 1.19.0

package/dist/utc/parse/parseMinuteFromUtc.d.ts

@@ -14,8 +14,10 @@
  */
 export declare function parseMinuteFromUtc(value: string, options?: {
     /**
-     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `""`.
+     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `""`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/utc/parse/parseMinuteFromUtc.js

@@ -1,4 +1,4 @@
-import { utcZonedDateTime } from "../../internal/utcZonedDateTime.js";
+import { utcWallClock } from "../../internal/utcWallClock.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
 /**
  * Return the minute (0-59) from a UTC datetime string.
@@ -19,7 +19,7 @@ export function parseMinuteFromUtc(value, options) {
         if (!isOptionsArgument(options)) {
             return "";
         }
-        const dateTime = utcZonedDateTime(value, options);
+        const dateTime = utcWallClock(value, options);
         return dateTime === null ? "" : dateTime.minute.toString().padStart(2, "0");
     }
     catch {

package/dist/utc/parse/parseMonthFromUtc.d.ts

@@ -14,8 +14,10 @@
  */
 export declare function parseMonthFromUtc(value: string, options?: {
     /**
-     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `""`.
+     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `""`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/utc/parse/parseMonthFromUtc.js

@@ -1,4 +1,4 @@
-import { utcZonedDateTime } from "../../internal/utcZonedDateTime.js";
+import { utcWallClock } from "../../internal/utcWallClock.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
 /**
  * Return the month (1-12) from a UTC datetime string.
@@ -19,7 +19,7 @@ export function parseMonthFromUtc(value, options) {
         if (!isOptionsArgument(options)) {
             return "";
         }
-        const dateTime = utcZonedDateTime(value, options);
+        const dateTime = utcWallClock(value, options);
         return dateTime === null ? "" : dateTime.month.toString().padStart(2, "0");
     }
     catch {

package/dist/utc/parse/parseNanosecondFromUtc.d.ts

@@ -15,8 +15,10 @@
  */
 export declare function parseNanosecondFromUtc(value: string, options?: {
     /**
-     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `""`.
+     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `""`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/utc/parse/parseNanosecondFromUtc.js

@@ -1,4 +1,4 @@
-import { utcZonedDateTime } from "../../internal/utcZonedDateTime.js";
+import { utcWallClock } from "../../internal/utcWallClock.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
 /**
  * Return the nanosecond (0-999) from a UTC datetime string.
@@ -20,7 +20,7 @@ export function parseNanosecondFromUtc(value, options) {
         if (!isOptionsArgument(options)) {
             return "";
         }
-        const dateTime = utcZonedDateTime(value, options);
+        const dateTime = utcWallClock(value, options);
         return dateTime === null
             ? ""
             : dateTime.nanosecond.toString().padStart(3, "0");

package/dist/utc/parse/parseSecondFromUtc.d.ts

@@ -14,8 +14,10 @@
  */
 export declare function parseSecondFromUtc(value: string, options?: {
     /**
-     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `""`.
+     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `""`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/utc/parse/parseSecondFromUtc.js

@@ -1,4 +1,4 @@
-import { utcZonedDateTime } from "../../internal/utcZonedDateTime.js";
+import { utcWallClock } from "../../internal/utcWallClock.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
 /**
  * Return the second (0-59) from a UTC datetime string.
@@ -19,7 +19,7 @@ export function parseSecondFromUtc(value, options) {
         if (!isOptionsArgument(options)) {
             return "";
         }
-        const dateTime = utcZonedDateTime(value, options);
+        const dateTime = utcWallClock(value, options);
         return dateTime === null ? "" : dateTime.second.toString().padStart(2, "0");
     }
     catch {

package/dist/utc/parse/parseTimeFromUtc.d.ts

@@ -11,11 +11,14 @@
  * @example parseTimeFromUtc("2024-03-17T14:30:45Z") // "14:30:45"
  * @example parseTimeFromUtc("2024-03-17T14:30:45Z", { timeZone: "America/New_York" }) // "10:30:45"
  * @example parseTimeFromUtc("invalid") // ""
+ * @example parseTimeFromUtc("1970-01-01T12:44:30Z", { timeZone: "-00:44:30" }) // "12:00:00" (a stored offset with seconds)
  */
 export declare function parseTimeFromUtc(value: string, options?: {
     /**
-     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `""`.
+     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `""`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/utc/parse/parseTimeFromUtc.js

@@ -1,5 +1,5 @@
 import { Temporal } from "@js-temporal/polyfill";
-import { normalizeTimeZone } from "../../internal/normalizeTimeZone.js";
+import { frameWallClock, normalizeZoneFrame } from "../../internal/zoneFrame.js";
 import { isValidUtc } from "../validate/index.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
 /**
@@ -15,6 +15,7 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  * @example parseTimeFromUtc("2024-03-17T14:30:45Z") // "14:30:45"
  * @example parseTimeFromUtc("2024-03-17T14:30:45Z", { timeZone: "America/New_York" }) // "10:30:45"
  * @example parseTimeFromUtc("invalid") // ""
+ * @example parseTimeFromUtc("1970-01-01T12:44:30Z", { timeZone: "-00:44:30" }) // "12:00:00" (a stored offset with seconds)
  */
 export function parseTimeFromUtc(value, options) {
     try {
@@ -24,13 +25,13 @@ export function parseTimeFromUtc(value, options) {
         if (!isValidUtc(value)) {
             return "";
         }
-        const timeZone = normalizeTimeZone(options?.timeZone);
-        if (timeZone === "") {
+        const frame = normalizeZoneFrame(options?.timeZone);
+        if (frame === null) {
             return "";
         }
         try {
             const instant = Temporal.Instant.from(value);
-            const dateTime = instant.toZonedDateTimeISO(timeZone);
+            const dateTime = frameWallClock(instant, frame);
             return dateTime.toPlainTime().toString();
         }
         catch {

package/dist/utc/parse/parseUnitFromUtc.d.ts

@@ -8,7 +8,7 @@ import { Temporal } from "@js-temporal/polyfill";
  *
  * | Member | Description |
  * | --- | --- |
- * | `year` | Full year, no padding (e.g. `2024`). |
+ * | `year` | Four digits (e.g. `2024`, `0005`); a sign and six digits outside 0000–9999 (e.g. `+010000`). |
  * | `month` | Zero-padded 2 (e.g. `03`). |
  * | `week` | Week-of-year, 1–53 (`weekStartsOn`-controlled). |
  * | `day` | Zero-padded 2. |
@@ -34,6 +34,8 @@ export type UtcUnit = Temporal.SmallestUnit<"year" | "month" | "week" | "day" |
  * - A `"week"` in late December can be week 1 of the next year, under either week numbering.
  * - `optionsArg` must be an object or omitted: a non-object value (such as `null`) returns "".
  * - Returns "" for invalid input.
+ * - The `"year"` unit is written as Temporal writes a year: four digits (`"2024"`, `"0005"`), or a
+ *   sign and six digits outside 0000–9999 (`"+010000"`, `"-000005"`).
  *
  * @param value ISO UTC datetime string (e.g., "2024-03-17T14:30:45Z")
  * @param unit unit to extract from the datetime
@@ -42,10 +44,13 @@ export type UtcUnit = Temporal.SmallestUnit<"year" | "month" | "week" | "day" |
  *
  * @example parseUnitFromUtc("2024-03-17T14:30:45Z", "month") // "03"
  * @example parseUnitFromUtc("2024-03-17T14:30:45Z", "hours") // "14"
+ * @example parseUnitFromUtc("2024-03-17T14:30:45Z", "year") // "2024"
+ * @example parseUnitFromUtc("0005-06-01T12:30:00Z", "year") // "0005"
  * @example parseUnitFromUtc("2024-03-17T02:30:45Z", "day", { timeZone: "America/New_York" }) // "16"
  * @example parseUnitFromUtc("2024-01-01T00:00:00Z", "week") // "1"
  * @example parseUnitFromUtc("2024-12-31T12:00:00Z", "week", { weekStartsOn: "sunday" }) // "1"
  * @example parseUnitFromUtc("invalid", "month") // ""
+ * @example parseUnitFromUtc("1970-01-01T12:44:30Z", "minute", { timeZone: "-00:44:30" }) // "00" (a stored offset with seconds)
  */
 export declare function parseUnitFromUtc(value: string, unit: UtcUnit, optionsArg?: {
     /**
@@ -58,8 +63,10 @@ export declare function parseUnitFromUtc(value: string, unit: UtcUnit, optionsAr
      */
     weekStartsOn?: "monday" | "sunday";
     /**
-     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `""`.
+     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `""`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/utc/parse/parseUnitFromUtc.js

@@ -1,11 +1,12 @@
 // fallow-ignore-file code-duplication -- cross-family Temporal type clone, by design (rule 5)
 import { Temporal } from "@js-temporal/polyfill";
 import { resolveDateTimeUnit } from "../../internal/resolveDateTimeUnit.js";
-import { normalizeTimeZone } from "../../internal/normalizeTimeZone.js";
+import { frameWallClock, normalizeZoneFrame } from "../../internal/zoneFrame.js";
 import { resolveWeekStartsOn } from "../../internal/resolveWeekStartsOn.js";
 import { getWeekNumber } from "../../plain/calculate/getWeekNumber.js";
 import { isValidUtc } from "../validate/index.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
+import { isoYearString } from "../../internal/isoYearString.js";
 /**
  * Extract a unit from a UTC datetime string.
  *
@@ -15,6 +16,8 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  * - A `"week"` in late December can be week 1 of the next year, under either week numbering.
  * - `optionsArg` must be an object or omitted: a non-object value (such as `null`) returns "".
  * - Returns "" for invalid input.
+ * - The `"year"` unit is written as Temporal writes a year: four digits (`"2024"`, `"0005"`), or a
+ *   sign and six digits outside 0000–9999 (`"+010000"`, `"-000005"`).
  *
  * @param value ISO UTC datetime string (e.g., "2024-03-17T14:30:45Z")
  * @param unit unit to extract from the datetime
@@ -23,10 +26,13 @@ import { isOptionsArgument } from "../../internal/isObject.js";
  *
  * @example parseUnitFromUtc("2024-03-17T14:30:45Z", "month") // "03"
  * @example parseUnitFromUtc("2024-03-17T14:30:45Z", "hours") // "14"
+ * @example parseUnitFromUtc("2024-03-17T14:30:45Z", "year") // "2024"
+ * @example parseUnitFromUtc("0005-06-01T12:30:00Z", "year") // "0005"
  * @example parseUnitFromUtc("2024-03-17T02:30:45Z", "day", { timeZone: "America/New_York" }) // "16"
  * @example parseUnitFromUtc("2024-01-01T00:00:00Z", "week") // "1"
  * @example parseUnitFromUtc("2024-12-31T12:00:00Z", "week", { weekStartsOn: "sunday" }) // "1"
  * @example parseUnitFromUtc("invalid", "month") // ""
+ * @example parseUnitFromUtc("1970-01-01T12:44:30Z", "minute", { timeZone: "-00:44:30" }) // "00" (a stored offset with seconds)
  */
 export function parseUnitFromUtc(value, unit, optionsArg) {
     try {
@@ -35,15 +41,15 @@ export function parseUnitFromUtc(value, unit, optionsArg) {
             return "";
         }
         const weekStartsOn = resolveWeekStartsOn(optionsArg?.weekStartsOn);
-        const timeZone = normalizeTimeZone(optionsArg?.timeZone);
-        if (!isValidUtc(value) || weekStartsOn === null || timeZone === "") {
+        const frame = normalizeZoneFrame(optionsArg?.timeZone);
+        if (!isValidUtc(value) || weekStartsOn === null || frame === null) {
             return "";
         }
         try {
-            const dateTime = Temporal.Instant.from(value).toZonedDateTimeISO(timeZone);
+            const dateTime = frameWallClock(Temporal.Instant.from(value), frame);
             switch (resolveDateTimeUnit(unit)) {
                 case "year":
-                    return dateTime.year.toString();
+                    return isoYearString(dateTime.year);
                 case "month":
                     return dateTime.month.toString().padStart(2, "0");
                 case "week":

package/dist/utc/parse/parseWeekFromUtc.d.ts

@@ -28,8 +28,10 @@ export declare function parseWeekFromUtc(value: string, optionsArg?: {
      */
     weekStartsOn?: "monday" | "sunday";
     /**
-     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `null`.
+     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `null`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/utc/parse/parseWeekFromUtc.js

@@ -1,5 +1,5 @@
 import { Temporal } from "@js-temporal/polyfill";
-import { normalizeTimeZone } from "../../internal/normalizeTimeZone.js";
+import { frameWallClock, normalizeZoneFrame } from "../../internal/zoneFrame.js";
 import { resolveWeekStartsOn } from "../../internal/resolveWeekStartsOn.js";
 import { getWeekNumber } from "../../plain/calculate/getWeekNumber.js";
 import { isValidUtc } from "../validate/index.js";
@@ -31,12 +31,12 @@ export function parseWeekFromUtc(value, optionsArg) {
         if (!isValidUtc(value))
             return null;
         const weekStartsOn = resolveWeekStartsOn(optionsArg?.weekStartsOn);
-        const timeZone = normalizeTimeZone(optionsArg?.timeZone);
-        if (weekStartsOn === null || timeZone === "")
+        const frame = normalizeZoneFrame(optionsArg?.timeZone);
+        if (weekStartsOn === null || frame === null)
             return null;
         try {
             const instant = Temporal.Instant.from(value);
-            const dt = instant.toZonedDateTimeISO(timeZone);
+            const dt = frameWallClock(instant, frame);
             const dateStr = dt.toPlainDate().toString();
             return getWeekNumber(dateStr, weekStartsOn);
         }

package/dist/utc/parse/parseYearFromUtc.d.ts

@@ -1,21 +1,25 @@
 /**
  * Return the year from a UTC datetime string.
  *
- * - Returns the year as a string (e.g., "2024").
+ * - Returns the year as Temporal writes it: four digits (`"2024"`, `"0005"`), or a sign and six
+ *   digits outside 0000–9999 (`"+010000"`, `"-000005"`).
  * - Returns "" for invalid input.
  *
  * @param value ISO UTC datetime string (e.g., "2024-03-17T14:30:45Z")
  * @param options The time zone the value is read in
- * @returns Year (YYYY) or "" on invalid input
+ * @returns the year as four digits, or a sign and six digits outside 0000–9999, or "" on invalid input
  *
  * @example parseYearFromUtc("2024-03-17T14:30:45Z") // "2024"
+ * @example parseYearFromUtc("0005-06-01T12:30:00Z") // "0005"
  * @example parseYearFromUtc("2025-01-01T02:00:00Z", { timeZone: "America/New_York" }) // "2024"
  * @example parseYearFromUtc("invalid") // ""
  */
 export declare function parseYearFromUtc(value: string, options?: {
     /**
-     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset, or `"local"` for
-     * the system time zone. An unknown zone returns `""`.
+     * The time zone the wall-clock fields are read in: an IANA name, a UTC offset (a time zone
+     * identifier such as `+05:30`, `+0530` or `-08`, or a stored offset `±HH:MM[:SS]`, what
+     * `getTimeZoneOffset` returns), or `"local"` for the system time zone. An unknown zone returns
+     * `""`.
      *
      * @defaultValue `"UTC"`
      */

package/dist/utc/parse/parseYearFromUtc.js

@@ -1,16 +1,19 @@
-import { utcZonedDateTime } from "../../internal/utcZonedDateTime.js";
+import { utcWallClock } from "../../internal/utcWallClock.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
+import { isoYearString } from "../../internal/isoYearString.js";
 /**
  * Return the year from a UTC datetime string.
  *
- * - Returns the year as a string (e.g., "2024").
+ * - Returns the year as Temporal writes it: four digits (`"2024"`, `"0005"`), or a sign and six
+ *   digits outside 0000–9999 (`"+010000"`, `"-000005"`).
  * - Returns "" for invalid input.
  *
  * @param value ISO UTC datetime string (e.g., "2024-03-17T14:30:45Z")
  * @param options The time zone the value is read in
- * @returns Year (YYYY) or "" on invalid input
+ * @returns the year as four digits, or a sign and six digits outside 0000–9999, or "" on invalid input
  *
  * @example parseYearFromUtc("2024-03-17T14:30:45Z") // "2024"
+ * @example parseYearFromUtc("0005-06-01T12:30:00Z") // "0005"
  * @example parseYearFromUtc("2025-01-01T02:00:00Z", { timeZone: "America/New_York" }) // "2024"
  * @example parseYearFromUtc("invalid") // ""
  */
@@ -19,8 +22,8 @@ export function parseYearFromUtc(value, options) {
         if (!isOptionsArgument(options)) {
             return "";
         }
-        const dateTime = utcZonedDateTime(value, options);
-        return dateTime === null ? "" : dateTime.year.toString();
+        const dateTime = utcWallClock(value, options);
+        return dateTime === null ? "" : isoYearString(dateTime.year);
     }
     catch {
         // Never throws (Core Rule 3): a hostile

package/dist/utc/validate/index.d.ts

@@ -1,2 +1,4 @@
+export * from "./isValidHttpDate.js";
 export * from "./isValidUtc.js";
 export * from "./isValidUtcRange.js";
+export * from "./isValidUtcTimestamp.js";

package/dist/utc/validate/index.js

@@ -1,2 +1,4 @@
+export * from "./isValidHttpDate.js";
 export * from "./isValidUtc.js";
 export * from "./isValidUtcRange.js";
+export * from "./isValidUtcTimestamp.js";

package/dist/utc/validate/isValidHttpDate.d.ts

@@ -0,0 +1,35 @@
+/**
+ * Return true when `value` is a real HTTP header date: the RFC 9110 §5.6.7 HTTP-date that
+ * headers like `Last-Modified`, `Date` and `Expires` carry, such as
+ * `Fri, 15 Mar 2024 14:30:00 GMT`.
+ *
+ * - True exactly when `parseHttpDate` returns a UTC string for the same value: the validator
+ *   calls the parser, so the two cannot disagree.
+ * - **All three HTTP-date formats**, which RFC 9110 §5.6.7 says a recipient "MUST accept":
+ *   IMF-fixdate, and the obsolete rfc850-date (`Sunday, 06-Nov-94 08:49:37 GMT`) and asctime-date
+ *   (`Sun Nov  6 08:49:37 1994`). The `httpDate` pattern matches IMF-fixdate alone.
+ * - Checks the calendar as well as the shape. The pattern matches a day that does not exist:
+ *   `31 Feb`, `29 Feb 2023` and `31 Jun` are false here.
+ * - **The day name must match the date, in all three formats.** The pattern does not check it.
+ * - False for an hour above 23 and a minute above 59, which the pattern matches. False for a
+ *   second of 60: GMT rejects leap seconds.
+ * - HTTP-date is case-sensitive and fixed-width, and its zone is the literal `GMT`: a numeric
+ *   offset is false.
+ * - **An rfc850-date reads the clock.** Its two-digit year is read against the current instant
+ *   (`Temporal.Now.instant()`), as `parseHttpDate` describes, so the same string can change its
+ *   answer decades apart; if the clock cannot be read the answer is false. The other two formats
+ *   never read the clock.
+ * - False for a non-string. Read the value with `parseHttpDate`; write one with `formatHttpDate`.
+ *
+ * @param value candidate RFC 9110 HTTP-date string
+ * @returns boolean indicating validity
+ *
+ * @example isValidHttpDate("Fri, 15 Mar 2024 14:30:00 GMT") // true
+ * @example isValidHttpDate("Sun Nov  6 08:49:37 1994") // true (asctime-date; the httpDate pattern does not match it)
+ * @example isValidHttpDate("Sat, 15 Mar 2024 14:30:00 GMT") // false (15 Mar 2024 was a Friday; the httpDate pattern matches it)
+ * @example isValidHttpDate("Wed, 29 Feb 2023 14:30:00 GMT") // false (2023 has no 29 February; the httpDate pattern matches it)
+ * @example isValidHttpDate("Fri, 15 Mar 2024 24:00:00 GMT") // false (hour 24; the httpDate pattern matches it)
+ * @example isValidHttpDate("Fri, 15 Mar 2024 14:30:00 -0400") // false (not an HTTP-date)
+ * @example isValidHttpDate("not a date") // false
+ */
+export declare function isValidHttpDate(value: string): boolean;

package/dist/utc/validate/isValidHttpDate.js

@@ -0,0 +1,38 @@
+import { parseHttpDate } from "../parse/parseHttpDate.js";
+/**
+ * Return true when `value` is a real HTTP header date: the RFC 9110 §5.6.7 HTTP-date that
+ * headers like `Last-Modified`, `Date` and `Expires` carry, such as
+ * `Fri, 15 Mar 2024 14:30:00 GMT`.
+ *
+ * - True exactly when `parseHttpDate` returns a UTC string for the same value: the validator
+ *   calls the parser, so the two cannot disagree.
+ * - **All three HTTP-date formats**, which RFC 9110 §5.6.7 says a recipient "MUST accept":
+ *   IMF-fixdate, and the obsolete rfc850-date (`Sunday, 06-Nov-94 08:49:37 GMT`) and asctime-date
+ *   (`Sun Nov  6 08:49:37 1994`). The `httpDate` pattern matches IMF-fixdate alone.
+ * - Checks the calendar as well as the shape. The pattern matches a day that does not exist:
+ *   `31 Feb`, `29 Feb 2023` and `31 Jun` are false here.
+ * - **The day name must match the date, in all three formats.** The pattern does not check it.
+ * - False for an hour above 23 and a minute above 59, which the pattern matches. False for a
+ *   second of 60: GMT rejects leap seconds.
+ * - HTTP-date is case-sensitive and fixed-width, and its zone is the literal `GMT`: a numeric
+ *   offset is false.
+ * - **An rfc850-date reads the clock.** Its two-digit year is read against the current instant
+ *   (`Temporal.Now.instant()`), as `parseHttpDate` describes, so the same string can change its
+ *   answer decades apart; if the clock cannot be read the answer is false. The other two formats
+ *   never read the clock.
+ * - False for a non-string. Read the value with `parseHttpDate`; write one with `formatHttpDate`.
+ *
+ * @param value candidate RFC 9110 HTTP-date string
+ * @returns boolean indicating validity
+ *
+ * @example isValidHttpDate("Fri, 15 Mar 2024 14:30:00 GMT") // true
+ * @example isValidHttpDate("Sun Nov  6 08:49:37 1994") // true (asctime-date; the httpDate pattern does not match it)
+ * @example isValidHttpDate("Sat, 15 Mar 2024 14:30:00 GMT") // false (15 Mar 2024 was a Friday; the httpDate pattern matches it)
+ * @example isValidHttpDate("Wed, 29 Feb 2023 14:30:00 GMT") // false (2023 has no 29 February; the httpDate pattern matches it)
+ * @example isValidHttpDate("Fri, 15 Mar 2024 24:00:00 GMT") // false (hour 24; the httpDate pattern matches it)
+ * @example isValidHttpDate("Fri, 15 Mar 2024 14:30:00 -0400") // false (not an HTTP-date)
+ * @example isValidHttpDate("not a date") // false
+ */
+export function isValidHttpDate(value) {
+    return parseHttpDate(value) !== "";
+}

package/dist/utc/validate/isValidUtc.d.ts

@@ -6,6 +6,10 @@
  * - Reads RFC 9557 annotations as `Temporal.Instant.from` does: elective ones (`[foo=bar]`), a
  *   time zone annotation and a calendar annotation are ignored (an instant has neither), and an
  *   unknown critical one (`[!foo=bar]`) is rejected.
+ * - Accepts four forms beyond the timestamp shape `YYYY-MM-DDTHH:MM:SS[.f]Z`: a time without
+ *   seconds, a comma before the fraction, an expanded `±YYYYYY` year and RFC 9557 annotations.
+ *   For the plain RFC 3339 spelling that readers other than Temporal expect, use
+ *   `isValidUtcTimestamp`, which is false for all four.
  * - Rejects leap seconds (e.g., "2024-12-31T23:59:60Z").
  * - Uses Temporal.Instant.from for validation.
  * - Requires a time component — date-only strings ("2024-01-01Z") are rejected.

package/dist/utc/validate/isValidUtc.js

@@ -10,6 +10,10 @@ import { utcDateTime } from "../../regex/utc-date-time.js";
  * - Reads RFC 9557 annotations as `Temporal.Instant.from` does: elective ones (`[foo=bar]`), a
  *   time zone annotation and a calendar annotation are ignored (an instant has neither), and an
  *   unknown critical one (`[!foo=bar]`) is rejected.
+ * - Accepts four forms beyond the timestamp shape `YYYY-MM-DDTHH:MM:SS[.f]Z`: a time without
+ *   seconds, a comma before the fraction, an expanded `±YYYYYY` year and RFC 9557 annotations.
+ *   For the plain RFC 3339 spelling that readers other than Temporal expect, use
+ *   `isValidUtcTimestamp`, which is false for all four.
  * - Rejects leap seconds (e.g., "2024-12-31T23:59:60Z").
  * - Uses Temporal.Instant.from for validation.
  * - Requires a time component — date-only strings ("2024-01-01Z") are rejected.

package/dist/utc/validate/isValidUtcTimestamp.d.ts

@@ -0,0 +1,43 @@
+/**
+ * Return true when `value` is a real UTC instant written as `YYYY-MM-DDTHH:MM:SS[.f]Z` and
+ * nothing else: a narrower check than `isValidUtc`.
+ *
+ * - The shape is one spelling of the RFC 3339 §5.6 `date-time`: a four-digit year, `0000` to
+ *   `9999` (`date-fullyear = 4DIGIT`), an upper-case `T`, a time with seconds, an optional
+ *   fraction of one to nine digits after a dot (`time-secfrac = "." 1*DIGIT`; GMT stops at nine
+ *   because Temporal keeps nanoseconds), and an upper-case `Z` with nothing after it.
+ * - Use it for a string headed for storage, or for a reader that is not Temporal: the shape is
+ *   plain RFC 3339, and the one `Temporal.Instant.prototype.toString()`, called with no options,
+ *   writes for years `0000` to `9999`.
+ * - Use `isValidUtc` when Temporal is the only reader. It also accepts a time without seconds, a
+ *   comma before the fraction, an expanded `±YYYYYY` year and RFC 9557 annotations; all four are
+ *   false here.
+ * - A subset of `isValidUtc`: every string that is true here is true there. The instant is
+ *   checked as well as the shape, so a day that does not exist is false.
+ * - False for the other spellings §5.6 allows: a lower-case `t` or `z`, a space for `T` (its
+ *   NOTE), and a numeric offset, `+00:00` included. `isValidRfc3339DateTime` checks the whole
+ *   grammar, with the same two GMT limits.
+ * - False for a leap second (`:60`), although §5.6 `time-second` admits it: GMT rejects leap
+ *   seconds because Temporal would read one as `:59`.
+ * - Not one canonical spelling: `12:00:00Z` and `12:00:00.000Z` are one instant and both are
+ *   true. A reader may still refuse or round a string that is true here: PostgreSQL has no year
+ *   `0000` and keeps microseconds. See `toPgMicroseconds` and `precision/`.
+ * - False for a non-string.
+ *
+ * @param value candidate UTC timestamp string
+ * @returns true when `value` is a real UTC instant in this shape, or false on invalid input
+ *
+ * @example isValidUtcTimestamp("2026-10-06T12:00:00Z") // true
+ * @example isValidUtcTimestamp("2026-10-06T12:00:00.123456789Z") // true (nine fraction digits)
+ * @example isValidUtcTimestamp("0000-01-01T00:00:00Z") // true (year 0000)
+ * @example isValidUtcTimestamp("2026-10-06T12:00:00Z[Europe/Paris]") // false (RFC 9557 annotation; isValidUtc accepts it)
+ * @example isValidUtcTimestamp("2026-10-06T12:00:00,5Z") // false (comma before the fraction; isValidUtc accepts it)
+ * @example isValidUtcTimestamp("-005000-01-01T00:00:00Z") // false (expanded year; isValidUtc accepts it)
+ * @example isValidUtcTimestamp("2026-10-06T12:00Z") // false (no seconds; isValidUtc accepts it)
+ * @example isValidUtcTimestamp("2026-10-06t12:00:00z") // false (lower-case t and z)
+ * @example isValidUtcTimestamp("2026-10-06T12:00:00+00:00") // false (a numeric offset, not Z)
+ * @example isValidUtcTimestamp("2026-02-30T00:00:00Z") // false (February has no 30th; the rfc3339DateTime pattern matches it)
+ * @example isValidUtcTimestamp("2016-12-31T23:59:60Z") // false (leap second)
+ * @example isValidUtcTimestamp("not a date") // false
+ */
+export declare function isValidUtcTimestamp(value: string): boolean;

package/dist/utc/validate/isValidUtcTimestamp.js

@@ -0,0 +1,48 @@
+import { rfc3339DateTime } from "../../regex/rfc-3339.js";
+import { isValidUtc } from "./isValidUtc.js";
+/**
+ * Return true when `value` is a real UTC instant written as `YYYY-MM-DDTHH:MM:SS[.f]Z` and
+ * nothing else: a narrower check than `isValidUtc`.
+ *
+ * - The shape is one spelling of the RFC 3339 §5.6 `date-time`: a four-digit year, `0000` to
+ *   `9999` (`date-fullyear = 4DIGIT`), an upper-case `T`, a time with seconds, an optional
+ *   fraction of one to nine digits after a dot (`time-secfrac = "." 1*DIGIT`; GMT stops at nine
+ *   because Temporal keeps nanoseconds), and an upper-case `Z` with nothing after it.
+ * - Use it for a string headed for storage, or for a reader that is not Temporal: the shape is
+ *   plain RFC 3339, and the one `Temporal.Instant.prototype.toString()`, called with no options,
+ *   writes for years `0000` to `9999`.
+ * - Use `isValidUtc` when Temporal is the only reader. It also accepts a time without seconds, a
+ *   comma before the fraction, an expanded `±YYYYYY` year and RFC 9557 annotations; all four are
+ *   false here.
+ * - A subset of `isValidUtc`: every string that is true here is true there. The instant is
+ *   checked as well as the shape, so a day that does not exist is false.
+ * - False for the other spellings §5.6 allows: a lower-case `t` or `z`, a space for `T` (its
+ *   NOTE), and a numeric offset, `+00:00` included. `isValidRfc3339DateTime` checks the whole
+ *   grammar, with the same two GMT limits.
+ * - False for a leap second (`:60`), although §5.6 `time-second` admits it: GMT rejects leap
+ *   seconds because Temporal would read one as `:59`.
+ * - Not one canonical spelling: `12:00:00Z` and `12:00:00.000Z` are one instant and both are
+ *   true. A reader may still refuse or round a string that is true here: PostgreSQL has no year
+ *   `0000` and keeps microseconds. See `toPgMicroseconds` and `precision/`.
+ * - False for a non-string.
+ *
+ * @param value candidate UTC timestamp string
+ * @returns true when `value` is a real UTC instant in this shape, or false on invalid input
+ *
+ * @example isValidUtcTimestamp("2026-10-06T12:00:00Z") // true
+ * @example isValidUtcTimestamp("2026-10-06T12:00:00.123456789Z") // true (nine fraction digits)
+ * @example isValidUtcTimestamp("0000-01-01T00:00:00Z") // true (year 0000)
+ * @example isValidUtcTimestamp("2026-10-06T12:00:00Z[Europe/Paris]") // false (RFC 9557 annotation; isValidUtc accepts it)
+ * @example isValidUtcTimestamp("2026-10-06T12:00:00,5Z") // false (comma before the fraction; isValidUtc accepts it)
+ * @example isValidUtcTimestamp("-005000-01-01T00:00:00Z") // false (expanded year; isValidUtc accepts it)
+ * @example isValidUtcTimestamp("2026-10-06T12:00Z") // false (no seconds; isValidUtc accepts it)
+ * @example isValidUtcTimestamp("2026-10-06t12:00:00z") // false (lower-case t and z)
+ * @example isValidUtcTimestamp("2026-10-06T12:00:00+00:00") // false (a numeric offset, not Z)
+ * @example isValidUtcTimestamp("2026-02-30T00:00:00Z") // false (February has no 30th; the rfc3339DateTime pattern matches it)
+ * @example isValidUtcTimestamp("2016-12-31T23:59:60Z") // false (leap second)
+ * @example isValidUtcTimestamp("not a date") // false
+ */
+export function isValidUtcTimestamp(value) {
+    // `isValidUtc` goes first: it stops a non-string before the pattern would read it as text.
+    return isValidUtc(value) && rfc3339DateTime.test(value);
+}

package/dist/zoned/calculate/addZoned.js

@@ -1,5 +1,5 @@
 // fallow-ignore-file code-duplication -- sibling variant keeps its own guard, parse and try/catch, by design
-import { addToZonedDisambiguated, calendarSystemOfZonedValue, formatZonedInCalendar, isValidAmount, parseCalendarZonedValue, resolveOverflow, } from "../../internal/index.js";
+import { addToZonedDisambiguated, calendarSystemOfZonedValue, formatZonedInCalendar, parseCalendarZonedValue, readDurationUnits, resolveOverflow, } from "../../internal/index.js";
 import { isValidDateTimeDurationUnit } from "../../plain/validate/index.js";
 import { isValidCalendarZonedDateTime } from "../validate/index.js";
 import { isOptionsArgument } from "../../internal/isObject.js";
@@ -62,11 +62,8 @@ export function addZoned(value, units, optionsArg) {
             return "";
         }
         const validZonedDateTime = isValidCalendarZonedDateTime(value);
-        const validUnits = typeof units === "object" &&
-            units !== null &&
-            Object.keys(units).every(isValidDateTimeDurationUnit);
-        const validAmounts = validUnits && Object.values(units).every(isValidAmount);
-        if (!validZonedDateTime || !validUnits || !validAmounts) {
+        const amounts = readDurationUnits(units, isValidDateTimeDurationUnit);
+        if (!validZonedDateTime || amounts === null) {
             // TODO descriptive messages of what failed - likely could be GMT offset for historical changes and DST
             return "";
         }
@@ -78,7 +75,7 @@ export function addZoned(value, units, optionsArg) {
                 return "";
             }
             const zoned = parseCalendarZonedValue(value);
-            const added = addToZonedDisambiguated(zoned, units, 1, {
+            const added = addToZonedDisambiguated(zoned, amounts, 1, {
                 overflow,
                 disambiguation,
             });