# Parent comparison: image 026

Parent: /root, local task 01a0e067-c27c-77f2-a3f9-ec52a44b62cf. Fresh describer: /root/blind_026, 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/026.png) · [Independent description](../descriptions/026.md)

Variant A. Captured action: Offline proposal save failed with typed quantity retained. URL: https://calendar-stage-20260923.cfd-staging.com/panel/proposals/?proposal=p_9b7954858811812947a65a4b721cbdf5505942bbd71ee49751577d0db7b3a2f7. Screenshot SHA256: `dc993efde1bf46f371d40dd04d5b069ea699ad6273788984be6ce6e3c8a7a7c8`.

- 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 reads A's failed-save banner saying typed values remain and instructing a retry with Mentés. It also observes the separate PDF-worker loading error caused by the offline injection. This is intentionally failure evidence, not a pass-looking screenshot. The retained quantity/current total and later conflict merge/reload prove recovery; the known PDF recovery limitation remains explicitly disclosed.

[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.