Give a reader their own events back

An event of theirs that had ended was on no surface at all. Every list and
the board drop a row once its end has passed, and settings only counted the
events a game held rather than naming them — so a one-off became unreachable
the day it finished: impossible to edit, and impossible to delete out of a
store nothing else can see. Repeating events escaped only because their
occurrences roll forward.

So settings names them now, under the game they were filed against, each row
opening the same detail sheet a row on the front page does. Nothing about
how they are managed changes; what was missing was the way back to them.

Two things the index has to get right or it leaves the same hole it closes.
The lists hold occurrences, never rules, so a repeating rule's own id opens
nothing — nearestOccurrence bridges that, and answers for a finished series
too by falling back to the first occurrence, since a rule whose `until` has
passed would otherwise be exactly as stuck. And an event filed under a game
we track has no row of theirs to nest under; the form allows that, so those
get their own heading rather than trailing the list and reading as though
they belonged to whichever game came last.

Each row says why it is not on the front page — ended and when, or its
cadence — because a list of bare titles leaves you guessing which of two
entries is the dead one.

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

README.md

@@ -210,6 +210,11 @@ carry no source link because there is no page to send a sceptic to, and they
 travel in your export. Like everything else here, your browser holds the only
 copy.
 
+Settings lists everything you have added, whatever state it is in, and opens
+the same panel a row does. Every other surface drops an event once it has
+ended, so that list is the only way back to a one-off of yours after its end
+date passes — to edit it, or to get rid of it.
+
 ### How often it comes round
 
 An event you add states its **cadence** — asked before any date, because the