@rkmodules/rules 0.0.172 → 0.0.173

package/dist/lib/Engine/cache.d.ts

@@ -41,6 +41,8 @@ export interface CacheRun {
     run: number;
     options: RunOptions;
     visited: Set<string>;
+    /** Activate enclosing graph calls when a descendant actually executes. */
+    onPrimitiveExecution?: () => void;
 }
 /** Engine-owned caches; execution state is carried explicitly across async boundaries. */
 export declare class ExecutionCache {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@rkmodules/rules",
-    "version": "0.0.172",
+    "version": "0.0.173",
     "main": "dist/index.cjs.js",
     "module": "dist/index.esm.mjs",
     "types": "./dist/index.d.ts",

package/readme.md

@@ -418,7 +418,10 @@ Cache hits emit `functionResult` with `cached: true` and
 `cache: { kind, createdAt }`, and populate the current execution context. The
 `createdAt` timestamp identifies the original successful computation. Event
 `duration` and context timings measure this run's work, not the original cached
-computation. `functionCall` fires only when a node executes. Direct primitive runs
+computation. `functionCall` fires only when a primitive executes. An enclosing graph
+call emits it once, immediately before its first executing descendant; traversing
+only cached descendants does not activate the graph node in the editor. Graphs
+still emit results on every traversal. Direct primitive runs
 now also emit these events and a final `result` event. Graph result events continue
 to describe the current traversal rather than a cached whole graph.