@almadar/core 10.19.0 → 10.20.0

package/dist/{types-By4AQApw.d.ts → types-DBzaYmuJ.d.ts}

@@ -1,60 +1,4 @@
-import { e as TraitEventListener, f as EntityField, g as EntityPersistence, j as TraitReference, k as RelationConfig } from './trait-BnNByIRE.js';
-
-/**
- * JSON primitives — the universal "data crossed a boundary" type.
- *
- * Every value that arrives over the wire from an LLM (tool-call args),
- * from disk (workspace files), or from an HTTP body before
- * domain-specific validation is a `JsonValue`. Narrow with a typed
- * predicate (`is`-guard) at the boundary; don't widen back to `unknown`.
- *
- * `JsonObject` and `ToolArgs` are aliases for the common
- * `Record<string, JsonValue>` shape. `ToolArgs` is the name the
- * agent surface uses for LLM-emitted tool-call arguments; `JsonObject`
- * is the general-purpose alias. They are the same type — the alias
- * exists so call sites read at the right semantic level.
- *
- * Why not `Record<string, unknown>`? Two reasons. (1) `unknown` widens
- * back to anything, which defeats the purpose of typing the boundary.
- * (2) The `@almadar/eslint-plugin/no-record-string-unknown` rule blocks
- * the wider form — `JsonValue`-based records are the typed answer.
- *
- * @packageDocumentation
- */
-/**
- * Recursive JSON value union — every shape JSON can carry.
- */
-type JsonValue = string | number | boolean | null | JsonValue[] | {
-    [key: string]: JsonValue;
-};
-/**
- * JSON object — keyed string→JsonValue. The wire form of arbitrary
- * structured data. Replaces `Record<string, unknown>` at typed
- * boundaries (LLM emits, file reads, HTTP bodies).
- */
-type JsonObject = {
-    [key: string]: JsonValue;
-};
-/**
- * LLM tool-call arguments — same shape as `JsonObject`, named for the
- * agent-surface call site. Each tool's `execute(args: ToolArgs)`
- * receives this and narrows via an `is`-guard predicate before any
- * field access.
- */
-type ToolArgs = JsonObject;
-/**
- * Type guard: is the given value a JSON primitive (non-array,
- * non-object)? Used by walkers that decide whether to recurse.
- */
-declare function isJsonPrimitive(value: JsonValue): value is string | number | boolean | null;
-/**
- * Type guard: is the given value a JSON object (non-array, non-null)?
- */
-declare function isJsonObject(value: JsonValue): value is JsonObject;
-/**
- * Type guard: is the given value a JSON array?
- */
-declare function isJsonArray(value: JsonValue): value is JsonValue[];
+import { e as TraitEventListener, f as EntityField, g as EntityPersistence, j as TraitReference, k as RelationConfig } from './trait-BcRvHKLW.js';
 
 /**
  * Cross-cutting presentation knobs that don't live per orbital
@@ -123,6 +67,62 @@ interface OwnershipOverlayEntry {
     ownerField: string;
 }
 
+/**
+ * JSON primitives — the universal "data crossed a boundary" type.
+ *
+ * Every value that arrives over the wire from an LLM (tool-call args),
+ * from disk (workspace files), or from an HTTP body before
+ * domain-specific validation is a `JsonValue`. Narrow with a typed
+ * predicate (`is`-guard) at the boundary; don't widen back to `unknown`.
+ *
+ * `JsonObject` and `ToolArgs` are aliases for the common
+ * `Record<string, JsonValue>` shape. `ToolArgs` is the name the
+ * agent surface uses for LLM-emitted tool-call arguments; `JsonObject`
+ * is the general-purpose alias. They are the same type — the alias
+ * exists so call sites read at the right semantic level.
+ *
+ * Why not `Record<string, unknown>`? Two reasons. (1) `unknown` widens
+ * back to anything, which defeats the purpose of typing the boundary.
+ * (2) The `@almadar/eslint-plugin/no-record-string-unknown` rule blocks
+ * the wider form — `JsonValue`-based records are the typed answer.
+ *
+ * @packageDocumentation
+ */
+/**
+ * Recursive JSON value union — every shape JSON can carry.
+ */
+type JsonValue = string | number | boolean | null | JsonValue[] | {
+    [key: string]: JsonValue;
+};
+/**
+ * JSON object — keyed string→JsonValue. The wire form of arbitrary
+ * structured data. Replaces `Record<string, unknown>` at typed
+ * boundaries (LLM emits, file reads, HTTP bodies).
+ */
+type JsonObject = {
+    [key: string]: JsonValue;
+};
+/**
+ * LLM tool-call arguments — same shape as `JsonObject`, named for the
+ * agent-surface call site. Each tool's `execute(args: ToolArgs)`
+ * receives this and narrows via an `is`-guard predicate before any
+ * field access.
+ */
+type ToolArgs = JsonObject;
+/**
+ * Type guard: is the given value a JSON primitive (non-array,
+ * non-object)? Used by walkers that decide whether to recurse.
+ */
+declare function isJsonPrimitive(value: JsonValue): value is string | number | boolean | null;
+/**
+ * Type guard: is the given value a JSON object (non-array, non-null)?
+ */
+declare function isJsonObject(value: JsonValue): value is JsonObject;
+/**
+ * Type guard: is the given value a JSON array?
+ */
+declare function isJsonArray(value: JsonValue): value is JsonValue[];
+
 /**
  * Recursive JSON Schema. Intentionally narrow — only the keywords V2's
  * signature → schema generator emits. Custom `x-*` extensions carry

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@almadar/core",
-  "version": "10.19.0",
+  "version": "10.20.0",
   "description": "Core schema types and definitions for Almadar",
   "type": "module",
   "main": "./dist/index.js",