# Expected Diagnosis: inconsistent-query-result-with-subquery

The expected result should converge on the case-specific mechanism below while
keeping conclusions bounded by the collected evidence.

## Expected conclusion

A TiKV StreamAgg correctness defect lost an unfinished final group when a result exceeded the 32 MiB response boundary and continued on another page. In the NOT IN DISTINCT plan this made one value disappear from the subquery result and allowed an extra outer row. Removing DISTINCT or forcing HASH_AGG avoids the faulty path.

## Required evidence chain

- Rule out index/table inconsistency using the fixed snapshot and admin-check evidence.
- Identify the TiKV StreamAgg boundary/pagination defect that drops an unfinished group.
- Explain why the lost subquery value makes NOT IN return one extra row.
- Recommend removing redundant DISTINCT or forcing HASH_AGG until the fixed build is available.