foottrace 1.0.2 → 1.0.3

package/dist/esm/lib/time-travel/bundles.d.ts

@@ -41,6 +41,10 @@ export declare function readTree(value: unknown): ExecutionTree | undefined;
  *   `changedSince` reads its paths), so a row without one is not a bundle the
  *   fold can survive — it is the crash a gap exists to prevent. `CommitBundle`
  *   declares it required, so no live log is affected.
+ * - Each trace entry needs a known verb and a string `path`. Readers use
+ *   string path operations; accepting a number can silently lose a causal
+ *   writer in a short log and crash the indexed lookup in a longer one.
+ *   Empty strings and historical path spellings remain valid strings.
  * - `updates` / `overwrite`, when present, must be plain objects. They are
  *   read only AT THE PATHS THE TRACE NAMES, so an absent one is harmless and
  *   is tolerated, exactly as the fold tolerates an absent `redactedPaths`.

package/dist/esm/lib/time-travel/bundles.js

@@ -63,6 +63,10 @@ export function readTree(value) {
  *   `changedSince` reads its paths), so a row without one is not a bundle the
  *   fold can survive — it is the crash a gap exists to prevent. `CommitBundle`
  *   declares it required, so no live log is affected.
+ * - Each trace entry needs a known verb and a string `path`. Readers use
+ *   string path operations; accepting a number can silently lose a causal
+ *   writer in a short log and crash the indexed lookup in a longer one.
+ *   Empty strings and historical path spellings remain valid strings.
  * - `updates` / `overwrite`, when present, must be plain objects. They are
  *   read only AT THE PATHS THE TRACE NAMES, so an absent one is harmless and
  *   is tolerated, exactly as the fold tolerates an absent `redactedPaths`.
@@ -95,6 +99,11 @@ export function bundleRefusal(row) {
         if (!isVerb(verb)) {
             return `trace[${i}].verb is ${verb === undefined ? 'missing' : JSON.stringify(verb)}, not ${VERBS.join(' | ')}`;
         }
+        const path = isPlainish(entry) ? entry.path : undefined;
+        if (typeof path !== 'string') {
+            const kind = path === undefined ? 'missing' : path === null ? 'null' : Array.isArray(path) ? 'an array' : `a ${typeof path}`;
+            return `trace[${i}].path is ${kind}, not a string`;
+        }
     }
     return undefined;
 }

package/dist/lib/time-travel/bundles.js

@@ -68,6 +68,10 @@ exports.readTree = readTree;
  *   `changedSince` reads its paths), so a row without one is not a bundle the
  *   fold can survive — it is the crash a gap exists to prevent. `CommitBundle`
  *   declares it required, so no live log is affected.
+ * - Each trace entry needs a known verb and a string `path`. Readers use
+ *   string path operations; accepting a number can silently lose a causal
+ *   writer in a short log and crash the indexed lookup in a longer one.
+ *   Empty strings and historical path spellings remain valid strings.
  * - `updates` / `overwrite`, when present, must be plain objects. They are
  *   read only AT THE PATHS THE TRACE NAMES, so an absent one is harmless and
  *   is tolerated, exactly as the fold tolerates an absent `redactedPaths`.
@@ -100,6 +104,11 @@ function bundleRefusal(row) {
         if (!(0, verbs_js_1.isVerb)(verb)) {
             return `trace[${i}].verb is ${verb === undefined ? 'missing' : JSON.stringify(verb)}, not ${verbs_js_1.VERBS.join(' | ')}`;
         }
+        const path = isPlainish(entry) ? entry.path : undefined;
+        if (typeof path !== 'string') {
+            const kind = path === undefined ? 'missing' : path === null ? 'null' : Array.isArray(path) ? 'an array' : `a ${typeof path}`;
+            return `trace[${i}].path is ${kind}, not a string`;
+        }
     }
     return undefined;
 }

package/dist/types/lib/time-travel/bundles.d.ts

@@ -41,6 +41,10 @@ export declare function readTree(value: unknown): ExecutionTree | undefined;
  *   `changedSince` reads its paths), so a row without one is not a bundle the
  *   fold can survive — it is the crash a gap exists to prevent. `CommitBundle`
  *   declares it required, so no live log is affected.
+ * - Each trace entry needs a known verb and a string `path`. Readers use
+ *   string path operations; accepting a number can silently lose a causal
+ *   writer in a short log and crash the indexed lookup in a longer one.
+ *   Empty strings and historical path spellings remain valid strings.
  * - `updates` / `overwrite`, when present, must be plain objects. They are
  *   read only AT THE PATHS THE TRACE NAMES, so an absent one is harmless and
  *   is tolerated, exactly as the fold tolerates an absent `redactedPaths`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "foottrace",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "type": "commonjs",
   "description": "Execution records, replay, time travel and honest attribution — independent of the engine that produced them",
   "license": "MIT",