Say who the game is waiting on, and move the Fedora; replay in words

Three items folded into the unshipped v0.7.9.

WAITING ON (reported by Jesse from play). The status line said "nobody —
the Division is running itself" while the game was stopped on the
Superintendent. Frame.actor carried clock.currentActor, which is null
for the whole Mainline Phase, so all three interruptions — §8.1's
clearance ruling, Gitea#5's Yard Office offer, Gitea#19's Red Flag
prompt — reported that nobody was holding it up. actingPlayer had the
answer since the Gitea#5 refactor; the Frame threw it away. It carries
actingPlayer now, plus a new `awaiting` field naming the question and
the train: "waiting on Bob · a clearance ruling · Train 4". Naming the
person alone is not enough when three different things can be pending.

THE FEDORA (TODO #29) rides at the right-hand end of the phase row
instead of a line of its own, and wraps under rather than squeezing the
chips.

THE DEVELOPER REPLAY (TODO #34) printed "loss — revenueFloor", the same
defect Gitea#16 was filed about, still alive because nothing
player-facing pointed at it. panels.ts's reasonSentence is exported and
shared rather than reimplemented, fed the last recorded frame and
stripped of markup. The drift test maps win/loss to won/lost so it still
checks the two AGREE rather than that they are spelled alike.

Also carries the previous, unsigned commit's work: the two setup screens
worded the same section by section.

877 tests pass, ten new.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AdG46Ja2PEDBkpqiDazMoX

TODO.md

@@ -168,8 +168,10 @@ pass as 19-21 and 24 above, and all three are answered by Gitea#18 rather than f
 28. **INVESTIGATE: move the game's settings off the top line and into a card of their own** — and
     show ALL of them, not the four that fit. Reasoning in Display below.
 
-29. **Put the Fedora at the right-hand end of the phase row**, with (or in) the Supervisor Shift
-    pill. Reasoning in Display below.
+29. ~~**Put the Fedora at the right-hand end of the phase row**~~ — done 2026-08-30 in v0.7.9. It
+    rides at the end of the phase row now, and wraps under it rather than squeezing the chips on a
+    narrow screen. Went in beside the "waiting on nobody" fix below, since both are the top few rows
+    of status that Jesse asked to have re-looked at as a whole.
 
 Queued 2026-08-25, from releasing 0.7.1 / 0.4.9g. **Both are blocked on the two commits being made
 and pushed** — they were still uncommitted when the session ended.
@@ -218,7 +220,12 @@ Queued 2026-08-29, from building Gitea#11 and #16 (both shipped in v0.7.3, main
     rather than recorded, a second pass can add any of them retroactively to games already played and
     saved. Needs Jesse and a conversation, not code, to start.
 
-34. **`replay.ts` prints a raw outcome enum, exactly as the results screen used to.** Its summary
+34. ~~**`replay.ts` prints a raw outcome enum, exactly as the results screen used to.**~~ — done
+    2026-08-30 in v0.7.9. `panels.ts`'s `reasonSentence` is exported and shared, fed the last
+    recorded frame and stripped of markup; the drift test now maps `win`/`loss` to `won`/`lost` so
+    it still checks agreement rather than spelling. Original note below.
+
+    **`replay.ts` printed a raw outcome enum, exactly as the results screen used to.** Its summary
     line is `` `${o.result} — ${o.reason}` ``, which renders "loss — revenueFloor" — the same defect
     Gitea#16 was filed about, in the dev-side replay viewer rather than the playable page. The
     sentences now exist (`panels.ts`'s `reasonSentence`), but they are written against a `Frame` and
@@ -359,6 +366,16 @@ Queued 2026-08-29, from building Gitea#11 and #16 (both shipped in v0.7.3, main
     fields and confirmed the dealt game matches what was chosen. Worth being an early item in the
     next play session, alongside #39's four unplayed v0.7.4 features.
 
+43. ~~**"Waiting on" said nobody while the game was stopped on the Superintendent.**~~ — done
+    2026-08-30 in v0.7.9. Reported by Jesse from play. `Frame.actor` carried `clock.currentActor`,
+    null for the whole Mainline Phase, so all three interruptions (clearance, Yard Office, Red Flag)
+    reported that the Division was running itself. It carries `actingPlayer` now and a new
+    `awaiting` field says what the question is and which train it is about.
+
+    **Worth knowing for the next Frame field:** the engine had the right answer in `actingPlayer`
+    since the Gitea#5 refactor, and the Frame simply did not carry it. A view that reads one field
+    of `clock` directly is a place this can happen again.
+
 ---
 
 ## Replay / Save Games