Changelog

The project overview's What changed card now ranks the nine most-changed features in three columns, with counts in place of sparklines and dates.

When an organisation's own AI key stops working, Specsight now says so. A banner appears on every page of the project, each Admin gets an email and an in-app notice naming the reason, and billing explains what to fix with a Check again button. Analysis restarts on its own once the key works.

Every feature's diagram is now a user flow: the screens people move through, the actions on the arrows between them, and the checks and responses along the way, with the scenarios behind any part of it one click away. New scenarios no longer ask to be placed; Specsight redraws the flow itself.

Recent activity on a project now shows releases Specsight reviewed with no changes; consecutive reviewed releases collapse into one entry so real changes stay visible.

An over-limit repository is no longer a dead end. Onboarding, the new project form, the partial-analysis banner, and Analyse again now show what was measured against your limit and offer a request for a higher limit, answered within a day. The old codebase-too-large page is gone.

A release notes draft is now one stack of blocks: Enter starts a new one, '# ' or '- ' in an empty paragraph changes its type, and any block drags into place. Enhance rewrites a single paragraph or list rather than a whole section, and a voice's structure is described in your own words.

Teams can now publish customer-facing release notes: pick the changes worth announcing, Specsight drafts them in a named voice you control, then publish to a shareable public page. Draft release notes links now sit on every release, the sync email, and the project overview, and new emails cover a draft being ready and a set going live.

internal security hardening

Signup confirmation, magic-link, and password-reset emails now land on a one-click confirm page instead of acting the moment the link opens, so inbox security scanners can no longer use up a link before the user clicks it.

Digest emails now carry the digest itself — the change counts, the written intro, and the Key changes and Worth knowing highlights land in the inbox, not just a link.

The Reports feature is now called Digests everywhere in the product, and each digest opens as a single readable page — a summary, the key changes, and collapsible sections for the underlying releases and full change list — instead of the old two-tab layout.