@appchy/jarvis 0.1.97 → 0.1.99

package/dist/bin.js

@@ -1395,8 +1395,16 @@ var SCRIPT = `#!/bin/sh
 ${SIGNATURE} \u2014 keeps this repo's map current, so what an agent plans against is what is here.
 # Detached and silenced: git waits for a hook's output streams to close, so a build left on stdout
 # would hold up every commit by the length of a build. Never fails a commit.
+#
+# Run at the lowest priority the machine offers. A code commit still costs a real extract, and one
+# arriving at normal priority the instant you commit is felt as the machine going away for half a
+# minute \u2014 which is how a background job becomes something people turn off. Borrowed from the
+# docdoc-era hook in crispy, which had this right first.
 command -v jarvis >/dev/null 2>&1 || exit 0
-(jarvis build graph >/dev/null 2>&1 &) >/dev/null 2>&1
+NICE=""
+command -v nice >/dev/null 2>&1 && NICE="nice -n 19"
+command -v taskpolicy >/dev/null 2>&1 && NICE="taskpolicy -b $NICE"
+( $NICE jarvis build graph >/dev/null 2>&1 & ) >/dev/null 2>&1
 exit 0
 `;
 function installCommitHook(repoRoot) {
@@ -7118,7 +7126,7 @@ async function freshness(ctx) {
     reason2 = `this checkout is ${origin?.behindBy} commit(s) behind ${origin?.ref} \u2014 the map and the board both describe an older world than the origin's. Pull, then \`jarvis build graph\`.`;
   } else if (originUnknown) {
     verdict = "unknown";
-    reason2 = `cannot reach ${origin?.ref}, so whether this is current is UNKNOWN rather than bad \u2014 rebuilding cannot answer it${origin?.lastSyncedIso ? `. Last heard from a remote at ${origin.lastSyncedIso}` : ", and this clone has never fetched"}.`;
+    reason2 = `cannot reach ${origin?.ref}, so I cannot tell whether this is current \u2014 UNKNOWN rather than out of date, and rebuilding cannot answer it${origin?.lastSyncedIso ? `. Last heard from a remote at ${origin.lastSyncedIso}` : ", and this clone has never fetched"}.`;
   } else if (behindHead) {
     verdict = "stale";
     reason2 = `${graphRel} is ${describeBehind(behindHeadBy, behindHeadForMs)} \u2014 run \`jarvis build graph\` (the incremental update \u2014 it re-extracts in place), then traces and impact are trustworthy again. \`--rebuild\` re-extracts from scratch and relabels; it is for a graph still wrong after a plain build, not for ordinary drift.`;
@@ -10252,7 +10260,7 @@ import { createRequire as createRequire2 } from "module";
 var _require = createRequire2(import.meta.url);
 var VERSION2 = _require("../package.json").version ?? "0.0.0";
 var IS_DEV = String(_require("../package.json").name ?? "").endsWith("-dev");
-var SHA = "8686d75";
+var SHA = "dd93b07";
 var BUILT = "2026-09-11";
 var BUILD = SHA ?? "source";
 var BUILD_LABEL = `${SHA ? `${VERSION2} (${SHA}${BUILT ? ` ${BUILT}` : ""})` : `${VERSION2} (source)`}${IS_DEV ? " \u2014 development build" : ""}`;