@llblab/pi-kit 0.1.4 → 0.1.6

package/node_modules/@llblab/pi-telegram/README.md

@@ -57,7 +57,7 @@ Paste the bot token. If `~/.pi/agent/telegram.json` already contains a saved tok
 
 The connected Pi instance owns Telegram polling. Use `/telegram-connect <name>` to activate a named profile. Each profile is a parallel bot runtime with isolated polling, diagnostics, Threaded Mode state, and local bus transport; the `default` profile keeps unsuffixed runtime paths. In classic mode each profile uses a singleton lock. When Telegram private-chat Threaded Mode is available, one live instance becomes the profile's leader and later visible Pi instances register as followers.
 
-After an unclean computer shutdown, `/telegram-connect` detects truncated or structurally invalid temporary ownership/routing files, quarantines only the damaged files under `tmp/telegram/recovery/`, and retries once. Saved `telegram.json` configuration and runtime diagnostics remain intact. Recovery never replaces a verifiable live owner; if safe automatic recovery cannot complete, the command gives one explicit Pi-restart instruction instead of requiring deletion of the whole `tmp/` directory.
+After an unclean computer shutdown, `/telegram-connect` detects truncated or structurally invalid temporary ownership/routing files, quarantines only the damaged files under `tmp/telegram/recovery/`, and retries once. A journal snapshot removed by older broad temp cleanup is rebuilt when its complete segment history proves an empty result, while a revisionless snapshot is repaired from the first surviving segment's exact predecessor when the reconstructed tail validates. Otherwise the snapshot and segments are quarantined as recovery evidence, a fresh journal is published, and startup continues with an informational diagnostic instead of requiring manual JSON repair. Saved `telegram.json` configuration and runtime diagnostics remain intact. Recovery never replaces a verifiable live owner; if safe automatic recovery cannot complete, the command gives one explicit Pi-restart instruction instead of requiring deletion of the whole `tmp/` directory.
 
 ### 4. Pair your Telegram account
 

package/node_modules/@llblab/pi-telegram/docs/architecture.md

@@ -163,7 +163,7 @@ Telegram private-chat Threaded Mode is the public switch for multi-instance Tele
 
 Named Telegram profiles are orthogonal to Threaded Mode. The selected profile chooses the bot/session slice (`botToken`, `botId`, `botUsername`, `allowedUserId`, `lastUpdateId`) and scopes the `owners.json` slot, diagnostics logs, state files, thread/bus ownership, and leader/follower IPC endpoints; it must not change the Threaded Mode rules. Within one selected profile, leader/follower election, bus transport, thread provisioning, routing, ownership forwarding, cleanup, and runtime diagnostics behave exactly as they do for the `default` slot. A different selected profile is a parallel bot runtime: its owner slot, `tmp/telegram/state.<profile>.json`, `tmp/telegram/logs.<profile>.jsonl`, `tmp/telegram/logs.<profile>._prev.jsonl`, thread bindings, Unix sockets, and Windows named pipes are isolated from the default profile and other named profiles while shared bridge settings remain top-level/global.
 
-Profile reality follows three explicit storage classes. `telegram.json` shared settings and extension registries are process-global platform configuration; `profiles.default` and `profiles.<name>` bot/session fields plus observable transport/routing authority are profile-scoped; queues, active turns, ownership caches, menu state, and runtime controllers are session-local memory. Config persistence serializes cross-process writers and applies each recursive mutation delta to the latest disk snapshot, so named-profile offsets and unrelated global/profile updates do not stale-replace one another. Polling publishes only its monotonic `lastUpdateId` into the current config-store snapshot; it never persists the detached full config object captured at poll start, which would interpret newer Settings fields as deletions. Runtime profile switching follows stop-old/commit-new ordering: reload keeps the selected identity stable, old polling/lock/bus teardown finishes while all dynamic resolvers still point at the old profile, and only then may activation expose the new token, lock key, state path, target namespace, and IPC endpoint. Downloaded attachments use UUID-prefixed names in the shared Telegram scratch directory and are session artifacts rather than identity or routing authority, so cross-profile cleanup is limited to stale scratch files and cannot redirect live traffic.
+Profile reality follows three explicit storage classes. `telegram.json` shared settings and extension registries are process-global platform configuration; `profiles.default` and `profiles.<name>` bot/session fields plus observable transport/routing authority are profile-scoped; queues, active turns, ownership caches, menu state, and runtime controllers are session-local memory. Config persistence serializes cross-process writers and applies each recursive mutation delta to the latest disk snapshot, so named-profile offsets and unrelated global/profile updates do not stale-replace one another. Polling publishes only its monotonic `lastUpdateId` into the current config-store snapshot; it never persists the detached full config object captured at poll start, which would interpret newer Settings fields as deletions. Runtime profile switching follows stop-old/commit-new ordering: reload keeps the selected identity stable, old polling/lock/bus teardown finishes while all dynamic resolvers still point at the old profile, and only then may activation expose the new token, lock key, state path, target namespace, and IPC endpoint. Downloaded attachments use UUID-prefixed names in the shared Telegram scratch directory and are session artifacts rather than identity or routing authority, so cross-profile cleanup recognizes only those UUID-prefixed scratch files. It never age-deletes journals, ownership, state, logs, or other top-level runtime files and therefore cannot redirect live traffic or orphan immutable journal segments.
 
 When Threaded Mode is active, the current polling owner is also the Telegram bus leader. The leader owns the local bus endpoint (Unix-domain socket on Unix-like platforms, named pipe on native Windows), polls `getUpdates`, performs direct Bot API calls, records follower heartbeats, prunes stale followers, and provisions Telegram UI thread targets through live runtime/bus state. Follower liveness is intentionally fast because heartbeat traffic is local IPC: followers heartbeat every `1s`, the leader treats them as stale after `2s`, and the prune loop runs every `1s` so stopped followers are detected promptly while active forwarded updates/API calls still refresh liveness. Heartbeat pruning is silent liveness bookkeeping and does not send a Telegram-visible disconnected notice, because the common cause may be leader reload or IPC handoff rather than a dead follower. Pruning alone preserves the binding; when Thread cleanup is enabled, only a subsequent OS check that confirms the exact registered PID absent may create fenced cleanup intent, and that cleanup serializes ahead of replacement registration. Successful follower target reuse refreshes the binding's recovery timestamp. Absent follower bindings remain durable restoration hints until explicit stale, deleted, offline, or reconciliation evidence invalidates them; process absence and heartbeat pruning alone do not remove them. If an authenticated live follower carries an exact target that is absent from current bindings, the leader recovers it only behind a synchronous visibility probe: success activates it, explicit stale evidence provisions a replacement, and ambiguous failure rejects registration. A carried slot is restored only when it is not already occupied. `tmp/telegram/logs.jsonl` is a session-local redacted runtime evidence stream for race debugging; it resets on extension start and runtime scope changes, and must not become routing/provisioning authority. `tmp/telegram/state.json` is an extension+bot observable/debug snapshot aligned with status diagnostics: `source: "snapshot"` and `writtenAtMs` mark it as observational, not authoritative. All instances on one Telegram profile read the same snapshot, but only the active transport lock owner persists it; followers become writers only after promotion. Status-only persistence reloads current disk bindings before serialization, preventing a stale follower/status view from erasing newer leader-owned targets. Fresh capability observations may skip redundant startup probes, but stale snapshots re-probe before suppressing bus/thread behavior. Top-level `bot` mirrors bot-wide capabilities such as thread mode, `runtime` describes process role/status, `liveRoster` mirrors followers/current targets/reservations, `diagnostics` mirrors recent status/debug signals including the latest thread-reconciler phase/counts, `threads` stores current routeable bindings, TTL-bounded reservations explain short-lived slot collision guards, and TTL-pruned `pendingProvisions` protects in-flight topic creation slots from cleanup/allocation races. Fresh provisioning writes pending state before the Bot API create call, adds the returned target to the pending record, persists a `starting` binding, then promotes it to `active` and clears pending state. If final binding persistence fails after Telegram returns a thread id, the targeted pending provision remains as cleanup/retry evidence. Once targeted pending provisions expire, they are retained for `thread-reconciler` close/delete cleanup and pending scratchpad removal after a successful cleanup apply; untargeted expired pending records can prune without cleanup because no Telegram thread id exists. Runtime events coalesce status-snapshot writes so transient bus/API/update failures remain inspectable even when the operator has not opened `/telegram-status`. The bridge must not keep a durable `telegram-targets.json` target history; stale/offline/failed thread observations are pruned instead of reused. Previous-process leader bindings that still probe alive become reservations/collision guards, not routeable active threads, so a reloaded leader can take the next free slot without duplicating the same visible tab name. The thread chat is always the private bot DM with the paired owner (`allowedUserId`). In Telegram private-chat Threaded Mode, the leader creates/reuses its own thread before polling — it is a real bound instance, not a dispatcher. Followers authenticate bus envelopes with the leader-minted capability secret stored in the active lock entry. Bot capability monitoring does not probe through the bus until the process either owns that direct lock or has completed authenticated follower registration. Leader lock entries also carry a stable `leaderEpoch` minted on acquisition and preserved across heartbeat refreshes; leader-owned cleanup/provisioning plans stamp that epoch, and Thread Reconciler apply skips destructive work if leadership has moved on before side effects run. Followers own their own Pi session state, queue, active turns, previews, menus, and lifecycle hooks, but route allowlisted, target-scoped Telegram API calls through the leader. When a follower promotes after heartbeat loss, status/state diagnostics expose only the transient `electing` lifecycle phase; stable `leader`/`follower` identity stays in the bus role so diagnostics do not duplicate role state. The TUI status bar and `/telegram-status` report `leader` or `follower` role so a registered follower is not shown as generically disconnected. Terminal status identity and the `[telegram|thread:name]` prompt label use the same target-aware current-instance resolver: registered local metadata wins over a stale shared binding for the matching target, while the binding remains a fallback for partial metadata.
 
@@ -205,9 +205,9 @@ All inbound updates are gated by the configured authorized user id.
 
 Here, **durable** means recovery across ordinary process exit, crash, kill, and replacement after a successful atomic rename is visible to the filesystem. It does not promise survival across host, kernel, filesystem, storage-device, or power failure: journal and offset publication do not call `fsync`/`fdatasync`, and parent directories are not flushed. A host-level failure may therefore lose a recently acknowledged rename despite correct process-level ordering. Operators requiring that stronger boundary must place the agent directory on storage with an independently managed durability/backup policy; `0.28.0` must not be described as power-loss durable.
 
-The profile-scoped journal separates transport progress from semantic progress. Leader/classic snapshots live at `tmp/telegram/inbox[.<profile>].json`; follower paths add a stable target-binding hash. The selected post-v1 storage design is one revisioned compacted snapshot plus immutable atomic transaction segments beside it. Existing v1 files load as implicit revision `0`, while positive snapshot revisions are explicit. Immutable revision segments publish privately and atomically under the existing journal transaction lock; exact repeats are idempotent, while gaps and conflicting duplicate revisions fail closed. Each segment carries one complete mutation, and readers reconstruct ordered upserts, removals, and operator-disposition state only from revisions newer than the snapshot. Malformed or gapped segments, filename/revision disagreement, and foreign journal identity fail closed. After the initial snapshot, append, batch completion, queue receipt/owner/handoff, retry/terminal, recovery, and operator dispositions publish only changed upserts/removals and disposition replacement in one segment. This avoids rewriting retained raw updates during completion-heavy drains without splitting exact queue, failure, recovery, or disposition transactions.
+The profile-scoped journal separates transport progress from semantic progress. Leader/classic snapshots live at `tmp/telegram/inbox[.<profile>].json`; follower paths add a stable target-binding hash. The selected post-v1 storage design is one revisioned compacted snapshot plus immutable atomic transaction segments beside it. Existing v1 files load as implicit revision `0`, while positive snapshot revisions are explicit. Immutable revision segments publish privately and atomically under the existing journal transaction lock; exact repeats are idempotent, while gaps and conflicting duplicate revisions fail closed. Each segment carries one complete mutation, and readers reconstruct ordered upserts, removals, and operator-disposition state only from revisions newer than the snapshot. Malformed or gapped segments, filename/revision disagreement, and foreign journal identity fail closed. Compatibility recovery for the former broad temp-cleanup bug rebuilds a missing snapshot when its complete revision-1 segment chain removes known base authority before any upsert and reconstructs to an empty journal, and repairs a revisionless snapshot when the first surviving segment supplies its exact positive predecessor revision and the reconstructed tail validates. If repair fails, the transaction-locked loader atomically moves the snapshot when present plus its segment directory under `tmp/telegram/recovery/`, publishes a fresh empty private journal, records an informational recovery event with the quarantine path, and continues startup; no uncertain files are silently deleted. After the initial snapshot, append, batch completion, queue receipt/owner/handoff, retry/terminal, recovery, and operator dispositions publish only changed upserts/removals and disposition replacement in one segment. This avoids rewriting retained raw updates during completion-heavy drains without splitting exact queue, failure, recovery, or disposition transactions.
 
-Compaction runs under the journal transaction lock when either 256 unapplied segments or 4 MiB of segment bytes is reached. It publishes the complete private (`0600`) snapshot at revision `R` before best-effort deletion of segments `<= R`; failed cleanup leaves redundant segments that readers ignore. Interrupted cleanup therefore leaves either an older snapshot plus newer authoritative segments or a newer snapshot plus harmless redundant older segments. Revision gaps, conflicting duplicates, malformed segments, and identity mismatches fail closed. The logical reconstructed journal and aggregate unapplied segment bytes are independently bounded at 10,000 entries and 32 MiB as applicable; rejected growth publishes neither snapshot nor segment bytes. Compaction may temporarily require exactly one private complete snapshot of at most 32 MiB. Capacity pauses polling and authority files are never automatically deleted, reset, or quarantined.
+Compaction runs under the journal transaction lock when either 256 unapplied segments or 4 MiB of segment bytes is reached. It publishes the complete private (`0600`) snapshot at revision `R` before best-effort deletion of segments `<= R`; failed cleanup leaves redundant segments that readers ignore. Interrupted cleanup therefore leaves either an older snapshot plus newer authoritative segments or a newer snapshot plus harmless redundant older segments. Revision gaps, conflicting duplicates, malformed segments, and identity mismatches fail closed. The logical reconstructed journal and aggregate unapplied segment bytes are independently bounded at 10,000 entries and 32 MiB as applicable; rejected growth publishes neither snapshot nor segment bytes. Compaction may temporarily require exactly one private complete snapshot of at most 32 MiB. Capacity pauses polling and valid authority files are never automatically deleted, reset, or quarantined. Only a missing-snapshot history that cannot be reconstructed safely uses the explicit evidence-preserving quarantine-and-reset compatibility fallback above.
 
 `pending` entries remain immediately executable while raw interception, routing, or grouping is incomplete. Every execution failure becomes `retry-wait` with durable attempt count, next eligible time, failure class, bounded summary, and latest failure time. The `failed` state remains schema-compatible only for legacy candidate journals and is converted to automatic retry during lifecycle startup. `queued` entries carry exact prompt/control receipts plus the acquiring Pi runtime instance, OS pid/birth identity, session generation, acquisition id, and acquisition time. Queueing alone is never completion.
 

package/node_modules/@llblab/pi-telegram/index.ts

@@ -132,6 +132,22 @@ export default function (pi: Pi.ExtensionAPI) {
         getProfileName: configStore.getActiveProfileName,
         getBotToken: configStore.getBotToken,
         getBotId: getTelegramBotId,
+        onRecovery(event) {
+          recordRuntimeEvent(
+            "recovery",
+            event.kind === "repaired"
+              ? "Telegram update journal was repaired automatically."
+              : "Telegram update journal was reset after its damaged files were quarantined.",
+            {
+              phase: "journal-auto-recovery",
+              recoveryKind: event.kind,
+              journalPath: event.path,
+              revision: event.revision,
+              quarantinePath: event.quarantinePath,
+              reason: event.reason,
+            },
+          );
+        },
         getQueueRuntimeIdentity() {
           return {
             instanceId: telegramInstanceId,
@@ -449,6 +465,15 @@ export default function (pi: Pi.ExtensionAPI) {
       BusApi.createTelegramAggregateTypingActionSender(telegramApiRuntime),
     updateStatus,
     isContextActive: telegramSessionContextStore.isCurrent,
+    getTransportAuthority() {
+      if (ownsTelegramDirectDelivery()) {
+        const epoch = getCurrentLeaderEpoch();
+        return epoch === undefined ? undefined : `direct:${epoch}`;
+      }
+      if (!telegramBusFollowerRegistrationState.isRegistered()) return undefined;
+      const generation = telegramBusFollowerRegistrationState.getGeneration();
+      return generation ? `follower:${generation}` : undefined;
+    },
     recordRuntimeEvent,
   });
   const currentModelRuntime = Model.createCurrentModelRuntime({

package/node_modules/@llblab/pi-telegram/lib/journal.ts

@@ -17,7 +17,7 @@ import {
   unlinkSync,
   writeFileSync,
 } from "node:fs";
-import { dirname, join } from "node:path";
+import { basename, dirname, join } from "node:path";
 import { isDeepStrictEqual } from "node:util";
 
 import {
@@ -349,6 +349,14 @@ export type TelegramUpdateJournalPublicationBoundary =
   | "before-write"
   | "after-write-before-rename";
 
+export interface TelegramUpdateJournalRecoveryEvent {
+  kind: "repaired" | "reset";
+  path: string;
+  revision?: number;
+  quarantinePath?: string;
+  reason: string;
+}
+
 export interface TelegramUpdateJournalStoreOptions {
   path: string;
   profileName?: string;
@@ -356,6 +364,7 @@ export interface TelegramUpdateJournalStoreOptions {
   maxEntries?: number;
   maxBytes?: number;
   getNowMs?: () => number;
+  onRecovery?: (event: TelegramUpdateJournalRecoveryEvent) => void;
   queueRuntimeIdentity?: TelegramUpdateJournalQueueRuntimeIdentity;
   getQueueProcessLiveness?: (
     owner: TelegramUpdateJournalQueueProcessIdentity,
@@ -1472,6 +1481,7 @@ export interface TelegramUpdateJournalRuntimeBindingResolverDeps {
   getBotId: () => number | undefined;
   getJournalPath: (profileName?: string) => string;
   getQueueRuntimeIdentity?: () => TelegramUpdateJournalQueueRuntimeIdentity;
+  onRecovery?: (event: TelegramUpdateJournalRecoveryEvent) => void;
 }
 
 export function createTelegramUpdateJournalRuntimeBindingResolver(
@@ -1506,6 +1516,7 @@ export function createTelegramUpdateJournalRuntimeBindingResolver(
         ...(deps.getQueueRuntimeIdentity
           ? { queueRuntimeIdentity: deps.getQueueRuntimeIdentity() }
           : {}),
+        ...(deps.onRecovery ? { onRecovery: deps.onRecovery } : {}),
       }),
     };
   };
@@ -1546,6 +1557,7 @@ export function createTelegramUpdateJournalBindingRuntime(deps: {
       ...(includeQueueRuntimeIdentity && deps.base.getQueueRuntimeIdentity
         ? { getQueueRuntimeIdentity: deps.base.getQueueRuntimeIdentity }
         : {}),
+      ...(deps.base.onRecovery ? { onRecovery: deps.base.onRecovery } : {}),
       getJournalPath(profileName) {
         return deps.getFollowerJournalPath(bindingKey, profileName);
       },
@@ -1601,6 +1613,13 @@ export function createTelegramUpdateJournalStore(
   );
   const getNowMs = options.getNowMs ?? Date.now;
   const onPublicationBoundary = options.onPublicationBoundary;
+  const notifyRecovery = (event: TelegramUpdateJournalRecoveryEvent): void => {
+    try {
+      options.onRecovery?.(event);
+    } catch {
+      // Recovery diagnostics must not break recovered journal authority.
+    }
+  };
   const getQueueProcessLiveness =
     options.getQueueProcessLiveness ?? getTelegramProcessLiveness;
 
@@ -1742,8 +1761,9 @@ export function createTelegramUpdateJournalStore(
     entries: [],
   });
 
-  const readCurrent = (): ReadTelegramUpdateJournalResult => {
+  const readCurrentStrict = (): ReadTelegramUpdateJournalResult => {
     let source: string;
+    let recoveringMissingSnapshot = false;
     try {
       const size = statSync(path).size;
       if (size > maxBytes) {
@@ -1775,15 +1795,14 @@ export function createTelegramUpdateJournalStore(
           );
         }
         if (orphanedSegmentNames.length > 0) {
-          throw createJournalError(
-            "invalid",
-            path,
-            `is missing while ${segmentDirectory} retains revision segments`,
-          );
+          recoveringMissingSnapshot = true;
+          source = serializeJournalFile(emptyFile());
+        } else {
+          return { file: emptyFile(), exists: false, serializedBytes: 0 };
         }
-        return { file: emptyFile(), exists: false, serializedBytes: 0 };
+      } else {
+        throw createJournalError("io", path, "could not be read", error);
       }
-      throw createJournalError("io", path, "could not be read", error);
     }
     let parsed: unknown;
     try {
@@ -1808,6 +1827,9 @@ export function createTelegramUpdateJournalStore(
     segmentNames.sort();
     let revision = file.revision ?? 0;
     let unappliedSegmentBytes = 0;
+    let orphanRecoverySawUpsert = false;
+    let orphanRecoverySawBaseRemoval = false;
+    let orphanRecoveryUnsafe = false;
     for (const name of segmentNames) {
       const nameRevision = Number(name.slice(0, 16));
       if (nameRevision <= revision) continue;
@@ -1871,11 +1893,16 @@ export function createTelegramUpdateJournalStore(
         file.entries.map((entry) => [entry.updateId, entry]),
       );
       for (const updateId of segment.removedUpdateIds) {
+        if (recoveringMissingSnapshot && !entriesById.has(updateId)) {
+          orphanRecoverySawBaseRemoval = true;
+          if (orphanRecoverySawUpsert) orphanRecoveryUnsafe = true;
+        }
         entriesById.delete(updateId);
       }
       for (const entry of segment.upsertedEntries) {
         entriesById.set(entry.updateId, entry);
       }
+      if (segment.upsertedEntries.length > 0) orphanRecoverySawUpsert = true;
       file = parseJournalFile(
         {
           version: TELEGRAM_UPDATE_JOURNAL_VERSION,
@@ -1935,10 +1962,166 @@ export function createTelegramUpdateJournalStore(
       }
       return { file, exists: true, serializedBytes: reboundBytes };
     }
+    if (recoveringMissingSnapshot) {
+      if (
+        orphanRecoveryUnsafe ||
+        !orphanRecoverySawBaseRemoval ||
+        file.entries.length > 0
+      ) {
+        throw createJournalError(
+          "invalid",
+          path,
+          `is missing while ${segmentDirectory} retains revision segments`,
+        );
+      }
+      const recovered = serializeJournalFile(file);
+      const recoveredBytes = assertCapacity(file, recovered);
+      writeJournalFile(path, recovered, onPublicationBoundary);
+      notifyRecovery({
+        kind: "repaired",
+        path,
+        revision: file.revision,
+        reason: "Recovered a missing snapshot from a complete empty segment history.",
+      });
+      return { file, exists: true, serializedBytes: recoveredBytes };
+    }
     const serializedBytes = assertCapacity(file);
     return { file, exists: true, serializedBytes };
   };
 
+  const readCurrent = (): ReadTelegramUpdateJournalResult => {
+    try {
+      return readCurrentStrict();
+    } catch (error) {
+      if (
+        !(error instanceof TelegramUpdateJournalError) ||
+        error.code !== "invalid"
+      ) {
+        throw error;
+      }
+      let snapshotExists = false;
+      try {
+        statSync(path);
+        snapshotExists = true;
+      } catch (snapshotError) {
+        if ((snapshotError as { code?: unknown })?.code !== "ENOENT") throw error;
+      }
+      const segmentDirectory = getTelegramUpdateJournalSegmentDirectory(path);
+      let segmentNames: string[];
+      try {
+        segmentNames = readdirSync(segmentDirectory)
+          .filter((name) => /^\d{16}\.json$/u.test(name))
+          .sort();
+      } catch {
+        throw error;
+      }
+      if (segmentNames.length === 0) throw error;
+
+      if (snapshotExists) {
+        try {
+          const snapshot = parseJournalFile(
+            JSON.parse(readFileSync(path, "utf8")) as unknown,
+            path,
+          );
+          const firstSegmentPath = join(segmentDirectory, segmentNames[0]);
+          const firstSegment = parseJournalSegment(
+            JSON.parse(readFileSync(firstSegmentPath, "utf8")) as unknown,
+            firstSegmentPath,
+          );
+          if (
+            snapshot.revision === undefined &&
+            firstSegment.previousRevision > 0 &&
+            snapshot.profile === firstSegment.profile &&
+            identitiesMatch(snapshot.botIdentity, firstSegment.botIdentity)
+          ) {
+            writeJournalFile(
+              path,
+              serializeJournalFile({
+                ...snapshot,
+                revision: firstSegment.previousRevision,
+              }),
+              onPublicationBoundary,
+            );
+            const repaired = readCurrentStrict();
+            notifyRecovery({
+              kind: "repaired",
+              path,
+              revision: repaired.file.revision,
+              reason: `Recovered a revisionless snapshot from segment revision ${firstSegment.revision}.`,
+            });
+            return repaired;
+          }
+        } catch {
+          // Fall through to evidence-preserving quarantine and reset.
+        }
+      }
+
+      const recoveryDirectory = join(
+        dirname(path),
+        "recovery",
+        `${getNowMs()}-${process.pid}-${randomUUID()}`,
+      );
+      mkdirSync(recoveryDirectory, { recursive: true, mode: 0o700 });
+      const snapshotQuarantinePath = join(recoveryDirectory, basename(path));
+      const segmentQuarantinePath = join(
+        recoveryDirectory,
+        basename(segmentDirectory),
+      );
+      if (
+        snapshotExists &&
+        !renameTelegramPathWithRetry(path, snapshotQuarantinePath)
+      ) {
+        throw createJournalError(
+          "io",
+          path,
+          "could not quarantine an unrecoverable journal snapshot",
+          error,
+        );
+      }
+      if (!renameTelegramPathWithRetry(segmentDirectory, segmentQuarantinePath)) {
+        if (snapshotExists) {
+          renameTelegramPathWithRetry(snapshotQuarantinePath, path);
+        }
+        throw createJournalError(
+          "io",
+          segmentDirectory,
+          "could not quarantine an unrecoverable journal segment history",
+          error,
+        );
+      }
+      const reset = emptyFile();
+      const serialized = serializeJournalFile(reset);
+      const serializedBytes = assertCapacity(reset, serialized);
+      try {
+        writeJournalFile(path, serialized, onPublicationBoundary);
+      } catch (publicationError) {
+        const segmentsRestored = renameTelegramPathWithRetry(
+          segmentQuarantinePath,
+          segmentDirectory,
+        );
+        const snapshotRestored =
+          !snapshotExists ||
+          renameTelegramPathWithRetry(snapshotQuarantinePath, path);
+        if (!segmentsRestored || !snapshotRestored) {
+          throw createJournalError(
+            "io",
+            path,
+            "reset publication failed after journal evidence was quarantined",
+            publicationError,
+          );
+        }
+        throw publicationError;
+      }
+      notifyRecovery({
+        kind: "reset",
+        path,
+        quarantinePath: recoveryDirectory,
+        reason: error.message,
+      });
+      return { file: reset, exists: true, serializedBytes };
+    }
+  };
+
   const runMutation = <T>(operation: () => T): T => {
     try {
       return withTelegramFileTransaction(`${path}.transaction`, operation);

package/node_modules/@llblab/pi-telegram/lib/runtime.ts

@@ -320,6 +320,8 @@ export interface TelegramTypingLoopDeps {
     options?: { message_thread_id?: number },
   ) => Promise<unknown>;
   sendAggregateTypingAction?: (chatId: number) => Promise<unknown>;
+  shouldContinue?: () => boolean;
+  onStopped?: () => void;
 }
 
 export interface TelegramRuntimeEventRecorderPort {
@@ -365,6 +367,8 @@ export interface TelegramTypingLoopStarterDeps<
   sendAggregateTypingAction?: (chatId: number) => Promise<unknown>;
   updateStatus: (ctx: TContext, error?: string) => void;
   isContextActive?: (ctx: TContext) => boolean;
+  isTransportAvailable?: () => boolean;
+  getTransportAuthority?: () => string | number | undefined;
   intervalMs?: number;
 }
 
@@ -376,15 +380,33 @@ export function createTelegramTypingLoopStarter<TContext>(
   options?: { target?: TelegramTypingLoopTarget },
 ) => void {
   return (ctx, chatId, options) => {
+    const transportAuthority = deps.getTransportAuthority?.();
+    const hasTransport = (): boolean =>
+      deps.getTransportAuthority
+        ? transportAuthority !== undefined &&
+          Object.is(deps.getTransportAuthority(), transportAuthority)
+        : deps.isTransportAvailable?.() !== false;
+    if (!hasTransport()) return;
+    let active = true;
     deps.typing.start({
       chatId: chatId ?? deps.getDefaultChatId(),
       target: options?.target,
       intervalMs: deps.intervalMs ?? TELEGRAM_TYPING_ACTION_INTERVAL_MS,
       sendTypingAction: async (targetChatId, actionOptions) => {
+        if (!active) return;
+        if (!hasTransport()) {
+          deps.typing.stop();
+          return;
+        }
         try {
           await deps.sendTypingAction(targetChatId, actionOptions);
         } catch (error) {
           if (deps.isContextActive?.(ctx) === false) return;
+          if (!active) return;
+          if (!hasTransport()) {
+            deps.typing.stop();
+            return;
+          }
           const message =
             error instanceof Error ? error.message : String(error);
           updateTelegramRuntimeStatusSafely(deps.updateStatus, ctx, {
@@ -404,10 +426,20 @@ export function createTelegramTypingLoopStarter<TContext>(
       },
       sendAggregateTypingAction: deps.sendAggregateTypingAction
         ? async (targetChatId) => {
+            if (!active) return;
+            if (!hasTransport()) {
+              deps.typing.stop();
+              return;
+            }
             try {
               await deps.sendAggregateTypingAction?.(targetChatId);
             } catch (error) {
               if (deps.isContextActive?.(ctx) === false) return;
+              if (!active) return;
+              if (!hasTransport()) {
+                deps.typing.stop();
+                return;
+              }
               const message =
                 error instanceof Error ? error.message : String(error);
               updateTelegramRuntimeStatusSafely(deps.updateStatus, ctx, {
@@ -427,6 +459,10 @@ export function createTelegramTypingLoopStarter<TContext>(
             }
           }
         : undefined,
+      shouldContinue: hasTransport,
+      onStopped: () => {
+        active = false;
+      },
     });
   };
 }
@@ -442,7 +478,12 @@ export function startTelegramTypingLoop(
 ): boolean {
   if (deps.chatId === undefined || deps.chatId === 0) return false;
   const previousKey = state.typingLoopKey;
+  const previousDeps = state.typingLoopDeps;
   const nextKey = getTelegramTypingLoopKey(deps);
+  if (previousDeps && previousDeps !== deps) {
+    previousDeps.onStopped?.();
+    state.typingInFlight = undefined;
+  }
   state.typingLoopDeps = deps;
   state.typingLoopKey = nextKey;
   const sendTyping = (): void => {
@@ -450,10 +491,14 @@ export function startTelegramTypingLoop(
     if (
       !activeDeps ||
       activeDeps.chatId === undefined ||
-      activeDeps.chatId === 0 ||
-      state.typingInFlight
+      activeDeps.chatId === 0
     )
       return;
+    if (activeDeps.shouldContinue?.() === false) {
+      stopTelegramTypingLoop(state);
+      return;
+    }
+    if (state.typingInFlight) return;
     const targetChatId = activeDeps.chatId;
     const threadParams = getTelegramTypingLoopThreadParams(activeDeps.target);
     const typing = Promise.resolve()
@@ -486,9 +531,12 @@ export function stopTelegramTypingLoop(
 ): boolean {
   if (!state.typingInterval) return false;
   clearInterval(state.typingInterval);
+  const activeDeps = state.typingLoopDeps;
   state.typingInterval = undefined;
   state.typingLoopDeps = undefined;
   state.typingLoopKey = undefined;
+  state.typingInFlight = undefined;
+  activeDeps?.onStopped?.();
   return true;
 }
 
@@ -571,6 +619,8 @@ export interface TelegramPromptDispatchRuntimeDeps<
   sendAggregateTypingAction?: (chatId: number) => Promise<unknown>;
   updateStatus: (ctx: TContext, error?: string) => void;
   isContextActive?: (ctx: TContext) => boolean;
+  isTransportAvailable?: () => boolean;
+  getTransportAuthority?: () => string | number | undefined;
   intervalMs?: number;
 }
 

package/node_modules/@llblab/pi-telegram/lib/status.ts

@@ -871,9 +871,6 @@ export function buildTelegramStatusBarText(
   state: TelegramStatusBarState,
 ): string {
   const label = theme.fg("accent", getTelegramStatusBarLabel(state));
-  if (state.error) {
-    return `${label} ${theme.fg("error", "error")}`;
-  }
   const queued = state.queuedStatus
     ? theme.fg("success", state.queuedStatus)
     : "";
@@ -885,6 +882,9 @@ export function buildTelegramStatusBarText(
     return `${label} ${theme.fg("warning", "electing")}${queued}`;
   if (!state.pollingActive && state.busRole !== "follower")
     return `${theme.fg("accent", "telegram")} ${theme.fg("dim", "disconnected")}${queued}`;
+  if (state.error) {
+    return `${label} ${theme.fg("error", "error")}`;
+  }
   if (state.processing) {
     const processingStatus = state.queuedStatus
       ? "active"

package/node_modules/@llblab/pi-telegram/lib/telegram-api.ts

@@ -37,6 +37,8 @@ function getTelegramApiTempDir(): string {
   return resolveTelegramTempDir();
 }
 const TELEGRAM_TEMP_FILE_MAX_AGE_MS = 24 * 60 * 60 * 1000;
+const TELEGRAM_TEMP_SCRATCH_FILE_PATTERN =
+  /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}-/u;
 const TELEGRAM_INBOUND_FILE_MAX_BYTES = getTelegramInboundFileByteLimitFromEnv(
   process.env,
   ["PI_TELEGRAM_INBOUND_FILE_MAX_BYTES", "TELEGRAM_MAX_FILE_SIZE_BYTES"],
@@ -1116,7 +1118,9 @@ export async function cleanupTelegramTempFiles(
     return 0;
   }
   for (const entry of entries) {
-    if (!entry.isFile()) continue;
+    if (!entry.isFile() || !TELEGRAM_TEMP_SCRATCH_FILE_PATTERN.test(entry.name)) {
+      continue;
+    }
     const path = join(tempDir, entry.name);
     try {
       const stats = await stat(path);

package/node_modules/@llblab/pi-telegram/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-telegram",
-  "version": "0.36.7",
+  "version": "0.36.10",
   "private": false,
   "publishConfig": {
     "access": "public"

package/node_modules/@llblab/pi-telegram/skills/generated-control-surface/SKILL.md

@@ -54,9 +54,15 @@ Console programs are one capability source, not the defining boundary. Use the r
 
 ## Control Admission
 
-Buttons are optional, but bias toward offering them when they materially shorten a likely feedback loop. If the user can approve, reject, refine, prioritize, redirect, inspect, or choose a concrete next step faster by tapping than by composing a reply, proactively expose the smallest useful control set without waiting to be asked for buttons.
+Buttons are optional only when no candidate passes the admission test. Bias toward offering them whenever they materially shorten a likely feedback loop. If the user can approve, reject, refine, prioritize, redirect, inspect, or choose a concrete next step faster by tapping than by composing a reply, proactively expose the smallest useful control set without waiting to be asked for buttons.
 
-Zero buttons remains preferable when controls would only decorate the answer, restate visible prose, solicit generic “What next?” input, expose an unclear consequence, or save negligible effort. A button earns its place by reducing response effort, ambiguity, turnaround time, or supervision cost while preserving an ordinary typed reply as a first-class option.
+On a Telegram-originated turn, emitting controls is required when the response asks the user for one or more bounded confirmations or choices, the likely answers can be represented truthfully in 2–6 safe controls, and no secret-bearing or high-impact ambiguity blocks their formulation. This includes blocking questions such as confirming scope, version, workflow classification, approval, or the next release step. Ask in prose when explanation is necessary, but attach the controls in the same reply; the availability of free-form typing is not a reason to omit them. A high-impact operation still uses the required confirmation flow rather than a one-tap execution shortcut.
+
+Apply the same requirement at a workflow handoff even when the current user message itself was a complete correction or implementation command. Before concluding a Telegram reply, project the user's likely next intent from the active goal, recent trajectory, newly completed act, and available capabilities—not only from an explicitly pending question. Typical phase transitions include “prepare → release”, “inspect → approve”, “fix → rerun”, and “draft → send”. If one next action or a small alternative set is high-confidence, newly unblocked, truthfully expressible, and safe to request, emit 2–6 controls now instead of waiting for the user to restate the obvious next step. A narrowly completed subtask does not erase the parent intent or make the predictive handoff decorative.
+
+This is anticipatory interaction, not generic suggestion generation. Prefer controls that advance the user's demonstrated workflow over broad capability menus, speculative side quests, or “What next?” buttons. A predicted high-impact action is offered as an explicit self-contained request or confirmation, never silently executed. When confidence is low or materially different next intents compete, omit controls or expose only the smallest clarifying choice.
+
+Zero buttons remains preferable when controls would only decorate the answer, restate visible prose, solicit generic “What next?” input, expose an unclear consequence, save negligible effort, or when the user already issued a complete command and neither that command nor the inferred active workflow leaves a high-confidence immediate decision. A button earns its place by reducing response effort, ambiguity, turnaround time, or supervision cost while preserving an ordinary typed reply as a first-class option.
 
 For status requests, show a compact `Refresh` control and bounded inspect/drill-down controls only when work is active, blocked, stale-sensitive, or otherwise actionable. A completed static status needs no buttons. Do not add destructive shortcuts or actions whose target and consequence are not yet clear.
 
@@ -130,11 +136,11 @@ Use the transport's canonical prompt-button syntax. For pi-telegram, one top-lev
 
 Model the control surface as an ordered ragged sequence of independently sized rows, not as a rectangular matrix to fill. Rectangular grids are one specialization for genuinely spatial or coordinate-bearing state; most interfaces should vary row width according to hierarchy, grouping, label pressure, and action priority.
 
-- Put controls in one compact row only when they are genuine peers that answer the same local question or form one coherent toolbar/navigation group.
-- Use a singleton full-width row for a structurally independent, pinned, primary, summary, or high-consequence action when separation improves comprehension.
+- Default to one full-width button per row for non-spatial controls. Put controls in one compact row only when they are genuine peers that answer the same local question or form one coherent toolbar/navigation group **and** their rendered labels comfortably fit a narrow phone-width chat.
+- Use a singleton full-width row for a structurally independent, pinned, primary, summary, or high-consequence action, and whenever label length makes horizontal grouping cramped or ambiguous.
 - Vary row widths intentionally—for example `1 → 2 → 4 → 1 → 2`—and never pad a row with empty, duplicate, or no-op controls merely to produce uniform dimensions.
 - Preserve reading order across rows: orientation and structural navigation first, primary content or choices next, secondary controls afterward, and destructive actions visibly separated when present.
-- Use at most two columns when buttons carry words, phrases, icon-plus-text labels, or other text that must be read; move additional peer choices into more semantic rows rather than compressing four or more textual buttons across a phone-width line. Three through five columns are for short symbols, glyphs, coordinates, or compact codes whose position carries meaning. Six through eight may be used only for single-glyph or similarly minimal position-bearing labels whose grouping materially improves the interaction. Eight is the phone-width UX maximum: never generate a row of nine or more controls even though the parser has no artificial width cap. Never shorten necessary wording merely to increase row density; regroup or use full-width rows when labels need explanation, wrap ambiguously, or lose meaning without prose.
+- Treat two columns as an earned compact mode, not the default: a pair normally fits when each label is no more than one emoji plus roughly two average-length words. If either label has more words, unusually long words, qualifiers, or likely wrapping, place each button on its own row. Use at most two columns for readable text labels; move additional peer choices into more semantic rows rather than compressing textual buttons across a phone-width line. Three through five columns are for short symbols, glyphs, coordinates, or compact codes whose position carries meaning. Six through eight may be used only for single-glyph or similarly minimal position-bearing labels whose grouping materially improves the interaction; a row of emoji-only controls may therefore legitimately use up to eight columns. Eight is the phone-width UX maximum: never generate a row of nine or more controls even though the parser has no artificial width cap. Never shorten necessary wording merely to increase row density; regroup or use full-width rows when labels need explanation, wrap ambiguously, or lose meaning without prose.
 
 Treat vertical extent independently from horizontal density. A genuinely spatial surface may retain many rows—such as an `8×16` field—when vertical continuity, coordinates, and one-glance topology matter; do not paginate merely to make its height match its width. For non-spatial collections, however, a tall button wall should yield to semantic grouping, progressive disclosure, or pagination. Keep compact state and instructions above a tall surface, preserve stable coordinates across regeneration, and avoid repeating prose between rows.
 
@@ -181,7 +187,7 @@ Button prompts must:
 - Request fresh inspection when state may have changed.
 - Avoid embedding volatile output that should be rediscovered.
 
-Labels stay short, distinct, and scannable. Emoji are optional semantic markers; do not rely on color alone. If buttons are unavailable, render the same control surface as a numbered choice list.
+Labels stay short, distinct, and scannable. Prefer an explicit `label` over exposing a long prompt as button text. Emoji are explicitly allowed and encouraged when one consistent semantic marker improves scanning or expressiveness; keep their meaning consistent across sibling controls, avoid decorative noise, and do not rely on emoji or color alone. If buttons are unavailable, render the same control surface as a numbered choice list.
 
 ## Capability Adapters
 
@@ -230,6 +236,8 @@ Buttons may represent explicit alternatives without live system inspection. Stat
 
 Before sending a surface, verify:
 
+- If the reply asks a Telegram user for bounded confirmation or selection, qualifying controls are present; do not ship a prose-only blocking question merely because the answer is short.
+- If the completed act unblocks a high-confidence next intent inferred from the parent goal and workflow trajectory, qualifying handoff controls are present even when no explicit pending question exists and the latest user message was itself a complete command.
 - State and controls share one clear owner and target.
 - Live claims come from current evidence.
 - Complete versus filtered or adapted output is labeled honestly.