# Expected Diagnosis: representative-business-slow-queries-in-premium-cluster-during-latest-window

This ad-hoc case checks whether the agent can identify the three most important
business slow queries for the commonly used `the primary premium cluster` cluster during the latest
completed Beijing `11:00-11:05` window.

The runtime hooks resolve the latest completed daily Beijing `11:00-11:05`
window at execution time and compute the reference directly from
`clinic_data_proxy.slow_query_logs`.

The runtime reference:
- filters out transaction or control statements such as `COMMIT`,
  `START TRANSACTION`, `BEGIN`, `ROLLBACK`, `SET`, `USE`, and `SHOW`
- ranks remaining slow-query digests by:
  1. `exec_count` descending
  2. `avg_time_s` descending
  3. `digest` lexicographic ascending

The final answer must be a single JSON code block with:
- `cluster_id`
- `window`
- `evidence_sufficient`
- `slow_queries`

Each `slow_queries[]` item must contain only:
- `digest`
- `exec_count`
- `avg_time_s`