Quality and coverage failures

Symptoms

Benchmarks report insufficient editorial coverage, unexpected difficulty distribution, low uniqueness, or a changed quality baseline.

Likely causes

• The theme’s metadata is stale.
• A word list is narrow or concentrated in one difficulty lane.
• A deliberate engine change altered the baseline.
• The benchmark was run with different dates, cache state, or runtime configuration.

Investigation and resolution

Run content-cli analyze, content-cli refresh, and the benchmark with a fixed report directory. Compare the runtime fingerprint and report inputs. If the change is intentional, update the baseline and explain why; otherwise improve the theme or investigate the ranking/strategy change.