@adrrr/tarmac 0.9.0 → 0.10.0

package/dist/schema.js

@@ -63,10 +63,19 @@ export function guardVersions(seen) {
     const state = noVersion > 0 ? 'no-version' : unchecked.length > 0 ? 'unchecked' : 'ok';
     return { state, versions, noVersion, unchecked };
 }
-/** What a human should be told, or `null` when there is nothing worth saying. */
+/** What a human should be told, in the halves a page shows it in. `null` when there is nothing. */
+export function schemaNoteParts(guard) {
+    const said = schemaSaid(guard);
+    return said.length === 0 ? null : { key: 'schema', lead: said[0], rest: said.slice(1).join(' ') };
+}
+/** The same notice, whole. What every caller outside the page still asks for. */
 export function schemaNotice(guard) {
+    const parts = schemaNoteParts(guard);
+    return parts === null ? null : `${parts.lead} ${parts.rest}`.trim();
+}
+function schemaSaid(guard) {
     if (guard.state === 'ok' || guard.state === 'nothing')
-        return null;
+        return [];
     const said = [];
     if (guard.noVersion > 0) {
         const total = guard.noVersion + guard.versions.length;
@@ -83,5 +92,5 @@ export function schemaNotice(guard) {
     // and has no scripts/ directory. Capturing a fixture is a maintainer's move, documented
     // in the README, not something to send a user looking for.
     said.push(`Nothing is blocked and no reading is hidden; if a column starts coming up empty, update tarmac or report it at ${ISSUES_URL}.`);
-    return said.join(' ');
+    return said;
 }

package/dist/sessions.js

@@ -36,6 +36,31 @@ const KNOWN_STATUS = new Map([
 const WAITING = 'waiting';
 /** Whether this reading is halted on a human. The one status the renderers treat as a state. */
 export const isWaiting = (s) => s.status === WAITING;
+/**
+ * The kind a terminal calls itself, and the anchor the two rules below reason from. A
+ * background entry has since been seen beside them — `kind: 'background'`, no `pid`, its word
+ * under `state` rather than `status` — so the two are no longer a reading of that CLI's help.
+ * It is still the anchor and never the list: one observed alternative is not the vocabulary,
+ * and the question asked is only whether anything on this machine still calls itself
+ * `interactive`.
+ */
+export const INTERACTIVE = 'interactive';
+/**
+ * Whether this fleet still speaks the kind we know. If NOTHING calls itself `interactive`, the
+ * word moved rather than every terminal on the machine going background at once — and the
+ * readers say so by treating them all as what they almost certainly still are. Same tolerance
+ * `buildFleet` already applies to telemetry: a signal true of every row is a change in the
+ * source.
+ */
+export const anchoredOnKind = (rows) => rows.some((r) => r.kind === INTERACTIVE);
+/**
+ * A background entry, under the anchor above. An ABSENT kind is not evidence of one: the same
+ * rule the status follows, where unrecognised means unknown, never "the quiet one". The two
+ * mistakes are not the same size — an agent read as a terminal is a row expecting a frame that
+ * will not come, while a terminal read as an agent is someone's open session dropped out of
+ * every count that is about them.
+ */
+export const isBackgroundAgent = (r, anchored) => anchored && r.kind !== null && r.kind !== INTERACTIVE;
 /** @param text raw stdout of `claude agents --json` */
 export function parseAgents(text) {
     let raw;

package/dist/wrapper.js

@@ -157,15 +157,20 @@ esac
 # --- drop the snapshot (best effort, atomic: temp file + rename in the same dir) ---
 if [ -n "$sid" ] && mkdir -p "$TARMAC_DIR" 2>/dev/null; then
   tmp="$TARMAC_DIR/${TEMP_PREFIX}$sid.$$.tmp"
-  # \`2>/dev/null\` comes FIRST, and the order is the whole point: redirections are applied
-  # left to right, so \`> "$tmp" 2>/dev/null\` opens the temp file while stderr is STILL the
-  # user's terminal — the shell prints its own \`cannot create …: Permission denied\` there,
-  # and the \`2>\` that was meant to swallow it only takes effect afterwards. On a snapshot
-  # directory that has become read-only that is one line of noise per FRAME, on the terminal
-  # of a script whose first rule is to be invisible. Exit code and display are untouched
-  # (\`printf\` is a regular built-in, so a failed redirection only fails the command), which
-  # is exactly why nothing but stderr itself catches this. RULE 1.
-  if printf '%s\\n' "$payload" 2>/dev/null > "$tmp"; then
+  # The \`2>/dev/null\` is on the GROUP, and that placement is the whole point: a redirection
+  # that cannot be performed is reported by the shell itself, not by \`printf\`, so it has to
+  # be silenced by something already in force when the failing redirection is attempted. On
+  # the simple command it is not — \`> "$tmp" 2>/dev/null\` opens the temp file while stderr is
+  # STILL the user's terminal, and even \`2>/dev/null > "$tmp"\`, which reads as the fix and
+  # was one under every POSIX sh, leaves zsh printing \`permission denied\` on the terminal.
+  # The group is entered first, so its stderr is /dev/null before the command inside it is
+  # attempted, and that holds under every shell here. On a snapshot directory that has become
+  # read-only the difference is one line of noise per FRAME, on the terminal of a script whose
+  # first rule is to be invisible. Exit code and display are untouched either way (\`printf\` is
+  # a regular built-in, so a failed redirection only fails the command, and a group carries
+  # the status of what it ran), which is exactly why nothing but stderr itself catches this.
+  # RULE 1.
+  if { printf '%s\\n' "$payload" > "$tmp"; } 2>/dev/null; then
     mv -f "$tmp" "$TARMAC_DIR/$sid.json" 2>/dev/null || rm -f "$tmp" 2>/dev/null
   else
     rm -f "$tmp" 2>/dev/null
@@ -293,7 +298,19 @@ else
       case "$rest" in
         *'"'*)
           rest=\${rest#*'"'}
-          printf '%s\\n' "\${rest%%'"'*}"
+          # Cut first, print second, and the two lines are not one on purpose. Spelled
+          # \`printf '%s\\n' "\${rest%%'"'*}"\` — a quoted pattern inside a quoted expansion —
+          # zsh reads the inner \`'\` as a literal character rather than as quoting, and the
+          # script ends on an unmatched \`"\`: a parse error, so nothing runs and the status
+          # line is blank. No POSIX sh does that, and no distribution ships zsh as
+          # \`/bin/sh\`, but linking it there is one command and this file's promise is that
+          # the wrapper runs wherever it is pointed. Dropping the outer quotes is the other
+          # way to make it parse, and it is wrong: unquoted, \`Fable 5\` reaches \`printf\` as
+          # two arguments and prints on two lines, and a \`*\` in a display name is expanded
+          # against the working directory. An assignment splits nothing and globs nothing,
+          # so the cut is safe unquoted and the value is quoted where it is used.
+          display=\${rest%%'"'*}
+          printf '%s\\n' "$display"
           ;;
       esac
       ;;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adrrr/tarmac",
-  "version": "0.9.0",
+  "version": "0.10.0",
   "description": "Fleet observability for Claude Code — reads documented surfaces only, never an internal format",
   "keywords": [
     "claude",