@cynodia/axiom-compiler 0.8.0-alpha.1 → 0.8.2-alpha.1

package/dist/normalize.d.ts

@@ -1,5 +1,5 @@
 import type { ApplicationGraph, ApplicationIR, ValidationIssue, ValidationResult } from '@cynodia/axiom-core';
-import type { RendererCapabilities } from '@cynodia/axiom-core';
+import type { RendererCapabilities, TriggerRuntimeCapabilities } from '@cynodia/axiom-core';
 export declare class GraphValidationError extends Error {
     readonly problems: ValidationIssue[];
     constructor(result: ValidationResult);
@@ -21,11 +21,34 @@ export interface CompileOptions {
      * rejected at compile time rather than discovered on screen.
      */
     renderer?: RendererCapabilities;
+    /**
+     * The trigger runtime the IR is being compiled for. Defaults to the browser's real (empty)
+     * capability set, because the browser runtime implements no trigger kind — so a
+     * client-authority trigger is rejected at compile time rather than compiled inert.
+     */
+    triggerRuntime?: TriggerRuntimeCapabilities;
 }
 /**
  * Validates a graph and normalizes it into the runtime-ready IR: references resolved,
  * lookups indexed, routes pre-compiled and ordered most-specific-first.
  */
 export declare function compileToIR(graph: ApplicationGraph, options?: CompileOptions): ApplicationIR;
+/**
+ * Validates a graph against the same capabilities `compileToIR` compiles for by default —
+ * the real browser renderer and the real (empty) browser trigger runtime — without
+ * compiling it.
+ *
+ * `validateGraph(graph)` alone is deliberately target-neutral (spec 8.2 §2-4, §41 of spec5):
+ * a graph is never rejected for a renderer or trigger runtime nobody named, the same way
+ * `RendererCapabilities` was already optional before triggers existed. That means a bare
+ * `validateGraph(graph).valid === true` does not by itself say the graph is executable by a
+ * browser — a UI node kind no renderer draws, or a client-authority trigger kind the browser
+ * trigger runtime does not execute (`CLIENT_TRIGGER_UNSUPPORTED`), both validate silently
+ * under the no-options call. A consumer that wants a validate-only answer reflecting actual
+ * browser executability — without compiling the whole IR just to catch a thrown
+ * `GraphValidationError` — calls this instead; `compileToIR(graph)`'s own validation step is
+ * exactly this call, so the two never disagree.
+ */
+export declare function validateForBrowser(graph: ApplicationGraph, options?: Pick<CompileOptions, 'renderer' | 'triggerRuntime'>): ValidationResult;
 export declare function serializeIR(ir: ApplicationIR): string;
 //# sourceMappingURL=normalize.d.ts.map

package/dist/normalize.js

@@ -1,6 +1,6 @@
 import { actionAuthority, actionGuards, authorityContext, inferExpressionType, inferLocationType, itemTypeOf, locationFieldIds, locationRootStateId, referencedIds, resolvePresentationMap, semanticContextFromGraph, stateAuthority, validateGraph, } from '@cynodia/axiom-core';
 import { isUINode, stripAuthoringMetadata } from '@cynodia/axiom-core';
-import { BROWSER_RENDERER_CAPABILITIES } from '@cynodia/axiom-runtime';
+import { BROWSER_RENDERER_CAPABILITIES, BROWSER_TRIGGER_CAPABILITIES } from '@cynodia/axiom-runtime';
 export class GraphValidationError extends Error {
     problems;
     constructor(result) {
@@ -41,6 +41,7 @@ export function compileToIR(graph, options = {}) {
     if (options.validate !== false) {
         const result = validateGraph(graph, {
             renderer: options.renderer ?? BROWSER_RENDERER_CAPABILITIES,
+            triggerRuntime: options.triggerRuntime ?? BROWSER_TRIGGER_CAPABILITIES,
         });
         if (!result.valid) {
             throw new GraphValidationError(result);
@@ -259,6 +260,28 @@ export function compileToIR(graph, options = {}) {
         triggers,
     };
 }
+/**
+ * Validates a graph against the same capabilities `compileToIR` compiles for by default —
+ * the real browser renderer and the real (empty) browser trigger runtime — without
+ * compiling it.
+ *
+ * `validateGraph(graph)` alone is deliberately target-neutral (spec 8.2 §2-4, §41 of spec5):
+ * a graph is never rejected for a renderer or trigger runtime nobody named, the same way
+ * `RendererCapabilities` was already optional before triggers existed. That means a bare
+ * `validateGraph(graph).valid === true` does not by itself say the graph is executable by a
+ * browser — a UI node kind no renderer draws, or a client-authority trigger kind the browser
+ * trigger runtime does not execute (`CLIENT_TRIGGER_UNSUPPORTED`), both validate silently
+ * under the no-options call. A consumer that wants a validate-only answer reflecting actual
+ * browser executability — without compiling the whole IR just to catch a thrown
+ * `GraphValidationError` — calls this instead; `compileToIR(graph)`'s own validation step is
+ * exactly this call, so the two never disagree.
+ */
+export function validateForBrowser(graph, options = {}) {
+    return validateGraph(graph, {
+        renderer: options.renderer ?? BROWSER_RENDERER_CAPABILITIES,
+        triggerRuntime: options.triggerRuntime ?? BROWSER_TRIGGER_CAPABILITIES,
+    });
+}
 export function serializeIR(ir) {
     return JSON.stringify(ir);
 }

package/dist/server.js

@@ -1,4 +1,4 @@
-import { actionAuthority, actionGuards, authorityContext, expressionDefsIn, isObservable, maxContract, requiredServerContract, serverIRExpressions, serverStateClosure, stateAuthority, usesIntegrationVocabulary, validateGraph, } from '@cynodia/axiom-core';
+import { actionAuthority, actionGuards, authorityContext, expressionDefsIn, isObservable, maxContract, requiredServerContract, serverIRExpressions, serverStateClosure, stateAuthority, usesIntegrationVocabulary, usesInvocationVocabulary, usesV4Semantics, validateGraph, } from '@cynodia/axiom-core';
 import { GraphValidationError } from './normalize.js';
 /**
  * Compiles the authoritative half of a graph.
@@ -131,7 +131,14 @@ export function compileToServerIR(graph, options = {}) {
      * one that groups or names an expression, or uses any integration/trigger/event
      * vocabulary, says so, because an older runtime could not execute it.
      */
-    const contract = maxContract(carriesDefinitions ? 'axiom.server.v2' : requiredServerContract(serverIRExpressions(document)), usesIntegrationVocabulary(document) ? 'axiom.server.v3' : 'axiom.server.v1');
+    const contractCandidates = [
+        carriesDefinitions || usesInvocationVocabulary(document)
+            ? 'axiom.server.v2'
+            : requiredServerContract(serverIRExpressions(document)),
+        usesIntegrationVocabulary(document) ? 'axiom.server.v3' : 'axiom.server.v1',
+        usesV4Semantics(document) ? 'axiom.server.v4' : 'axiom.server.v1',
+    ];
+    const contract = contractCandidates.reduce(maxContract);
     return { contract, ...document };
 }
 export function serializeServerIR(ir) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cynodia/axiom-compiler",
-  "version": "0.8.0-alpha.1",
+  "version": "0.8.2-alpha.1",
   "description": "Normalizes an Axiom application graph and emits a self-contained page.",
   "license": "MIT",
   "author": "AskTech AS",
@@ -31,8 +31,8 @@
     }
   },
   "dependencies": {
-    "@cynodia/axiom-core": "0.8.0-alpha.1",
-    "@cynodia/axiom-runtime": "0.8.0-alpha.1"
+    "@cynodia/axiom-core": "0.8.2-alpha.1",
+    "@cynodia/axiom-runtime": "0.8.2-alpha.1"
   },
   "scripts": {
     "build": "tsc -b tsconfig.json tsconfig.test.json",