v2.7.1

A hotfix for a crash that made v2.7.0 unusable. Upgrade immediately if you are on 2.7.0.

Fixes

• Opening any issue in the web UI crashed the page. The issue view showed "Something went wrong" instead of the issue, on every issue, on every instance. Loading an issue clears the comments on screen and then reads how many are loaded, to decide whether a later background refresh should reconcile the whole thread or just fetch the newest page. Those two steps landed in the same reactive effect during the 2.7.0 comment-windowing work, so the effect depended on state it had just written, re-ran itself, and hit Svelte's update-depth limit before anything rendered. The count is now sampled without subscribing to it. Page detail was never affected, and no data was involved: nothing was written, lost, or corrupted.
• A failed route no longer disappears without a trace. The error boundary shows the reader a deliberately generic message and, until now, discarded the underlying exception entirely, so a route that failed on every load left no record in the console or anywhere else. It is still never shown in the UI; it is now logged for whoever is diagnosing it.