feat: surface task execution progress across Host Agent and Cloud

Host Agent now persists step-level execution detail locally (via a real TaskMetadataStore/Timeline wired into TaskRunner) and reports a bounded in-progress snapshot piggybacked on lease renewal. Cloud persists that snapshot per active assignment and exposes it through the existing task list/detail query path; Cloud Console renders it as a live badge. Host Agent's local console gains authenticated, read-only task list and detail/timeline pages (same-origin, server-rendered) with inlined screenshots. Also fixes a pre-existing gap in the shared Timeline: the actual per-step LLM prompt is now recorded instead of the task goal, benefiting both Runtime and Host Agent consoles. When a host uses the cloud planner transport, each decide call's prompt and resulting tool decision are durably logged in a new planner_decision_log table (with bounded retention) and browsable from Cloud Console; direct-transport hosts explicitly surface a "not reported" state. Includes Alembic migrations 0008 (progress columns on scheduled_tasks) and 0009 (planner_decision_log), bounded Host-Agent-local retention, dual-backend repository parity, and Vitest + pytest coverage. Task 6.5 (manual end-to-end device verification) remains. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-07-14 12:47:49 +08:00
parent c049c3c1b1
commit ec261d57c2
59 changed files with 3801 additions and 122 deletions
@@ -0,0 +1,52 @@
+import type { TaskListItem, TaskStatus } from "./types";
+
+/**
+ * Statuses that represent an actively executing assignment, where live
+ * in-progress step information is meaningful to surface.
+ */
+const ACTIVE_STATUSES: ReadonlySet<TaskStatus> = new Set<TaskStatus>([
+  "assigned",
+  "dispatched",
+]);
+
+/**
+ * Format a task's latest in-progress step snapshot for inline display.
+ *
+ * Returns `null` when:
+ * - the task is not actively executing (queued, done, failed) — terminal/queued
+ *   status always wins over a stale progress snapshot; or
+ * - no progress has been reported yet (`progress_step_index` is null/undefined
+ *   or `progress_step_status` is missing).
+ *
+ * Otherwise returns a compact string like `"step 2 — running: tapping button"`.
+ * The summary is truncated to a display-friendly length with a Unicode ellipsis
+ * when it exceeds the limit.
+ */
+export function formatTaskProgress(
+  task: Pick<
+    TaskListItem,
+    | "status"
+    | "progress_step_index"
+    | "progress_step_status"
+    | "progress_summary"
+  >,
+  maxSummaryLength = 120,
+): string | null {
+  if (!ACTIVE_STATUSES.has(task.status)) return null;
+  if (
+    task.progress_step_index === null ||
+    task.progress_step_index === undefined ||
+    !task.progress_step_status
+  ) {
+    return null;
+  }
+  const summary = task.progress_summary ?? "";
+  const trimmed = summary.trim();
+  const display =
+    trimmed.length > maxSummaryLength
+      ? `${trimmed.slice(0, maxSummaryLength - 1).trimEnd()}\u2026`
+      : trimmed;
+  return `step ${task.progress_step_index} \u2014 ${task.progress_step_status}${
+    display ? `: ${display}` : ""
+  }`;
+}