feat(ui): call the list view Checklist

"Ending soon" described the sort, not the job — and it sat one line above a
sort control whose own option reads "Ending soonest", so the tab and the
ordering looked like the same control said twice. Checklist is what a reader
with four games is doing with it.

The stored id stays "soon". That value is in `prefs.view` on real devices, and
a label is copy: renaming one must never move a reader to the other view.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

docs/PRD.md

@@ -86,11 +86,15 @@ back through and that pushed every other bar off to the right. An event older th
 its faded left edge rather than being redrawn as though it started at the edge — the same honesty
 the frayed right edge carries for an unannounced end.
 
-**F2 — Ends-soonest list.**
+**F2 — Checklist (the ends-soonest list).**
 A flat list of all *currently running* events sorted ascending by end date, with a relative
 countdown ("ends in 2 days", "ends in 4 hours"). Under 24 hours, the row is emphasized. This is the
 view that justifies the app, and it is one tap from the timeline.
 
+The tab reads **Checklist**, which is what a reader with four games is doing with it: working down a
+list of jobs with deadlines. Its stored id stays `"soon"` — that value is in `prefs.view` on real
+devices, and renaming a label must never move a reader to the other view.
+
 **Which view opens is the reader's answer, not ours.** This spec said "calendar (default)" and the
 app shipped opening on the list; both were a decision made on the reader's behalf and then forgotten
 on every reload. So the first run asks (F8) and the answer is stored in `prefs.view`. The list is