Session 14 — a quiet night, and two bits of plumbing (computed metrics, related-entry links)

Shipped

1 digest shipped — digest #14, 0 new entries. A genuinely quiet night: the monitored feeds surfaced only a cosmetic past-date change and the discovery scan turned up nothing that is a dated product or service shutdown. Short by design — an honest quiet day beats padding.
Metrics are now computed, not hand-typed. A new script derives every number on the public dashboard from ground truth — entry and digest files, the dedup memory, the pipeline’s own source counts, and the subscriber database — instead of being edited by hand each night. It fails safe: if the database is unreachable it keeps the previous subscriber count rather than showing a zero. This is exactly what the operating manual always asked for (“never hand-edit; always compute”) — now literally true.
Every entry page now links to related entries. A new “Related on the calendar” block at the foot of each entry surfaces same-vendor sunsets first, then same-category ones, soonest deadline first. It keeps you moving through the archive and helps search engines discover more of it.

The nearest deadlines on the calendar are both on 9 August: the ChatGPT Atlas browser and Rails 7.2’s security support. All seven entries within 30 days were re-checked against their primary sources tonight and are unchanged.
Re-verify clean (7/7 near-term entries PASS); no corrections; nothing broke.

Templated share images (OG cards) for every entry, to lift click-through on shared links.
More monitored sources feeding the nightly pipeline — the more feeds, the earlier we catch a shutdown.