fix(tasks): correct the change-feed contract and its documentation

Review found the `onTasksChanged` teardown reasoning inverted. The comment
claimed every registration is an effect on the registry's own fiber, so
listeners would be gone before service disposal empties the store — but the
traceable proxy rebinds `this.ctx` to the CALLER, which this package's own
HMR-safety test already proves. The only shipped consumer registers from the
api-proxy mux stream, so it was still listening and simply kept the rows it
last received. Service disposal now announces the emptied set, and teardown
announces its stopping transition immediately instead of leaving an observer
on `running` for however long a slow producer takes to release.

Two documentation claims were false in the opposite direction: the Agent Note
and the ui-task README both said an unowned task is invisible in the header,
while `list(caller)` returns unowned tasks to every caller, the carrier fans
their changes out to every subscribed session, and this PR's own test asserts
exactly that. The note even contradicted itself two sections earlier. Both
sides now state the real asymmetries — another session's tasks, and the
process-local registry emptying on restart.

The "no Web path calls the consuming `ctx.tasks.read()`" invariant claimed a
test that did not exist; the carrier suite's producer had no `readOutput` at
all, so a stray read would have failed nothing. Its producer now counts cursor
consumption and the lifecycle and baseline paths both assert zero.

Also: a session created after the mux opened now receives the task baseline it
missed, the popover samples its clock when it opens rather than at mount, and
a failed task's unbounded producer detail elides instead of widening the row.

packages/client/ui-task/src/client/TaskListAction.module.css

@@ -111,6 +111,15 @@
   line-height: 18px;
 }
 
+/* A failed task's detail is the producer's raw error text, so it has no bound;
+   without this it widens the row past the menu instead of eliding like .label. */
+.status {
+  max-width: 40%;
+  overflow: hidden;
+  white-space: nowrap;
+  text-overflow: ellipsis;
+}
+
 .duration {
   font-variant-numeric: tabular-nums;
 }

packages/client/ui-task/src/client/TaskListAction.tsx

@@ -148,7 +148,14 @@ export function TaskListAction({ sessionId, useSessions, t }: TaskListActionProp
         className={css.trigger}
         aria-expanded={open}
         aria-label={countLabel}
-        onClick={() => { setOpen(current => !current) }}
+        onClick={() => {
+          // Sample the clock in the same commit that opens the list: the
+          // mount-time value predates every task, so the first painted frame
+          // would otherwise clamp a long-running row to zero until the
+          // open effect corrects it a frame later.
+          setNow(Date.now())
+          setOpen(current => !current)
+        }}
       >
         {liveCount > 0 ? <StateDot state="ongoing" className={css.triggerDot} /> : null}
         <span className={css.count}>{countLabel}</span>
@@ -167,7 +174,7 @@ export function TaskListAction({ sessionId, useSessions, t }: TaskListActionProp
                   <StateDot state={dotState(task.status)} className={css.rowDot} />
                   <span className={css.kind}>{task.kind}</span>
                   <span className={css.label} title={task.label}>{task.label}</span>
-                  <span className={css.status}>{task.detail ?? status}</span>
+                  <span className={css.status} title={task.detail ?? status}>{task.detail ?? status}</span>
                   <span
                     className={css.duration}
                     title={t(live ? 'duration.title.live' : 'duration.title.done', { duration })}