@xema/omni-protocol 0.1.47 → 0.1.49

package/dist/testing.js

@@ -1,5 +1,5 @@
 import { browserSessionKey, effectiveLevels, sameCapabilities, } from "./index.js";
-import { assertNoViolations, validateAuthenticationState, validateEventEnvelope, validateHostGuarantees, validateHostReport, validateManifest, validateResult, validateSnapshot, validateTimeZone, validatePhone, isTimeZone, } from "./validation.js";
+import { assertNoViolations, validateAuthenticationState, validateEventEnvelope, validateHostGuarantees, validateHostReport, validateManifest, validateResult, validateSnapshot, validateTimeZone, validatePhone, isTimeZone, sameTimeZone, } from "./validation.js";
 export { ProtocolConformanceError, assertNoViolations } from "./validation.js";
 /**
  * A part of the contract a run may never reach: state nothing obliges an adapter to publish, so
@@ -342,7 +342,9 @@ export async function exerciseAdapter(adapter, context, options = {}) {
         // The provider republishes the agent's day: once connected, the identity carries the zone the
         // host sent. That proves the round trip, not the store -- an echo passes it -- and the name
         // says only what it tests; storage is proved by a colleague's zone arriving from describeUsers().
-        if (isTimeZone(context.timeZone) && current().identity.timeZone !== context.timeZone) {
+        // A zone is judged by what it denotes: Asia/Kolkata and Asia/Calcutta are one zone, and a
+        // provider that keeps the canonical name has kept the zone.
+        if (isTimeZone(context.timeZone) && !sameTimeZone(current().identity.timeZone, context.timeZone)) {
             violations.push({
                 rule: "authentication.identity.timeZone.republished",
                 path: "authentication.identity.timeZone",

package/dist/validation.d.ts

@@ -74,6 +74,8 @@ export type ResultMethod = "execute" | "dial" | "setCapacity" | "requestBreak" |
 export declare function validateResult(result: unknown, method: ResultMethod, path?: string, dialId?: string): ProtocolViolation[];
 /** An IANA zone name the runtime knows: `Asia/Kolkata` is one, an offset or a made-up name is not. */
 export declare function isTimeZone(value: unknown): value is string;
+/** Whether two zone names denote one zone: `Asia/Kolkata` and `Asia/Calcutta` do, and a name is judged by what it denotes. */
+export declare function sameTimeZone(a: unknown, b: unknown): boolean;
 /** The zone a host sends at connect: required, and an IANA name. */
 export declare function validateTimeZone(value: unknown, path?: string): ProtocolViolation[];
 /** What a login is validated against beyond its own shape. */

package/dist/validation.js

@@ -1788,6 +1788,13 @@ export function isTimeZone(value) {
         return false;
     }
 }
+/** Whether two zone names denote one zone: `Asia/Kolkata` and `Asia/Calcutta` do, and a name is judged by what it denotes. */
+export function sameTimeZone(a, b) {
+    if (!isTimeZone(a) || !isTimeZone(b))
+        return false;
+    const canonical = (zone) => new Intl.DateTimeFormat("en", { timeZone: zone }).resolvedOptions().timeZone;
+    return a === b || canonical(a) === canonical(b);
+}
 /** The zone a host sends at connect: required, and an IANA name. */
 export function validateTimeZone(value, path = "context.timeZone") {
     const into = new Collector();

package/guide.md

@@ -1939,7 +1939,9 @@ field to fill in later: an identity without one is refused (`authentication.iden
 so is a zone that is not an IANA name, wherever it appears. Nothing is ever assumed in its place --
 not the viewer's browser, which gives a different answer per reader for the same record, and not the
 provider's clock. The harness holds a provider to the round trip: the identity carries the zone the
-host stated (`authentication.identity.timeZone.republished`). **The round trip is not the store.**
+host stated (`authentication.identity.timeZone.republished`), judged by what the name denotes:
+`Asia/Kolkata` and `Asia/Calcutta` are one zone, and a provider that keeps the canonical name has
+kept the zone. **The round trip is not the store.**
 An adapter that echoes the stated zone back onto the identity passes that check with nothing kept,
 and a lead reading a colleague's day would still get the wrong one. What proves the store is a zone
 the run never sent: a colleague's `User` from `describeUsers()` carrying theirs. A provider's own

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xema/omni-protocol",
-  "version": "0.1.47",
+  "version": "0.1.49",
   "description": "The Omni protocol: the contract every provider adapter implements",
   "type": "module",
   "license": "MIT",