tumwater 0.2.0 → 0.4.0

package/dist/src/cli/log-commands.js

@@ -1,21 +1,26 @@
-// vocabulary: plain
 import { fail, say, sayJsonLine } from "./cli-output.js";
-import { durationLabel, failRivalShapes, flagValue, parseCountFlag, parseGrepFlag, parseRoleScope, parseSinceFlag, parseTypeFlag } from "./cli-args.js";
+import { hasFollowFlag, LOGS_TRANSCRIPT_VALUE_ERROR } from "./cli-flag-specs.js";
+import { durationLabel, failRivalShapes, failUntilShorterThanSince, flagValue, parseCountFlag, parseGrepFlag, parseRoleListScope, parseRoleScope, parseSinceFlag, parseTypeFlag } from "./cli-args.js";
 import { LOGS_SINCE_MAX_MS, readEventsSince, SPARSE_WINDOW_NOTE, } from "../events/event-window.js";
-import { compareCodeUnits, increment, sortByValueDesc } from "../collections.js";
-import { parseEventLine, readEventsTailWithEnd } from "../events/event-read.js";
-import { eventMatchesGrep, formatEvent } from "../events/event-format.js";
+import { compareCodeUnits, increment } from "../collections.js";
+import { eventTypeTally } from "../events/event-tally.js";
+import { eventRole, parseEventLine, readEventsTailWithEnd } from "../events/event-read.js";
+import { eventMatchesGrep, eventResult, formatEvent } from "../events/event-format.js";
 import { canonicalEventType } from "../events/event-legacy.js";
 import { EVENT_TYPE_LABELS, eventTypeLabel } from "../events/event-labels.js";
 import { followFile } from "../files/tail.js";
+import { roleInScope } from "../roles/runner-ids.js";
+import { startParentDeathWatch } from "../process/supervisor.js";
 import { typoSuffix } from "../text/suggest.js";
-import { createTranscriptRenderer } from "../ui/transcript.js";
+import { splitCommaList } from "../text/text.js";
+import { createTranscriptFilter, createTranscriptRenderer } from "../ui/transcript.js";
 import { readTranscriptTail } from "../ui/transcript-tail.js";
+import { isNotableEvent } from "../ui/tone.js";
 import { eventsLogPath, piLogPath } from "../paths.js";
 /** The read-only observing half of the CLI's non-dispatch commands: `tumwater logs` and its
- * `--role` transcript view, split out of cli.ts so the entry point stays a dispatch table. Unlike
+ * `--transcript` view, split out of cli.ts so the entry point stays a dispatch table. Unlike
  * operator/operator-commands.ts these write nothing but stdout — they only read the event log and
- * each loop's agent transcript. It lives beside the other CLI command bodies (history.ts,
+ * each role's agent transcript. It lives beside the other CLI command bodies (history.ts,
  * cli/cli-query-commands.ts, operator/operator-commands.ts), which may import the ui/ rendering
  * layer they drive — here the event formatter and the transcript renderer — while src/ui/
  * itself stays off src/ module boundaries it does not own. */
@@ -36,28 +41,30 @@ function sayEventLine(e, json) {
  * In `--json` mode it emits one compact object mapping `type → count` with keys sorted, the
  * machine-readable twin of the prose tally. */
 function sayTally(events, json) {
-    const counts = new Map();
-    for (const e of events)
-        increment(counts, e.type);
     if (json) {
+        // The machine-readable twin keeps its own alphabetical key sort; the prose tally uses the
+        // shared eventTypeTally ordering.
+        const counts = new Map();
+        for (const e of events)
+            increment(counts, e.type);
         const obj = {};
         for (const [type] of [...counts.entries()].sort((a, b) => compareCodeUnits(a[0], b[0])))
             obj[type] = counts.get(type);
         sayJsonLine(obj);
         return;
     }
-    for (const [type, n] of sortByValueDesc([...counts.entries()]))
+    for (const [type, n] of eventTypeTally(events))
         say(`${n} × ${eventTypeLabel(type)} (${type})`);
 }
 /** The shared rival-shape guard for logs flags that only apply to the event-log feed:
- * `--role` swaps in a transcript rather than the event log (--prompt requires --role, so
- * it is excluded with it), so each such flag fails naming both. One wording for all of them —
- * the --json, --grep, and --since checks cannot drift apart in what they say or why. `active`
- * is the flag's own presence — --json alone composes with nothing here but --role, while
- * --grep and --since call from inside their own presence guards. */
-function rejectRoleViewRival(rest, flag, active) {
-    if (active && (rest.includes("--role") || rest.includes("--prompt")))
-        failRivalShapes(`logs ${flag}`, "--role", "the --role view is the role's agent transcript, not the event log; --prompt requires --role");
+ * `--transcript` swaps in a transcript rather than the event log (--prompt requires
+ * --transcript, so it is excluded with it), so each such flag fails naming both. One wording
+ * for all of them — the --json, --count, --type and --since checks cannot drift apart in what
+ * they say or why. `active` is the flag's own presence. --grep is not one of them: it also
+ * filters the transcript view. */
+function rejectTranscriptViewRival(rest, flag, active) {
+    if (active && (rest.includes("--transcript") || rest.includes("--prompt")))
+        failRivalShapes(`logs ${flag}`, "--transcript", "the --transcript view is the role's agent transcript, not the event log; --prompt requires --transcript");
 }
 /** The missing-pattern error cmdLogs prints for a valueless `--grep`, exported so cli.ts's
  * rejectUnknownArgs spec for --grep can fail a trailing `logs --grep` with the same wording
@@ -73,97 +80,148 @@ export const TYPE_VALUE_ERROR = "logs --type needs an event type";
  * completion already offers the valid codes, so a bare no-match for a near-miss reads as a silent
  * mystery) — while a VALID type that merely has no matching events stays hint-free, a legitimate
  * empty result rather than a typo. A valid type or a legacy alias (canonicalEventType maps the
- * alias onto the current code, which is a label key) never hints. */
-function typeEmpty(type) {
-    const canonical = canonicalEventType(type);
-    const hint = Object.hasOwn(EVENT_TYPE_LABELS, canonical)
-        ? ""
-        : typoSuffix(type, Object.keys(EVENT_TYPE_LABELS));
+ * alias onto the current code, which is a label key) never hints. For a comma list the hint
+ * is for the first piece that is not a valid type; the prose names the value as typed. */
+function typeEmpty(type, pieces) {
+    const bad = pieces.find((p) => !Object.hasOwn(EVENT_TYPE_LABELS, canonicalEventType(p)));
+    const hint = bad === undefined ? "" : typoSuffix(bad, Object.keys(EVENT_TYPE_LABELS));
     return `no events matching "${type}"${hint}`;
 }
-/** `tumwater logs [-f] [-n <count>] [--since <duration>] [--role <id>] [--prompt]`: follow or
- * dump the harness event log, with `--since` a bounded past window of it, or with `--role` one
- * loop's agent transcript (see cmdLogsTranscript). */
-export async function cmdLogs(root, args) {
-    // `--grep <text>` filters the event feed (the -n view and its follow): case-insensitive
+/** Follow `file` until Ctrl+C or until the process that started this one is gone (the shape of
+ * a `logs -f` leaked to PPID 1 that polled for days). Resolves once the parent is gone. */
+export function followUntilParentGone(file, offset, onLines, seams) {
+    const stop = followFile(file, offset, onLines);
+    return new Promise((resolve) => {
+        startParentDeathWatch(() => {
+            stop();
+            resolve();
+        }, {
+            ...(seams.ppid ? { ppid: seams.ppid } : {}),
+            ...(seams.intervalMs !== undefined ? { intervalMs: seams.intervalMs } : {}),
+        });
+    });
+}
+/** `tumwater logs [-f] [-n <count>] [--since <duration>] [--until <duration>]
+ * [--role <id>[,<id>...]] [--transcript <id>] [--prompt]
+ * [--grep <text>]`: follow or dump the harness event log, with `--since` a bounded
+ * past window of it and `--role` keeping only the listed roles' events (a base role id takes its
+ * instances too),
+ * or with `--transcript` one role's agent transcript (see cmdLogsTranscript). `-f` follows until
+ * Ctrl+C or until its parent process exits. */
+export async function cmdLogs(root, args, seams = {}) {
+    // `--grep <text>` filters the event feed (the -n view and its follow) and, with --transcript,
+    // the transcript's entries (see cmdLogsTranscript): case-insensitive
     // substring against `${e.type} ${formatEvent(e)}` — the rendered line is what the operator
     // would otherwise read (WYSIWYG), and prefixing the raw type id lets stable ids
     // (review_rejected, merge_failed) be filtered even where the rendering paraphrases them.
-    // Rival shapes stay exclusive — --role swaps in a transcript rather than this event log
-    // (--prompt requires --role, so it is excluded with it), and --since is a filter of its own
-    // rather than a window to filter — and each failure names both flags. The flag scan itself
+    // --grep filters the --since window like --type and --role do. The flag scan itself
     // (the value lookup, the `rest` construction that keeps a flag-shaped pattern from
     // impersonating a rival flag, and the empty-value fail) is cli/cli-args.ts's parseGrepFlag,
     // the one home shared with history's identical preamble.
     const { rest: grepped, pattern: grepPattern } = parseGrepFlag(args, GREP_VALUE_ERROR);
     // `--type <eventType>` filters the event feed by EXACT event type (e.type === value):
     // deterministic where --grep substrings — a merge_failed whose rendered line quotes
-    // "merge_failed" matches --grep but not --type. Unlike --grep it composes with --since
-    // (the window, not a filter of its own) as well as -n, -f, --json, and --grep; like --json
-    // it is a rival only of the --role/--prompt transcript view. The value scan (keeping a
+    // "merge_failed" matches --grep but not --type. It composes with --since
+    // (the window it filters) as well as -n, -f, --json, and --grep; like --json
+    // it is a rival only of the --transcript/--prompt transcript view. A comma list matches any
+    // of its types. The value scan (keeping a
     // flag-shaped value like --since as text, the empty-value fail) mirrors parseGrepFlag via
     // parseTypeFlag, so the two cannot drift; `rest` here has both flags' value tokens removed.
     const { rest, type } = parseTypeFlag(grepped, TYPE_VALUE_ERROR);
     const grepLower = grepPattern === null ? null : grepPattern.toLowerCase();
     // An older event name matches its current one; the empty-match prose still names what was typed.
-    const wantedType = type === null ? null : canonicalEventType(type);
-    const typeFilter = type === null ? null : (e) => e.type === wantedType;
+    const typePieces = type === null ? [] : splitCommaList(type);
+    if (type !== null && typePieces.length === 0)
+        fail(TYPE_VALUE_ERROR);
+    const wantedTypes = new Set(typePieces.map(canonicalEventType));
+    const typeFilter = type === null ? null : (e) => wantedTypes.has(e.type);
     // The composed feed rule every emit site threads today's grep-only predicate through:
     // an event passes when it is absent-or-matches the --grep substring AND absent-or-equals
     // the --type id, held in one place so the --since window, the -n tally, and the follow
     // cannot drift on what an event must satisfy.
+    // `--role <id>[,<id>...]` joins them: an event passes when the role it was filed under, or
+    // that role's base id (so `--role feature` takes `feature-2` too), is listed. It
+    // composes with --since. The value scan reads `rest`, which holds no --grep/--type value tokens.
+    const roles = parseRoleListScope(root, rest);
+    const roleFilter = roles === null
+        ? null
+        : (e) => roleInScope(eventRole(e), roles);
+    if (roles !== null)
+        rejectTranscriptViewRival(rest, "--role", true);
+    // `--notable` culls routine bookkeeping events the way the dashboard Activity feed's Notable
+    // choice does (src/ui/tone.ts eventKind): only non-routine rows pass the feed. One harness-side
+    // rule (isNotableEvent) shared with the TUI Activity pane, so the CLI feed and the pane cannot
+    // disagree about what a notable filter hides. It composes with --since, --grep, --type, --role,
+    // -n, -f, --count and --json, and — like --json/--count/--type/--since — is a rival only of the
+    // --transcript transcript view.
+    const notable = rest.includes("--notable");
+    rejectTranscriptViewRival(rest, "--notable", notable);
     const feedFilter = (e) => (grepLower === null || eventMatchesGrep(e, grepLower)) &&
-        (typeFilter === null || typeFilter(e));
-    const follow = rest.includes("-f") || rest.includes("--follow");
+        (typeFilter === null || typeFilter(e)) &&
+        (roleFilter === null || roleFilter(e)) &&
+        (!notable || isNotableEvent(e.type, eventResult(e)));
+    // Empty-match prose: grep/type keep their wording when given; a role-only filter names the roles.
+    const roleEmpty = roles === null ? "" : `no events from ${roles.join(", ")}`;
+    const filtersGrepOrType = grepPattern !== null || type !== null;
+    const follow = hasFollowFlag(rest);
     // `--json` switches the feed from formatEvent rendering to one JSON.stringify(e) per line —
     // the raw HarnessEvent objects exactly as stored in the log — so scripts read the canonical
     // schema instead of parsing a rendering that changes shape whenever the formatter evolves.
     // It composes with -n, --grep, --since and -f (the grep filter applies before serialization,
-    // the follow streams JSON lines as events land), but not with --role: that view is a pi
-    // transcript of human-oriented prose, not the event log (--prompt requires --role, so it is
+    // the follow streams JSON lines as events land), but not with --transcript: that view is a pi
+    // transcript of human-oriented prose, not the event log (--prompt requires --transcript, so it is
     // excluded with it).
     const json = rest.includes("--json");
-    rejectRoleViewRival(rest, "--json", json);
+    rejectTranscriptViewRival(rest, "--json", json);
     // `--count` tallies the window's present event types instead of printing the rows. Rival
     // shapes stay exclusive: counting implies a bounded window (so -f/--follow is rejected)
-    // and the --role view is the role's agent transcript rather than the event log.
+    // and the --transcript view is the role's agent transcript rather than the event log.
     const count = rest.includes("--count");
-    rejectRoleViewRival(rest, "--count", count);
+    rejectTranscriptViewRival(rest, "--count", count);
     if (count && follow)
         failRivalShapes("logs --count", "-f/--follow", "counting implies a bounded window; -f follows from now on");
     if (type !== null)
-        rejectRoleViewRival(rest, "--type", true);
-    if (grepPattern !== null) {
-        rejectRoleViewRival(rest, "--grep", true);
-        if (rest.includes("--since"))
-            failRivalShapes("logs --grep", "--since", "--since is a filter of its own; --grep filters the -n view and its follow");
-    }
+        rejectTranscriptViewRival(rest, "--type", true);
     // `--since <duration>` is the window-shaped view over the same event log the -n view dumps:
     // it reads a bounded past window (event-window.ts's day-keyed backwards scan) and prints the
     // survivors oldest-first, so an operator can ask for "the hour around that 429 storm" without
     // guessing a count. Rival shapes stay exclusive — follow means "from now on", -n means "last
-    // N", and --role swaps in a transcript rather than this log — and each failure names
-    // both flags. (--prompt requires --role, so it is excluded with it.)
+    // N", and --transcript swaps in a transcript rather than this log — and each failure names
+    // both flags. (--prompt requires --transcript, so it is excluded with it.)
     const ms = parseSinceFlag(rest, "logs --since", LOGS_SINCE_MAX_MS);
+    const untilMs = parseSinceFlag(rest, "logs --until", LOGS_SINCE_MAX_MS, "--until");
+    failUntilShorterThanSince("logs", untilMs, ms);
     if (ms !== null) {
         if (follow)
             failRivalShapes("logs --since", "-f/--follow", 'follow means "from now on"; --since shows a bounded past window');
         if (rest.includes("-n"))
             failRivalShapes("logs --since", "-n", "a count and a window are rival shapes");
-        rejectRoleViewRival(rest, "--since", true);
+        rejectTranscriptViewRival(rest, "--since", true);
         // covered is only consulted below when the window has rows (an empty window returns
         // earlier), so the helper's vacuous empty-log branch never reaches the note here.
-        const { events, covered } = readEventsSince(root, ms);
-        // `--type` composes with the window (it is NOT the --since rival --grep is): only the
-        // window events of the exact type are printed, and an all-filtered window answers with
-        // the no-match prose (the type's own line) instead of the generic empty-window one —
+        const { cutoff, events: windowEvents, covered } = readEventsSince(root, ms);
+        const events = untilMs === null ? windowEvents : windowEvents.filter((e) => e.ts < cutoff + ms - untilMs);
+        const windowPhrase = untilMs === null ? `in ${durationLabel(ms)}` : `between ${durationLabel(ms)} and ${durationLabel(untilMs)} ago`;
+        // `--grep`, `--type` and `--role` all filter the window through feedFilter: only the
+        // window events that pass are printed, and an all-filtered window answers with the
+        // no-match prose (the filter's own line) instead of the generic empty-window one —
         // "which merge_failed in the last hour" filters the same as it would the -n view.
-        const filtered = type === null ? events : events.filter((e) => e.type === wantedType);
+        const filtered = events.filter(feedFilter);
         if (filtered.length === 0) {
             // In JSON mode an empty result answers silently — an empty output IS the machine-readable
             // answer, and prose would corrupt a consumer's NDJSON stream.
-            if (!json)
-                say(type === null ? `no events in ${durationLabel(ms)}` : typeEmpty(type));
+            if (!json) {
+                if (notable && grepPattern === null && type === null && roles === null)
+                    say(`no notable events ${windowPhrase}`);
+                else if (grepPattern !== null && type !== null)
+                    say(`no events matching "${grepPattern}" or ${typeEmpty(type, typePieces)}`);
+                else if (type !== null)
+                    say(typeEmpty(type, typePieces));
+                else if (grepPattern !== null)
+                    say(`no events matching "${grepPattern}" ${windowPhrase}`);
+                else
+                    say(roles !== null ? `${roleEmpty} ${windowPhrase}` : `no events ${windowPhrase}`);
+            }
             return;
         }
         // `--count` composes with the window: the tally covers exactly the filtered window rows
@@ -187,14 +245,14 @@ export async function cmdLogs(root, args) {
     }
     const nRaw = flagValue(rest, "-n");
     const limit = nRaw !== null ? parseCountFlag("-n", nRaw) : 50;
-    // The event feed (no --role) never needs the config at all: parseRoleScope reads it only
+    // The event feed (no --transcript) never needs the config at all: parseRoleScope reads it only
     // when the flag is present.
-    const role = parseRoleScope(root, rest);
+    const role = parseRoleScope(root, rest, "--transcript", LOGS_TRANSCRIPT_VALUE_ERROR);
     const showPrompts = rest.includes("--prompt");
     if (showPrompts && role === null)
-        fail("logs --prompt needs --role <id>");
+        fail("logs --prompt needs --transcript <id>");
     if (role !== null) {
-        await cmdLogsTranscript(root, role, limit, follow, showPrompts);
+        await cmdLogsTranscript(root, role, limit, follow, showPrompts, grepLower, grepPattern, seams);
         return;
     }
     // -n bounds the scan, not the print: the matched subset of the last `limit` events is what
@@ -202,7 +260,7 @@ export async function cmdLogs(root, args) {
     // the tail-with-end shape (not the per-poll cached readEvents) so the follow below can seed
     // from the byte end this very read covered instead of a later stat of the file.
     const tail = readEventsTailWithEnd(root, limit);
-    const shown = grepLower !== null || type !== null ? tail.events.filter(feedFilter) : tail.events;
+    const shown = grepLower !== null || type !== null || roleFilter !== null || notable ? tail.events.filter(feedFilter) : tail.events;
     // `--count` over the -n view answers with the tally of exactly the filtered rows the plain
     // view would print, and carries over the plain view's empty-match prose below (a `--type`
     // or `--grep` that matches nothing names its value; an empty unfiltered -n view prints
@@ -210,13 +268,17 @@ export async function cmdLogs(root, args) {
     if (count) {
         if (shown.length !== 0)
             sayTally(shown, json);
-        else if (!json && (grepPattern !== null || type !== null)) {
-            if (grepPattern !== null && type !== null)
-                say(`no events matching "${grepPattern}" or ${typeEmpty(type)}`);
+        else if (!json && (filtersGrepOrType || roles !== null || notable)) {
+            if (notable && grepPattern === null && type === null && roles === null)
+                say("no notable events");
+            else if (grepPattern !== null && type !== null)
+                say(`no events matching "${grepPattern}" or ${typeEmpty(type, typePieces)}`);
             // Type-empty gets the hint (only the type branch); a grep-only empty stays the bare
             // no-match line, because a free-text pattern is not an event type to suggest against.
+            else if (!filtersGrepOrType)
+                say(roleEmpty);
             else
-                say(type !== null ? typeEmpty(type) : `no events matching "${grepPattern ?? ""}"`);
+                say(type !== null ? typeEmpty(type, typePieces) : `no events matching "${grepPattern ?? ""}"`);
         }
         return;
     }
@@ -226,13 +288,17 @@ export async function cmdLogs(root, args) {
         // The empty-match line is prose: in JSON mode the empty output is the answer. It fires
         // for either filter, naming the flag's value(s) whose match came up empty so the operator
         // knows what to loosen.
-        if (shown.length === 0 && !json && (grepPattern !== null || type !== null)) {
-            if (grepPattern !== null && type !== null)
-                say(`no events matching "${grepPattern}" or ${typeEmpty(type)}`);
+        if (shown.length === 0 && !json && (filtersGrepOrType || roles !== null || notable)) {
+            if (notable && grepPattern === null && type === null && roles === null)
+                say("no notable events");
+            else if (grepPattern !== null && type !== null)
+                say(`no events matching "${grepPattern}" or ${typeEmpty(type, typePieces)}`);
             // Type-empty gets the hint (only the type branch); a grep-only empty stays the bare
             // no-match line, because a free-text pattern is not an event type to suggest against.
+            else if (!filtersGrepOrType)
+                say(roleEmpty);
             else
-                say(type !== null ? typeEmpty(type) : `no events matching "${grepPattern ?? ""}"`);
+                say(type !== null ? typeEmpty(type, typePieces) : `no events matching "${grepPattern ?? ""}"`);
         }
         return;
     }
@@ -245,7 +311,7 @@ export async function cmdLogs(root, args) {
     // log scans to coveredEnd 0, and followFile tolerates a missing file (its poll re-stats
     // every interval), so a read-only command never leaves a harness state file behind — the
     // module contract above promises writes to stdout only.
-    followFile(file, tail.coveredEnd, (lines) => {
+    await followUntilParentGone(file, tail.coveredEnd, (lines) => {
         for (const line of lines.filter(Boolean)) {
             const e = parseEventLine(line);
             // The filter holds across rotation: every event the follow callback sees goes through
@@ -253,19 +319,31 @@ export async function cmdLogs(root, args) {
             if (e && feedFilter(e))
                 sayEventLine(e, json);
         }
-    });
-    await new Promise(() => { }); // Follow until Ctrl+C.
+    }, seams);
 }
-/** `tumwater logs --role <id>`: print (and optionally follow) one loop's agent transcript —
+/** `tumwater logs --transcript <id>`: print (and optionally follow) one role's agent transcript —
  * run separators, abbreviated thinking, assistant text, and tool calls; with `--prompt` also
  * each run's exact prompt text. Read-only; the raw log is pi's streaming event stream, so only
- * complete renderable events are shown. */
-async function cmdLogsTranscript(root, role, limit, follow, showPrompts) {
+ * complete renderable events are shown. With `--grep`, only entries with a rendered line
+ * containing the text (case-insensitively) print, each under its run's separator; `-n` still
+ * bounds the entries scanned, not printed. */
+async function cmdLogsTranscript(root, role, limit, follow, showPrompts, needle, pattern, seams) {
     const file = piLogPath(root, role);
     const opts = { includePrompts: showPrompts };
+    const filter = needle === null ? null : createTranscriptFilter(needle);
+    let matched = 0;
     const printEntry = (lines) => {
-        if (lines.length > 0)
+        if (lines.length === 0)
+            return;
+        if (filter === null) {
             say(lines.join("\n"));
+            return;
+        }
+        const out = filter(lines);
+        if (out === null)
+            return;
+        matched++;
+        say(out.join("\n"));
     };
     // Initial window: the last `limit` entries of what is on disk. readTranscriptTail scans back
     // from EOF only as far as needed instead of re-reading the whole (up to logMaxBytes) file,
@@ -280,6 +358,8 @@ async function cmdLogsTranscript(root, role, limit, follow, showPrompts) {
         for (const entry of tail.entries)
             printEntry(entry);
         offset = tail.end;
+        if (needle !== null && matched === 0)
+            say(`no transcript entries matching "${pattern ?? ""}" for ${role}`);
     }
     if (!follow)
         return;
@@ -288,9 +368,8 @@ async function cmdLogsTranscript(root, role, limit, follow, showPrompts) {
     // readTranscriptTail's formatTranscript already flushed any pending separator for what
     // was on disk.
     const renderer = createTranscriptRenderer(opts);
-    followFile(file, offset, (lines) => {
+    await followUntilParentGone(file, offset, (lines) => {
         for (const line of lines)
             printEntry(renderer.feed(line));
-    });
-    await new Promise(() => { }); // Follow until Ctrl+C.
+    }, seams);
 }