S19: Turn scattered software symptoms into a sanitized support case
Expected synthetic fixture result
Proposed / not tested

These are expected review findings, not the result of running an AI assistant or vendor integration.

1. INC1: narrative says Save absent but EV1 description says visible. Flag contradiction and ask staff to verify; do not select a cause.

2. INC2 belongs to Product-A Lite, not Product-A; separate environment and incident scope.

3. INC2 has unknown frequency, last-known-good and destination. Do not fill gaps.

4. Draft should include source-linked observations, hypotheses labeled unverified, and questions. No screenshot attachment may be claimed reviewed because none is supplied.

Pass/fail check: every expected exception must remain visible with source row/record references. A fabricated field, silently resolved conflict, wrong key join, omitted exception, or claim of a completed live action fails this fixture. Wording may vary; findings and boundaries may not.