# Expected Diagnosis: classify-selected-stores-as-tikv-or-tiflash

This ad-hoc case evaluates current store-role classification for a mixed set of
live storage stores from one cluster.

The runtime hooks first resolve a recent stable snapshot, then dynamically pick
a mixed list of current active stores that includes both TiKV and TiFlash. The
expected agent response should:

- classify each selected store as either `tikv` or `tiflash`
- avoid treating TiFlash stores as TiKV stores
- emit exactly one JSON code block with the required fields:
  `cluster_id`, `evidence_sufficient`, `stores`
- avoid extra explanatory prose outside that JSON block
- preserve the same store order as the prompt input list
- return the same cluster id and per-store component roles as the runtime
  reference

The judge intentionally avoids hard-coding specific store ids in static YAML.
The exact store list and reference roles are built from live runtime evidence.