# Parent comparison: image 009

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

Variant A. Captured action: Lost-response retry reopened created proposal with linked sidebar. URL: https://calendar-stage-20260923.cfd-staging.com/panel/proposals/?proposal=p_aaee89436be27231c745a649b6e521db9d5fe0e2d80c26179f76b4c098dfbc85. Screenshot SHA256: `af2c2a6be2905efadc59f3813e1dbd4adf6d597ca902c8df9449cf742f804396`.

- C05: When Péter creates a proposal for a new synthetic customer and repeats the save after a simulated retry, then exactly one CRM contact and one linked proposal exist and the editor opens.
- C06: When Péter chooses an existing CRM contact with a proposal, then its proposal link reopens that record instead of creating a duplicate. When it has no proposal, Create makes and opens its first proposal.
- C19: When a lead is opened from any lead-card/contact entry point in the proposal flow, then a side panel shows editable lead business information, original enquiry, own note, reminder date, work-delivery date, calendar-note visibility and proposal property.

**Parent comparison:** The independent description identifies the retry customer's editor at saved version 1, matching customer sidebar and zero-value unused template. The successful linked editor is the visual counterpart to the prior lost-response form in 008. Completed post-contact/pre-link fault and concurrent retry receipts establish exactly one contact and proposal, not the green notice alone. Technical linked IDs and entry paths are checked in the GUI/API readback.

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