# Parent comparison: image 021

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

Variant A. Captured action: Desktop sidebar dates and notes while main quantity is also dirty. URL: https://calendar-stage-20260923.cfd-staging.com/panel/proposals/?proposal=p_9b7954858811812947a65a4b721cbdf5505942bbd71ee49751577d0db7b3a2f7. Screenshot SHA256: `c94439569922769bb554fd39c4df6682244d04be78252cc4b8eefa283ab5a8da`.

- 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.
- C20: When the integrated sidebar is open at desktop and 390 px viewport widths and Péter edits a sheet cell or uses the list behind it, then the underlying UI remains visible and interactive and both sets of edits survive saving/reopening without overwriting unrelated fields. On narrow screens, use a resize/collapse or split workspace rather than a modal takeover.
- C21: When Péter edits either note, the reminder date, work-delivery date or calendar-note checkbox and reloads, then the same values appear in the integrated sidebar and the existing CRM fields retain their intended meanings.
- C22: When the three sidebar design links are opened, then three distinct usable arrangements appear, each demonstrating expand/collapse, editable fields and non-blocking interaction. Two standalone pages clearly state that edits are demo-only.

**Parent comparison:** The description sees the integrated desktop sidebar beside an editable quantity cell with caret, both notes/date/visibility areas and an unsaved main proposal. This is the actual simultaneous-edit state, not a saved or finished-preview claim. The completed GUI save/reload verifies both main and customer edits, while 022 and later mobile images show persisted fields. This integrated design is also the first of the three C22 arrangements; its persistence is distinguished from the two labelled frontend demos.

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