@elevasis/sdk 1.41.0 → 1.41.1

package/dist/cli.cjs

@@ -45834,7 +45834,7 @@ function wrapAction(commandName, fn) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "1.41.0",
+  version: "1.41.1",
   description: "SDK for building Elevasis organization resources",
   type: "module",
   bin: {

package/dist/index.d.ts

@@ -502,6 +502,15 @@ interface ModelConfig {
     modelOptions?: ModelSpecificOptions;
 }
 
+/**
+ * What happened to `strict` on a request, recorded per call rather than inferred.
+ *
+ * `applied` and `notAttempted` are the two states that a refusal-only field cannot tell apart —
+ * both leave `strictRefusalReasons` empty. Recording the verdict positively is what makes "was
+ * this agent's output actually enforced?" answerable from an `ai_calls` row.
+ */
+type StrictStatus = 'applied' | 'refused' | 'compileRejected' | 'notAttempted';
+
 declare const ResourceGovernanceStatusSchema: z.ZodEnum<{
     active: "active";
     deprecated: "deprecated";
@@ -1029,6 +1038,7 @@ interface WorkflowDefinition {
  * Generic LLM Types
  * Universal interfaces for LLM interaction across all resource types
  */
+
 /**
  * Standard chat message format
  * Compatible with OpenAI, Anthropic, and other providers
@@ -1062,15 +1072,30 @@ interface LLMGenerateResponse<T = unknown> {
         totalTokens: number;
     };
     cost?: number;
+    /**
+     * What actually happened to `strict` on the request that produced this response. Every server
+     * adapter sets it on every call, so the value is a statement rather than an inference:
+     *
+     * - `applied` — the request carried `strict: true` and the grammar was in effect
+     * - `refused` — `toStrictSchema` could not express the schema, so the request went out unstrict
+     * - `compileRejected` — the schema passed `toStrictSchema` but the provider's grammar compiler
+     *   rejected it at request time, and the call was retried unstrict
+     * - `notAttempted` — this adapter does not send strict at all (OpenAI, Google, OpenRouter)
+     *
+     * This exists because `strictRefusalReasons` alone cannot answer the question. Its absence means
+     * "strict held" OR "nothing ever tried", and a prod run that recorded zero refusals while
+     * returning an array-typed field as a string is exactly the case where the difference matters.
+     *
+     * Internal-only, like `usage` — `UniversalLLMAdapter` lifts it onto the `ai_calls` row and
+     * strips it before the response reaches callers.
+     */
+    strictStatus?: StrictStatus;
     /**
      * Why this call went out WITHOUT `strict`, on an adapter that tried to send it with one.
      *
-     * Present only on a refusal, so absence means either "strict was in effect" or "this adapter
-     * does not attempt strict at all" — the two are distinguished by which adapter answered, not by
-     * this field. `toStrictSchema` already computes these reasons and, until now, nothing consumed
-     * them at the call site: an unstrict call was indistinguishable from a strict one anywhere
-     * outside a dev-only flow log. That invisibility is what let every tenant run unstrict against a
-     * strict-capable API for as long as it took someone to recognise a pre-strict error signature.
+     * The detail behind a `refused` / `compileRejected` `strictStatus` — the short, stable reason
+     * strings `toStrictSchema` computes. Read `strictStatus` to answer "was it enforced"; read this
+     * to answer "why not".
      *
      * Internal-only, like `usage` — `UniversalLLMAdapter` lifts it onto the `ai_calls` row and
      * strips it before the response reaches callers.
@@ -11248,15 +11273,24 @@ interface BaseAICall {
      */
     unvalidatedOutput?: string;
     /**
-     * Why this call went out without `strict` structured output, on an adapter that tried to send it
-     * with one. Present ONLY on a refusal — its absence on a row from a strict-capable adapter means
-     * strict was in effect.
+     * What happened to `strict` structured output on this call — `applied`, `refused`,
+     * `compileRejected`, or `notAttempted`. Every server adapter sets it, so this is the field that
+     * answers "is this agent's output actually being enforced?" without reading source.
      *
-     * This is the row that answers "is this agent's output actually being enforced?" without reading
-     * source. Counting rows that carry it, per resource, is the refusal count: a redeployed agent on
-     * a current bundle should read zero. It exists because the previous answer was a dev-only flow
-     * log, which meant production had no answer — and every sync-managed tenant ran unstrict against
-     * a strict-capable API until a 14-turn session surfaced a pre-strict error signature.
+     * It replaces an inference that turned out to be unsound. `strictRefusalReasons` alone records
+     * only refusals, so an empty row meant "strict held" OR "this adapter never tries" — and a prod
+     * run recorded zero refusals while a call returned an array-typed field as a string, which a
+     * grammar makes impossible. The absence proved nothing, because the deployed API had no way to
+     * write the field at all.
+     *
+     * Absent on rows written before this field existed; that absence is itself diagnostic (the API
+     * predates the change). Existing readers that only look at the fields above are unaffected.
+     */
+    strictStatus?: StrictStatus;
+    /**
+     * Why this call went out without `strict`, when a strict-capable adapter refused the schema. The
+     * detail behind `strictStatus: 'refused' | 'compileRejected'` — read `strictStatus` for whether
+     * it was enforced, this for why not.
      *
      * Existing readers that only look at the fields above are unaffected.
      */
@@ -11316,6 +11350,8 @@ interface LLMUsageData {
     outputValidationError?: string;
     /** Raw model output that failed validation — JSON-stringified, truncated, truncation marked inline */
     unvalidatedOutput?: string;
+    /** What happened to `strict` on this call — set by every server adapter, refusal or not */
+    strictStatus?: StrictStatus;
     /** Why the call went out unstrict, when a strict-capable adapter refused the schema */
     strictRefusalReasons?: string[];
 }

package/dist/node/index.d.ts

@@ -372,6 +372,15 @@ interface ModelConfig {
     modelOptions?: ModelSpecificOptions;
 }
 
+/**
+ * What happened to `strict` on a request, recorded per call rather than inferred.
+ *
+ * `applied` and `notAttempted` are the two states that a refusal-only field cannot tell apart —
+ * both leave `strictRefusalReasons` empty. Recording the verdict positively is what makes "was
+ * this agent's output actually enforced?" answerable from an `ai_calls` row.
+ */
+type StrictStatus = 'applied' | 'refused' | 'compileRejected' | 'notAttempted';
+
 declare const ResourceGovernanceStatusSchema: z.ZodEnum<{
     active: "active";
     deprecated: "deprecated";
@@ -899,6 +908,7 @@ interface WorkflowDefinition {
  * Generic LLM Types
  * Universal interfaces for LLM interaction across all resource types
  */
+
 /**
  * Standard chat message format
  * Compatible with OpenAI, Anthropic, and other providers
@@ -932,15 +942,30 @@ interface LLMGenerateResponse<T = unknown> {
         totalTokens: number;
     };
     cost?: number;
+    /**
+     * What actually happened to `strict` on the request that produced this response. Every server
+     * adapter sets it on every call, so the value is a statement rather than an inference:
+     *
+     * - `applied` — the request carried `strict: true` and the grammar was in effect
+     * - `refused` — `toStrictSchema` could not express the schema, so the request went out unstrict
+     * - `compileRejected` — the schema passed `toStrictSchema` but the provider's grammar compiler
+     *   rejected it at request time, and the call was retried unstrict
+     * - `notAttempted` — this adapter does not send strict at all (OpenAI, Google, OpenRouter)
+     *
+     * This exists because `strictRefusalReasons` alone cannot answer the question. Its absence means
+     * "strict held" OR "nothing ever tried", and a prod run that recorded zero refusals while
+     * returning an array-typed field as a string is exactly the case where the difference matters.
+     *
+     * Internal-only, like `usage` — `UniversalLLMAdapter` lifts it onto the `ai_calls` row and
+     * strips it before the response reaches callers.
+     */
+    strictStatus?: StrictStatus;
     /**
      * Why this call went out WITHOUT `strict`, on an adapter that tried to send it with one.
      *
-     * Present only on a refusal, so absence means either "strict was in effect" or "this adapter
-     * does not attempt strict at all" — the two are distinguished by which adapter answered, not by
-     * this field. `toStrictSchema` already computes these reasons and, until now, nothing consumed
-     * them at the call site: an unstrict call was indistinguishable from a strict one anywhere
-     * outside a dev-only flow log. That invisibility is what let every tenant run unstrict against a
-     * strict-capable API for as long as it took someone to recognise a pre-strict error signature.
+     * The detail behind a `refused` / `compileRejected` `strictStatus` — the short, stable reason
+     * strings `toStrictSchema` computes. Read `strictStatus` to answer "was it enforced"; read this
+     * to answer "why not".
      *
      * Internal-only, like `usage` — `UniversalLLMAdapter` lifts it onto the `ai_calls` row and
      * strips it before the response reaches callers.
@@ -2749,15 +2774,24 @@ interface BaseAICall {
      */
     unvalidatedOutput?: string;
     /**
-     * Why this call went out without `strict` structured output, on an adapter that tried to send it
-     * with one. Present ONLY on a refusal — its absence on a row from a strict-capable adapter means
-     * strict was in effect.
+     * What happened to `strict` structured output on this call — `applied`, `refused`,
+     * `compileRejected`, or `notAttempted`. Every server adapter sets it, so this is the field that
+     * answers "is this agent's output actually being enforced?" without reading source.
      *
-     * This is the row that answers "is this agent's output actually being enforced?" without reading
-     * source. Counting rows that carry it, per resource, is the refusal count: a redeployed agent on
-     * a current bundle should read zero. It exists because the previous answer was a dev-only flow
-     * log, which meant production had no answer — and every sync-managed tenant ran unstrict against
-     * a strict-capable API until a 14-turn session surfaced a pre-strict error signature.
+     * It replaces an inference that turned out to be unsound. `strictRefusalReasons` alone records
+     * only refusals, so an empty row meant "strict held" OR "this adapter never tries" — and a prod
+     * run recorded zero refusals while a call returned an array-typed field as a string, which a
+     * grammar makes impossible. The absence proved nothing, because the deployed API had no way to
+     * write the field at all.
+     *
+     * Absent on rows written before this field existed; that absence is itself diagnostic (the API
+     * predates the change). Existing readers that only look at the fields above are unaffected.
+     */
+    strictStatus?: StrictStatus;
+    /**
+     * Why this call went out without `strict`, when a strict-capable adapter refused the schema. The
+     * detail behind `strictStatus: 'refused' | 'compileRejected'` — read `strictStatus` for whether
+     * it was enforced, this for why not.
      *
      * Existing readers that only look at the fields above are unaffected.
      */
@@ -2817,6 +2851,8 @@ interface LLMUsageData {
     outputValidationError?: string;
     /** Raw model output that failed validation — JSON-stringified, truncated, truncation marked inline */
     unvalidatedOutput?: string;
+    /** What happened to `strict` on this call — set by every server adapter, refusal or not */
+    strictStatus?: StrictStatus;
     /** Why the call went out unstrict, when a strict-capable adapter refused the schema */
     strictRefusalReasons?: string[];
 }

package/dist/test-utils/index.d.ts

@@ -335,6 +335,15 @@ interface ModelConfig {
     modelOptions?: ModelSpecificOptions;
 }
 
+/**
+ * What happened to `strict` on a request, recorded per call rather than inferred.
+ *
+ * `applied` and `notAttempted` are the two states that a refusal-only field cannot tell apart —
+ * both leave `strictRefusalReasons` empty. Recording the verdict positively is what makes "was
+ * this agent's output actually enforced?" answerable from an `ai_calls` row.
+ */
+type StrictStatus = 'applied' | 'refused' | 'compileRejected' | 'notAttempted';
+
 declare const ResourceGovernanceStatusSchema: z.ZodEnum<{
     active: "active";
     deprecated: "deprecated";
@@ -862,6 +871,7 @@ interface WorkflowDefinition {
  * Generic LLM Types
  * Universal interfaces for LLM interaction across all resource types
  */
+
 /**
  * Standard chat message format
  * Compatible with OpenAI, Anthropic, and other providers
@@ -895,15 +905,30 @@ interface LLMGenerateResponse<T = unknown> {
         totalTokens: number;
     };
     cost?: number;
+    /**
+     * What actually happened to `strict` on the request that produced this response. Every server
+     * adapter sets it on every call, so the value is a statement rather than an inference:
+     *
+     * - `applied` — the request carried `strict: true` and the grammar was in effect
+     * - `refused` — `toStrictSchema` could not express the schema, so the request went out unstrict
+     * - `compileRejected` — the schema passed `toStrictSchema` but the provider's grammar compiler
+     *   rejected it at request time, and the call was retried unstrict
+     * - `notAttempted` — this adapter does not send strict at all (OpenAI, Google, OpenRouter)
+     *
+     * This exists because `strictRefusalReasons` alone cannot answer the question. Its absence means
+     * "strict held" OR "nothing ever tried", and a prod run that recorded zero refusals while
+     * returning an array-typed field as a string is exactly the case where the difference matters.
+     *
+     * Internal-only, like `usage` — `UniversalLLMAdapter` lifts it onto the `ai_calls` row and
+     * strips it before the response reaches callers.
+     */
+    strictStatus?: StrictStatus;
     /**
      * Why this call went out WITHOUT `strict`, on an adapter that tried to send it with one.
      *
-     * Present only on a refusal, so absence means either "strict was in effect" or "this adapter
-     * does not attempt strict at all" — the two are distinguished by which adapter answered, not by
-     * this field. `toStrictSchema` already computes these reasons and, until now, nothing consumed
-     * them at the call site: an unstrict call was indistinguishable from a strict one anywhere
-     * outside a dev-only flow log. That invisibility is what let every tenant run unstrict against a
-     * strict-capable API for as long as it took someone to recognise a pre-strict error signature.
+     * The detail behind a `refused` / `compileRejected` `strictStatus` — the short, stable reason
+     * strings `toStrictSchema` computes. Read `strictStatus` to answer "was it enforced"; read this
+     * to answer "why not".
      *
      * Internal-only, like `usage` — `UniversalLLMAdapter` lifts it onto the `ai_calls` row and
      * strips it before the response reaches callers.
@@ -10322,15 +10347,24 @@ interface BaseAICall {
      */
     unvalidatedOutput?: string;
     /**
-     * Why this call went out without `strict` structured output, on an adapter that tried to send it
-     * with one. Present ONLY on a refusal — its absence on a row from a strict-capable adapter means
-     * strict was in effect.
+     * What happened to `strict` structured output on this call — `applied`, `refused`,
+     * `compileRejected`, or `notAttempted`. Every server adapter sets it, so this is the field that
+     * answers "is this agent's output actually being enforced?" without reading source.
      *
-     * This is the row that answers "is this agent's output actually being enforced?" without reading
-     * source. Counting rows that carry it, per resource, is the refusal count: a redeployed agent on
-     * a current bundle should read zero. It exists because the previous answer was a dev-only flow
-     * log, which meant production had no answer — and every sync-managed tenant ran unstrict against
-     * a strict-capable API until a 14-turn session surfaced a pre-strict error signature.
+     * It replaces an inference that turned out to be unsound. `strictRefusalReasons` alone records
+     * only refusals, so an empty row meant "strict held" OR "this adapter never tries" — and a prod
+     * run recorded zero refusals while a call returned an array-typed field as a string, which a
+     * grammar makes impossible. The absence proved nothing, because the deployed API had no way to
+     * write the field at all.
+     *
+     * Absent on rows written before this field existed; that absence is itself diagnostic (the API
+     * predates the change). Existing readers that only look at the fields above are unaffected.
+     */
+    strictStatus?: StrictStatus;
+    /**
+     * Why this call went out without `strict`, when a strict-capable adapter refused the schema. The
+     * detail behind `strictStatus: 'refused' | 'compileRejected'` — read `strictStatus` for whether
+     * it was enforced, this for why not.
      *
      * Existing readers that only look at the fields above are unaffected.
      */
@@ -10390,6 +10424,8 @@ interface LLMUsageData {
     outputValidationError?: string;
     /** Raw model output that failed validation — JSON-stringified, truncated, truncation marked inline */
     unvalidatedOutput?: string;
+    /** What happened to `strict` on this call — set by every server adapter, refusal or not */
+    strictStatus?: StrictStatus;
     /** Why the call went out unstrict, when a strict-capable adapter refused the schema */
     strictRefusalReasons?: string[];
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.41.0",
+  "version": "1.41.1",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -59,8 +59,8 @@
     "typescript": "5.9.2",
     "zod": "^4.1.0",
     "@repo/core": "0.57.0",
-    "@repo/eslint-config": "0.0.0",
-    "@repo/typescript-config": "0.0.0"
+    "@repo/typescript-config": "0.0.0",
+    "@repo/eslint-config": "0.0.0"
   },
   "scripts": {
     "lint": "eslint src --max-warnings 0",