Skip to main content

0.8.6 — Reading the record instead of the JSON

Released 2026-08-11.

Every release keeps two snapshots: what it contained when it was handed over, and what it contained when it was delivered. They answer one question — did anything change in between? Until now they answered it in about 260KB of raw JSON, which is to say they did not answer it at all.

What's new​

Snapshot comparison on the release view. The Snapshots tab now shows a comparison instead of two data dumps. It opens with a plain verdict — "Release content did not drift" or "Release content drifted" — and then shows you the working:

  • Change table — stories, requirements, total issues and open issues on both sides, with the movement, plus the issue breakdown by HIGH / MEDIUM / LOW severity.
  • Quality gate side by side — each check with its result and detail from both snapshots. A check that ran on only one side reads Not recorded, never Failed; a check that did not run is not a check that failed.
  • Every story listed — requirement, title, the revision on each side, and whether it changed. Changed and unchanged alike, so you can see what you are being told about.
  • Raw JSON still there, collapsed at the bottom, for when you need it.

Content drift and analysis drift are kept apart. Issue counts almost always move between handover and delivery, because analysis carries on after a release is handed over. That is not the release changing. The comparison reports it as its own line and never lets it reach the drift verdict, so "1,552 issues became 2,754" and "nothing was rebuilt" can both be true on the same screen.

Bug fixes​

  • Snapshot text no longer renders smaller than the rest of the page.
  • Where only one snapshot exists — the normal state for a release in progress — the page now explains that, rather than showing a lone unexplained block.
  • A snapshot that is unreadable or missing a section no longer blanks the page. What can be read is shown, and a warning names what could not be.

Behind the scenes​

  • The comparison is derived entirely on the server. No snapshot data is sent to the browser for processing.
  • Correctness work on the regression suite: several test-infrastructure defects were repaired, including one that could delete builder-feedback records during a test run.

Upgrade notes​

None. This release adds no database changes and no configuration. Existing snapshots are read as they are — nothing is rewritten, regenerated or migrated.