[szibis]

#581 was merged while behind main, just after the v1.88.0 metadata sync (#604). Its head predated the cut, and the merge placed its seven entries inside the released ## [1.88.0] section and left ## [Unreleased] empty, so:

• the CHANGELOG says v1.88.0 contains the series-limit changes; it doesn't — v1.88.0 was cut from feat(conformance): generate the roadmap and matrix from the registry, and enforce it in CI #594;
• the release bot sees an empty [Unreleased] and will not cut a release for fix: answer metric queries over the series limit like Loki instead of cutting them silently #581.

This restores [1.88.0] to exactly what the release commit (036bd874) published — verified byte-for-byte from ## [1.88.0] down — and lists the seven entries under [Unreleased] / ### Fixed. The set of entries in the file is unchanged; only their section moves.

Same repair as #602. The changelog gate cannot catch this one: it ran on #581 against the base it was cut from, where the entries were correctly under [Unreleased]; the misplacement happens only when a branch that is behind a release is merged without being brought up to date.

[github-actions]

PR Quality Report

Compared against base branch main.

Coverage and tests

Signal	Base	PR	Delta
Test count	7398	7398	0
Coverage	89.9%	89.9%	0.0% (stable)

Compatibility

Track	Base	PR	Delta
Loki API	100.0%	11/11 (100.0%)	0.0% (stable)
Logs Drilldown	100.0%	17/17 (100.0%)	0.0% (stable)
VictoriaLogs	100.0%	11/11 (100.0%)	0.0% (stable)

Performance smoke

Performance smoke was skipped for this PR because no perf-sensitive paths changed.

State

• Coverage, compatibility, and sampled performance are reported here from the same PR workflow.
• This is a delta report, not a release gate by itself. Required checks still decide merge safety.
• Performance smoke was intentionally skipped because no perf-sensitive paths changed in this PR.
• Delta states use the same noise guards as the quality gate (percent + absolute + low-baseline checks), so report labels match merge-gate behavior.