Analyzing Jellyfin PR #16062 with GauntletCI

Jellyfin PR #16062 is titled "Query Performance Improvements." It was a massive architectural shift: 126 files, 27,810 lines of code. It was reviewed, approved, and merged on May 3, 2026.

By May 7, the community was already reporting 90-second query hangs (Issue #16279).

We ran GauntletCI: a deterministic, rules-based Behavioral Change Risk (BCR) detector: against the merged diff. It took exactly 660 ms to find exactly why the "Performance Improvement" was causing performance degradation.

The Gap Between Intent and Reality

In a 27,000-line diff, human review is a suggestion, not a safeguard. The maintainers intended to fix N+1 query patterns. They succeeded in some areas, but the sheer scale of the change made it impossible to see what was being introduced simultaneously.

1. The Performance Traps (GCI0044)

Findings: 28 LINQ-in-loop patterns.

The Reality: While the PR closed older performance issues, it introduced 28 new ones.…