[Bug]: Composer image attachments are marked non-persisted due to premature draft storage verification

[UtkarshUsername]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

1. Start the app.
2. Open any thread in the web or desktop app.
3. Attach an image in the composer.
4. Observe the orange warning badge on the image.
5. Refresh.
6. See if the image persisted.

Expected behavior

Attached images should be persisted in composer draft storage when local storage is available. The warning badge should appear only when persistence actually fails.

Actual behavior

The composer verifies persisted attachment IDs before the debounced draft write has flushed to storage. As a result, image attachments can be marked as non-persisted even when storage is healthy, which shows the orange warning badge and makes draft recovery unreliable.

Impact

Major degradation or frequent failure

Version or commit

0.0.13

Environment

No response

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response