# Parent comparison: image 059

Parent: /root, local task 01a0e067-c27c-77f2-a3f9-ec52a44b62cf. Fresh describer: /root/blind_059, gpt-6-luna high, forked with no conversation context. Its only evidence input was this image. Parent read the completed description and verified the image checksum.

[Actual screenshot](../inputs/059.png) · [Independent description](../descriptions/059.md)

Variant B. Captured action: Return from another customer restores both unsaved drafts. URL: https://kertujitok-proposal-b-20260927.clientsflowdigital.workers.dev/panel/proposals/?proposal=p_aaee89436be27231c745a649b6e521db9d5fe0e2d80c26179f76b4c098dfbc85. Screenshot SHA256: `590940143f36f40c52fa6a0401a86aaf47ab6a83640aac71f1c6e50681255185`.

- C23: When a save fails or another session changes the same proposal, then the user sees a clear unsaved/conflict state with a recoverable path and their typed values are not silently lost.

**Parent comparison:** The independent description sees both the restored unsaved proposal draft and unsaved customer sheet after B's dirty switch, with current 422,200 Ft and retained fields. This is intentionally an unsaved recovery state. The actual switch-away/return receipt verifies typed values survived, and later explicit saves/readbacks verify final persistence. It is not treated as saved merely because a previous version number is displayed.

[Completed GUI journeys and exact behavioral evidence](../../deployed-gui/scenario-matrix.md). Full criterion acceptance also requires the other applicable states and nonvisual checks. A screenshot alone does not prove persistence, timing, arithmetic or downloaded bytes.