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

package/dist/normalize.d.ts

@@ -33,5 +33,22 @@ export interface CompileOptions {
  * 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

@@ -260,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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cynodia/axiom-compiler",
-  "version": "0.8.1-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.1-alpha.1",
-    "@cynodia/axiom-runtime": "0.8.1-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",