Every change to this project’s spec, in order. Specsight syncs, manual edits, and annotations.
The project overview "what changed" card widened from a weekly to a monthly window with weekly sparkline bars, and the recent activity feed now folds Specsight syncs in alongside manual edits and annotations.
The changelog toolbar lost the time-range filter — the page now relies on source filtering, search, and pagination.
The 90-day window before data is purged was deliberately long. Specs are knowledge that compounds; a team that lapses for a month, then comes back, should be able to pick up where they left off without losing context. Shorter windows protect us; this one protects them.
Plans rebalanced — Standard, BYOK, Partnership — paired with a scheduled-lock workflow that gives organisations 90 days to recover before data is purged.
Only the prefix is stored after creation — the rest of the key is a one-way hash. If a key is lost there is no recovery: delete it, generate a new one, paste it into the AI tool. Painful, but the only safe option.
Mobile navigation, the dashboard tab layouts, and the Feedback modal landed — bringing the touch experience in line with the desktop refresh.
Notifications fan out — in-app first, then email. The in-app one always fires; the email only follows if the member has mention emails on. Keeps urgent signals visible even when someone has muted their inbox.
The Feedback experience grew up — admin triage replies and a history page joined the original modal-only flow, with attachments and email updates when a submission gets a response.
In-app notifications launched — a bell menu now collects every notification type that previously only arrived by email; mention notifications fan out to both surfaces with a clear preferences split.
The changelog is append-only by design. Even when Specsight later reverses a scenario it added in a previous sync, the original entry stays. We want every change to remain permanently traceable.
The integrations tab was renamed from API Keys to MCP, with OAuth as the recommended setup path. The legacy generic API-key flow for scripts was retired in favour of the AI-tool-focused MCP one.
Markdown joined the export choices, and single-feature exports landed. Expanding a sync entry on the changelog now opens a per-feature, per-scenario change view with before-and-after wording.