# Two-tab work draft acceptance

WJ-058 uses two real pages in one isolated Chromium context. After creating a work entry through the form, both tabs edit that entry with distinct hours and descriptions. The first tab saves. The second reloads, opens the entry and must recover its own input while showing the currently saved version.

A normal save from the second tab must report a conflict and leave the first tab's persisted values unchanged. Clicking Continue with my draft explicitly accepts the displayed base version, but still does not write anything. Only the subsequent Save work action may persist the second draft. The fixture checks the rendered form and the actual H2 work_entry after each boundary, including that only one record exists.

The browser performs all writes through the real UI. Database access in these steps is read-only verification; no cookies or draft storage are copied or injected. Mail is captured by the isolated test server. No production data is touched.

Validation passed for 0.1.41-SNAPSHOT: all five browser scenarios; 178 executed JVM cases (194 reported, 16 pending acceptance cases skipped), zero failures/errors; 68 operations tests, 17 frontend tests and production/admin-recovery smoke checks. The initial test query was corrected to read its selected columns by index because H2 returns uppercase field names. No production change was necessary.