Never run two turns into one, and say when a session waits on its own work

A turn started by something with no row of its own -- a subagent reporting
back, a peer message the CLI only owns up to at the end -- met the previous
reply with nothing between it, and the fold grew that reply rather than
starting a new one. Two answers were drawn as one paragraph, running together
mid-sentence with not even a space between them. The fold now refuses to grow
a settled reply, and `joinPages` carries the same rule across a page boundary.

The other half is the row. `Event::TaskNote` records a background task
reporting back -- a subagent that finished, or a backgrounded command -- with
its title, how it ended and what it said; `TaskNoteRow` draws it as a card,
since somebody said this, and its own row rather than an update to the Task
call's, which is above everything the session has said since. Reported once
however many of the CLI's two lifecycle shapes arrive.

`SessionStatus::Waiting` is a session whose own turn is over while work it
started is not. `Idle` means "waiting for a person" and this means the
opposite, so reporting it as idle sent a "finished" notification at the one
moment that was untrue. Drawn as "waiting" in `waitingColor`; the queue and
the held-command boundary release on either end-of-turn status, so a message
sent while a subagent runs is not held until it finishes.

And a usage limit the account hits inside a subagent now reaches the session
as well as the subagent's transcript. `resume.rs` can only schedule against a
session, and a background Task outliving its parent's turn is the ordinary
case, so auto-resume was doing nothing at all for it.

The status word and its colour were two `when`s on two screens, and the second
missed `waiting` silently; they are `sessionStatusWord`/`sessionStatusColour`
now. Echo's `/subagent n` reproduces the whole shape, staggered a second
apart. Verified on the emulator against the sandbox: 169 server tests, ktfmt,
clippy, rustfmt, Android lint and the JVM unit tests all clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

server/src/session/mod.rs

@@ -2525,11 +2525,15 @@ fn notification_for(
 ) -> Option<NotificationKind> {
     match (was, now) {
         (_, SessionStatus::AwaitingInput) => Some(NotificationKind::AwaitingInput),
-        (SessionStatus::Running | SessionStatus::Compacting, SessionStatus::Idle)
-            if unread == 0 =>
-        {
-            Some(NotificationKind::Finished)
-        }
+        (
+            SessionStatus::Running | SessionStatus::Compacting | SessionStatus::Waiting,
+            SessionStatus::Idle,
+        ) if unread == 0 => Some(NotificationKind::Finished),
+        // Nothing for a turn that ended into `Waiting`. The session stopped
+        // talking, but a subagent it started is still working and will make it
+        // talk again -- "finished" there is the announcement arriving at the
+        // one moment it is not true. The `Waiting` -> `Idle` above is the same
+        // work actually ending, and that is where it is said.
         _ => None,
     }
 }
@@ -2651,7 +2655,7 @@ async fn pump(
                         state: SessionStatus::Running,
                     } if turn_start.is_none() => turn_start = Some(entry.seq),
                     Event::Status {
-                        state: SessionStatus::Idle | SessionStatus::Exited,
+                        state: SessionStatus::Idle | SessionStatus::Waiting | SessionStatus::Exited,
                     } => turn_start = None,
                     _ => {}
                 }
@@ -2660,8 +2664,12 @@ async fn pump(
                 // idle session and goes out rather than queueing behind
                 // itself.
                 match &entry.event {
+                    // `Waiting` alongside `Idle`: both mean the CLI's own turn
+                    // is over and it will accept a command, and holding one
+                    // until the last background task reported back would sit
+                    // on it for as long as that task takes.
                     Event::Status {
-                        state: SessionStatus::Idle,
+                        state: SessionStatus::Idle | SessionStatus::Waiting,
                     } => commands.take_one(),
                     Event::Status {
                         state: SessionStatus::Exited,