[charleslpan]

Stacked on #3919. The newest page of a task's plan version history is now pushed to the window through main's central live layer. The list is no longer re-read on every task-record editedAt while the history is open.

What changed

• Service. live.taskHistory (GET /api/live/task-history?id=) serves one statement (task-history-live.ts). It reads what listRevisions reads for the newest page:

  • PAGE + 1 revisions, picked by a subquery;
  • joined to user, coding_agent, the call, and the revision a restore brought back;
  • membership as a join.

  It goes through sealedParts, so it is sealed or held-polled. It checks sameUser.

• Shared label. UNKNOWN_AGENT_LABEL moves to task-wire, so the reader names a missing agent the way the store does.

• Tests.

  • A PGlite parity test against listRevisions. It covers a call save, an agent save, a developer save, a restore, and a history past one page. A stranger reads nothing.
  • An endpoint test.
  • The immutability and seal tests.

• Host. client.historyLive, a host follow with tasks.historyChanged, and an eventIterator procedure tasks.historyFollow, the same shape as the pages follow.

• Window. usePlanHistory reads the newest page once, then takes the stream through the source's followNewest.

  • Older pages stay a one-off service read.
  • The plan template's history follows nothing and reads once.
  • editedAt no longer re-reads the list.

• Restore wait dropped. There's no transaction-id wait; that work was dropped with feat(host): liveRows hands out a TxWait for a write's transaction (P4) #4230.

Checks run locally

Typecheck, lint, knip and repository-checks all pass. Vitest across the affected areas passes (4257 tests).

Made with Luke

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
luke-web	Ready	Preview	Oct 21, 2026 5:07am UTC