@checkstack/ai-frontend 0.1.4 → 0.1.6

package/CHANGELOG.md

@@ -1,5 +1,74 @@
 # @checkstack/ai-frontend
 
+## 0.1.6
+
+### Patch Changes
+
+- Updated dependencies [56e7c75]
+- Updated dependencies [56e7c75]
+  - @checkstack/frontend-api@0.9.0
+  - @checkstack/ui@1.15.1
+  - @checkstack/common@0.15.0
+  - @checkstack/ai-common@0.1.3
+  - @checkstack/integration-common@0.7.3
+
+## 0.1.5
+
+### Patch Changes
+
+- b50916d: Fix "Date cannot be represented in JSON Schema" crashing the AI chat. Zod v4's
+  `toJSONSchema()` throws on `z.date()` (and even `z.coerce.date()`) by default,
+  and the chat hit this in TWO places:
+
+  - **`@checkstack/backend-api`** `toJsonSchema()` (the OpenAPI generator and AI
+    tool-introspection / MCP substrate) called it with no options.
+  - **`@checkstack/ai-backend`** the agent loop hands the Vercel AI SDK the raw
+    Zod tool input, and the SDK runs its OWN `toJSONSchema()` (throwing) to build
+    the model-facing tool schema - so a single date field in any tool input
+    crashed every chat turn (the whole tool list is projected before the model is
+    called).
+
+  Both now render dates as `{ type: "string", format: "date-time" }` (their wire
+  shape) and degrade other unrepresentable types to `{}` instead of throwing.
+
+  For the model boundary, a single `dateSafeModelSchema()` helper hands the SDK a
+  ready-made date-safe schema plus a validator that COERCES the ISO strings the
+  model emits back into real `Date`s before parsing with the original schema
+  (refinements and the downstream RPC client, which expects `Date`s, keep
+  working). A single `toModelSchema()` entry point applies this at EVERY point a
+  schema is handed to the model - chat tool inputs, the headless agent runner's
+  tool inputs (the automation "AI Action"), and `generateObject` structured
+  output - gated so non-date schemas are untouched, so individual tool / agent
+  definitions never special-case dates. Regression tests cover the converter, the
+  AI tool serializer, and the model-schema generation + coercion helper, including
+  the full inbound round-trip with the exact ISO shape a live model emits
+  (`...T22:00:00Z`, no milliseconds).
+
+  **Timezone correctness.** Because the model produces dates as text, the chat now
+  enforces an unambiguous wire contract: a date-time tool argument MUST be RFC 3339
+  with an explicit timezone offset. Zone-less (`2026-07-01T22:00:00`) and date-only
+  (`2026-07-01`) values are rejected with a model-readable error (the model
+  self-repairs), instead of being silently interpreted in the pod's local zone -
+  which would resolve the same string to different instants across pods. To resolve
+  an operator's bare "22:00", the browser's IANA timezone is sent with every chat
+  turn and folded into the system prompt, so each operator's times are interpreted
+  in their own zone by default. When no browser zone is available (a headless
+  automation AI Action), the reference zone falls back to the host/container
+  timezone (`TZ`), not UTC. A format-matrix test covers every common shape a model
+  might emit. The chat UI shows the operator which timezone is in use, and the
+  `TZ` override is documented for operators.
+
+  **Current time in context.** The model has no clock, so the system prompt now
+  includes the current instant (UTC plus the reference-zone wall clock), letting it
+  resolve relative dates like "today at 10:00" without asking. Applied to both the
+  chat and the headless agent runner, computed per turn/run so it is never stale.
+
+  **Less-strict topic classifier.** The chat's off-topic pre-classifier was
+  refusing legitimate requests like "create a maintenance" because maintenances
+  (and several other domains) were not listed. The classifier now enumerates the
+  full domain set and treats any create/list/update/delete action on a platform
+  resource as on-topic by default.
+
 ## 0.1.4
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@checkstack/ai-frontend",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "license": "Elastic-2.0",
   "type": "module",
   "main": "src/index.tsx",
@@ -14,11 +14,11 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@checkstack/ai-common": "0.1.2",
-    "@checkstack/common": "0.14.1",
-    "@checkstack/frontend-api": "0.8.0",
-    "@checkstack/integration-common": "0.7.2",
-    "@checkstack/ui": "1.15.0",
+    "@checkstack/ai-common": "0.1.3",
+    "@checkstack/common": "0.15.0",
+    "@checkstack/frontend-api": "0.9.0",
+    "@checkstack/integration-common": "0.7.3",
+    "@checkstack/ui": "1.15.1",
     "lucide-react": "^1.17.0",
     "react": "19.2.7",
     "react-router-dom": "^7.16.0"
@@ -27,6 +27,6 @@
     "typescript": "^5.0.0",
     "@types/react": "^19.0.0",
     "@checkstack/tsconfig": "0.0.7",
-    "@checkstack/scripts": "0.6.0"
+    "@checkstack/scripts": "0.6.1"
   }
 }

package/src/lib/use-chat-turn.ts

@@ -18,6 +18,20 @@ function newId(): string {
     : `${Date.now()}-${Math.random().toString(36).slice(2)}`;
 }
 
+/**
+ * The operator's IANA timezone (e.g. "Europe/Berlin"), sent with every turn so
+ * the backend prompt can resolve bare times like "22:00" into the right offset.
+ * The browser is the authoritative source of the user's wall clock. Returns
+ * undefined where `Intl` is unavailable (the backend then falls back to UTC).
+ */
+function browserTimeZone(): string | undefined {
+  try {
+    return Intl.DateTimeFormat().resolvedOptions().timeZone || undefined;
+  } catch {
+    return undefined;
+  }
+}
+
 /**
  * React hook that drives ONE streaming chat turn against /api/ai/chat. The
  * heavy lifting (SSE parsing, state folding) lives in DOM-free, unit-tested
@@ -65,7 +79,9 @@ export function useChatTurn({
           .fetch("/chat", {
             method: "POST",
             headers: { "content-type": "application/json" },
-            body: JSON.stringify(body),
+            // Stamp the operator's timezone on every turn (user message AND
+            // confirm-card decision) so the model resolves bare times correctly.
+            body: JSON.stringify({ timeZone: browserTimeZone(), ...body }),
             signal: controller.signal,
           });
         if (!response.ok || !response.body) {

package/src/pages/ChatPage.tsx

@@ -206,6 +206,16 @@ export function ChatPage() {
   const [copiedError, setCopiedError] = useState(false);
   const bottomRef = useRef<HTMLDivElement>(null);
 
+  // The operator's browser timezone, surfaced as a hint and sent with each turn
+  // so the assistant resolves bare times ("22:00") in this zone by default.
+  const browserTimeZone = useMemo<string | undefined>(() => {
+    try {
+      return Intl.DateTimeFormat().resolvedOptions().timeZone;
+    } catch {
+      return;
+    }
+  }, []);
+
   const {
     messages,
     setMessages,
@@ -643,6 +653,12 @@ export function ChatPage() {
               <Send className="w-4 h-4" />
             </Button>
           </div>
+          {browserTimeZone ? (
+            <p className="px-2 pb-2 -mt-1 text-xs text-muted-foreground">
+              Times you mention are interpreted in your timezone (
+              {browserTimeZone}).
+            </p>
+          ) : null}
         </Card>
       </div>