rust-deploy-stale-binary

Answer

Root cause: the JIT-001/002 write-through + read-through reconcile fix landed in source only. The fleet executes ~/.cargo/bin/hilo, which was still the Jul 19 build, so every fleet node ran the pre-fix code path and hilo graph stats kept returning 205 edges (Variant C warm-vs-stats mismatch). Source-level fixes are inert until the binary is rebuilt and redeployed in the same tick.

Fix 1 — rebuild + atomically redeploy in the same tick (the exact tick-44 remediation):

#!/usr/bin/env bash
set -euo pipefail
# WarpFS tick 44 — hilo-cli cache-staleness fix (JIT-001/002)
# Never ship source-only: rebuild and redeploy the binary the fleet runs.
cargo build --release -p hilo-cli                     # 7m39s
install -m 0755 target/release/hilo ~/.cargo/bin/hilo.tmp
mv ~/.cargo/bin/hilo.tmp ~/.cargo/bin/hilo            # atomic replace
cmp -s target/release/hilo ~/.cargo/bin/hilo          # deploy parity check
fleet restart hilo                                    # workers exec the new inode
hilo graph stats                                      # expect 325 edges / 140 files

Fix 2 — make staleness detectable, not inferable (embed build provenance so a stale binary cannot masquerade as current):

// build.rs — stamp every release with its build time and source revision
fn main() {
    let ts = std::process::Command::new("date")
        .args(["+%Y-%m-%dT%H:%M:%SZ"]).output().unwrap();
    println!("cargo:rustc-env=HILO_BUILD_TS={}", String::from_utf8_lossy(&ts.stdout).trim());
    let rev = std::process::Command::new("git")
        .args(["rev-parse", "--short", "HEAD"]).output().unwrap();
    println!("cargo:rustc-env=HILO_SOURCE_REV={}", String::from_utf8_lossy(&rev.stdout).trim());
    println!("cargo:rerun-if-changed=src/");
}

// src/commands/stats.rs — every fleet call now reports which binary produced it
fn run() {
    println!("hilo {} built {} @ {}",
        env!("CARGO_PKG_VERSION"),
        env!("HILO_BUILD_TS"),
        env!("HILO_SOURCE_REV"));
    // ... graph stats path (post-JIT-001/002 reconcile)
}

Fix 3 — deploy-parity gate so future ticks fail loudly instead of silently serving stale logic:

# Tick harness: after ANY change under hilo-cli/src OR any compiled config,
# the tick is not "done" until the installed binary matches the fresh build.
cargo build --release -p hilo-cli
if ! cmp -s target/release/hilo ~/.cargo/bin/hilo; then
  echo "STALE: reinstalling hilo ($(date))"
  install -m 0755 target/release/hilo ~/.cargo/bin/hilo.tmp
  mv ~/.cargo/bin/hilo.tmp ~/.cargo/bin/hilo
  fleet restart hilo
fi
# hard assertion, not a log line:
cmp -s target/release/hilo ~/.cargo/bin/hilo || exit 1

Fix 4 — gitreins evaluator caps upsized per the Rust sizing table (caps are compiled constants, so this also required the redeploy):

# config.toml — gitreins evaluator caps (old -> new)
[evaluator]
max_nodes      = 100            # was 50
max_time_ms    = 30_000         # was 10_000 (10m)
max_mem_mb     = 1_024          # was 400 (0.4M)
max_results    = 2_000_000      # new 2M tier