[adamjohnwright]

No spec: test fixtures and the replay harness. Moves the e2e recordings from Release 97 to Release 98, as the beta backend now serves.

What changed

• The whole suite re-recorded against Release 98. Release 97's saved release files are removed, and so are two orphan recordings (tests renamed long ago, the only ones still saying 97).
• Replay keys a request's query with its parameters in order. The site asks for one pathway's details with the same parameters in two orders, from two services, and which one a test makes depends on timing; replay aborted the order it had not recorded. The probes' .api.json keys are normalised on load, and check-har uses the same key. A unit test covers it, seen failing without the sort.

Tests the move needed

• A new analysis result for the seven tests that read one: the Release 97 result was removed with the release.
• Circadian clock's illustration lost its <foreignObject> in Release 98, so the "a figure that cannot be made says so" test puts one back.
• The dragged-tissue test holds its submission unanswered: it is about the stepper.
• The legacy-link tests back out mid-load; the reads they abandon join check-har's ABANDONED list.
• Stubbed answers say release 98.

Checks moved, with reasons

• known-problems.json: six totals up. Compared kind by kind with main, all but one are kinds main already counts. The routes have more recorded answers (3–4 more on three, 1 more on the reaction exporter), and Release 98's objects are larger. The one new kind is a releaseStatus field in a pathways/low/entity answer, which the site's type does not list (1 instance).
• schema.spec: no recorded search answer holds a deleted object's entry any more (Release 97 offered two for TP53; Release 98 offers none for anything the tests ask), so that entry kind is no longer covered by recorded data.

Also

• A test that the render page's reaction view carries no analysis (set aside from Render page, from #771's review: one "not here", the reaction's analysis, tested scrubbing #772 for this move).
• The render failure message drops a host written in capitals (unit test seen failing first).

Local results: 424 passed, 0 failed, 7 skipped. One of those skips was caused by the key change; it is fixed and the test passes. Release 97's last skipped count was 6.

🤖 Generated with Claude Code