@indigoai-us/hq-cloud 5.34.0 → 5.36.0

package/src/journal.ts

@@ -210,6 +210,7 @@ export function updateEntry(
   size: number,
   direction: "up" | "down",
   remoteEtag?: string,
+  mtimeMs?: number,
 ): void {
   const entry: JournalEntry = {
     hash,
@@ -220,6 +221,9 @@ export function updateEntry(
   if (remoteEtag !== undefined && remoteEtag !== "") {
     entry.remoteEtag = normalizeEtag(remoteEtag);
   }
+  if (mtimeMs !== undefined) {
+    entry.mtimeMs = mtimeMs;
+  }
   journal.files[relativePath] = entry;
   journal.lastSync = new Date().toISOString();
 }

package/src/types.ts

@@ -34,6 +34,22 @@ export interface JournalEntry {
    * against `syncedAt`.
    */
   remoteEtag?: string;
+  /**
+   * Local mtime (epoch ms) of the file at the moment we last synced it. Used
+   * by the push planner as the fast-path "is this file unchanged?" check:
+   * when `lstat.size === entry.size && lstat.mtimeMs === entry.mtimeMs`,
+   * the SHA256 is skipped and the file is classified `unchanged` without
+   * reading its bytes. Same trade-off rsync/gitignore use — a same-length
+   * edit that doesn't bump mtime will be missed, but that's vanishingly
+   * rare in practice and the speedup on no-op syncs (~5–10×) is the goal.
+   *
+   * Optional for backwards compatibility: entries written before this field
+   * existed (or symlink entries, where lstat.mtimeMs is the link's own
+   * mtime and the prefixed-hash check is already cheap) fall through to
+   * `hashFile()` on the first post-upgrade sync; the next `updateEntry`
+   * stamps the field so subsequent syncs use the fast-path.
+   */
+  mtimeMs?: number;
   /**
    * Tombstone marker (Journal v2, US-005). When set, this entry represents
    * a file that was pruned by a scope shrink — either implicitly (next pull