[hhkaos]

Closes the last reader-side item in #13 — and the premise there was wrong, which is the finding.

The reader already pruned, silently

boardEvents() resolved every {feedUrl, eventId} against the live feed:

return allEvents().filter(function (event) {
  return refs.some(function (item) { return sameRef(item, eventRef(event)); });
});

So a saved event whose publisher stopped carrying it left the collection
without a word, and the pointer stayed in localStorage aimed at nothing.
Reproduced before fixing: two events in Favorites, the publisher removes one,
Actualizar → Favorites · 1 evento, no message. Unsubscribing from a feed did
the same to every saved event from it.

And it did this for any absence — aged out, cancelled, recycled id,
truncated response, changed URL. None of those is "withdrawn".

Who it hits: eventos.wiki publishes 485 events and Sarao 180 — publishers who
prune are exactly these. The collection that suffers most is "Mis charlas",
which by definition accumulates past talks.

What changed

• A collection holds the event, not a pointer. The live event still wins
  while the feed carries it (it may have been edited); the saved copy is the
  fallback instead of nothing. Pre-existing pointers are backfilled from the
  feed as it loads.
• Mark, never remove. With the card no longer vanishing there is something
  to mark, and covers decides whether the absence means anything: inside the
  window a feed declares complete, "Retirado del feed"; outside it, or without
  covers, nothing. A feed still loading, failed, or truncated claims nothing
  either. Events from an unsubscribed feed get "Feed no suscrito".
• Cleanup in Ajustes, with a count and a confirmation, scoped to what can
  no longer be followed: unsubscribed feeds, withdrawn events, and
  pre-snapshot pointers with nothing left to point at.

Two UX calls, both deliberate

No "remove past events". A saved past event is the only history this
reader has — the feed no longer carries it — and it is the one a reader asked
for by name. "Solo futuros" already keeps them out of lists, which is a view,
not a deletion.

No preference toggle. Whether an absence means removal depends on each
feed's covers, which the reader cannot see. A setting here would hand the
user a decision the data already answers.

Verification

End to end in a browser: legacy pointers backfill; a pruned event survives and
is badged only when covers covers its date; an event before covers.from
survives unbadged; unsubscribing badges all three "Feed no suscrito"; the
cleanup removes exactly those and the summary goes empty; saving a new event
through the picker writes a snapshot with savedAt.

_{Aside, filed while testing: a value outside the attendanceMode enum makes <ote-events> throw and render an empty widget rather than degrading. My test data was invalid, but one malformed event blanking the whole list is worth reporting upstream.}

🤖 Generated with Claude Code