@anchrd/intel-contract 0.7.0 → 0.8.0

package/dist/contract/contract.d.ts

@@ -1,6 +1,8 @@
 import { z } from "zod";
 export declare const IntelId: z.ZodString;
 export declare const IsoDateTime: z.ZodISODateTime;
+export declare const UI_LANGUAGES: readonly ["en", "de", "es"];
+export type UiLanguage = (typeof UI_LANGUAGES)[number];
 export declare const ProblemDetails: z.ZodObject<{
     type: z.ZodString;
     status: z.ZodNumber;
@@ -478,6 +480,7 @@ export declare const AgentScheduleTarget: z.ZodObject<{
 export type AgentScheduleTarget = z.infer<typeof AgentScheduleTarget>;
 export declare const AgentSchedule: z.ZodObject<{
     cron: z.ZodString;
+    timezone: z.ZodDefault<z.ZodString>;
     target: z.ZodObject<{
         kind: z.ZodEnum<{
             document: "document";
@@ -553,6 +556,7 @@ export declare const AgentDefinition: z.ZodObject<{
     }, z.core.$strict>>>;
     schedules: z.ZodDefault<z.ZodArray<z.ZodObject<{
         cron: z.ZodString;
+        timezone: z.ZodDefault<z.ZodString>;
         target: z.ZodObject<{
             kind: z.ZodEnum<{
                 document: "document";
@@ -595,6 +599,7 @@ export declare const AgentDefinitionInput: z.ZodObject<{
     }, z.core.$strict>>>;
     schedules: z.ZodDefault<z.ZodArray<z.ZodObject<{
         cron: z.ZodString;
+        timezone: z.ZodDefault<z.ZodString>;
         target: z.ZodObject<{
             kind: z.ZodEnum<{
                 document: "document";
@@ -629,6 +634,7 @@ export declare const SaveAgentDefinitionInput: z.ZodObject<{
         }, z.core.$strict>>>;
         schedules: z.ZodDefault<z.ZodArray<z.ZodObject<{
             cron: z.ZodString;
+            timezone: z.ZodDefault<z.ZodString>;
             target: z.ZodObject<{
                 kind: z.ZodEnum<{
                     document: "document";
@@ -690,6 +696,7 @@ export declare const CreateAgentInput: z.ZodObject<{
         }, z.core.$strict>>>;
         schedules: z.ZodDefault<z.ZodArray<z.ZodObject<{
             cron: z.ZodString;
+            timezone: z.ZodDefault<z.ZodString>;
             target: z.ZodObject<{
                 kind: z.ZodEnum<{
                     document: "document";
@@ -759,6 +766,7 @@ export declare const NodeAgent: z.ZodObject<{
         }, z.core.$strict>>>;
         schedules: z.ZodDefault<z.ZodArray<z.ZodObject<{
             cron: z.ZodString;
+            timezone: z.ZodDefault<z.ZodString>;
             target: z.ZodObject<{
                 kind: z.ZodEnum<{
                     document: "document";
@@ -842,6 +850,7 @@ export declare const CreatedAgent: z.ZodObject<{
         }, z.core.$strict>>>;
         schedules: z.ZodDefault<z.ZodArray<z.ZodObject<{
             cron: z.ZodString;
+            timezone: z.ZodDefault<z.ZodString>;
             target: z.ZodObject<{
                 kind: z.ZodEnum<{
                     document: "document";

package/dist/contract/contract.js

@@ -1,6 +1,14 @@
 import { z } from "zod";
 export const IntelId = z.string().min(1).max(128);
 export const IsoDateTime = z.iso.datetime({ offset: true });
+// The languages whose UI catalog ships inside intel-ui. They live here rather than only in the UI
+// because `intel build` has to know them: a built-in language may be chosen as `ui.defaultLanguage`
+// without the customer listing a copy under `ui.languages` that would rot at every UI update.
+//
+// ⚠️ The list is a claim about the contents of packages/ui/src/i18n and cannot be checked here.
+// `i18n.unit.ts` compares it against the catalogs actually built in; a language listed here without
+// a file gives a red run there instead of a UI that starts on a catalog which does not exist.
+export const UI_LANGUAGES = ["en", "de", "es"];
 export const ProblemDetails = z.strictObject({
     type: z.string(),
     status: z.number().int().min(400).max(599),
@@ -283,8 +291,42 @@ export const AgentScheduleTarget = z.strictObject({
     kind: z.enum(["document", "flow"]),
     id: IntelId,
 });
+/**
+ * ⚠️ `timezone` is what the cron expression is READ IN, and it belongs to the schedule rather than
+ * to whoever is looking at it (#228). "Every morning at eight" means eight o'clock where the person
+ * who wrote it sits — in Berlin that is 06:00 UTC in summer and 07:00 in winter, and a field that
+ * does not carry the zone cannot express that difference. A UTC cron is an hour wrong twice a year
+ * and nobody sees why.
+ *
+ * The UI suggests the reader's own zone when a schedule is created, but it is not a per-user
+ * setting: an agent's schedule would otherwise move whenever its owner travelled, and it would mean
+ * different times to two people reading the same definition. What is stored is the answer.
+ *
+ * ⚠️ The default is `"UTC"`, and it is load-bearing rather than tidy: every definition written
+ * before this field parses to it and therefore keeps firing exactly when it did. A default of
+ * "whatever the writer's browser says" would silently move every existing schedule at the next save.
+ *
+ * The name is validated against this runtime's own tz database rather than a pattern. A regular
+ * expression would accept `Mars/Olympus`, and the failure would surface inside a Durable Object
+ * alarm — the place where nobody is watching.
+ */
+const IanaTimezone = z
+    .string()
+    .trim()
+    .min(1)
+    .max(64)
+    .refine((zone) => {
+    try {
+        new Intl.DateTimeFormat("en-US", { timeZone: zone });
+        return true;
+    }
+    catch {
+        return false;
+    }
+}, { message: "must be an IANA timezone name this runtime knows, for example Europe/Berlin" });
 export const AgentSchedule = z.strictObject({
     cron: z.string().trim().min(1).max(120),
+    timezone: IanaTimezone.default("UTC"),
     target: AgentScheduleTarget,
 });
 export const AgentModel = z.strictObject({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anchrd/intel-contract",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "type": "module",
   "license": "UNLICENSED",
   "repository": {