Every change to this project’s spec, in order. Specsight syncs, manual edits, and annotations.
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.
Whether a repository fits a plan is now judged on its source code alone — repositories with years of version history but modest source no longer read as too large.
Quiet releases now leave a mark — when a review finds no product behaviour changed, the changelog shows a calm "Specsight reviewed" line with a one-sentence reason instead of staying silent. Runs of reviewed releases collapse into a single expandable group, and a project whose latest merge changed nothing reads "Reviewed" on the dashboard.
Ask Specsight is now open to every organisation — the Coming soon gate is gone, so anyone on the team can ask from the project overview, the Ask area in the project rail, or the Command-K palette. The daily question limit and the locked-organisation block still apply, and Ask stays in beta for now.
In-product Specsight Help arrived — open it from the Help button and ask in plain language how to use Specsight, anywhere in the dashboard. Answers come from the help articles with a link to the article behind each one; Admins can also ask about their plan, subscription status, and remaining usage. Project questions hand over to that project's Ask.