[witbrock]

Outcome

Attachment readiness now comes from each draft attachment's lifecycle. Removing an unfinished upload releases Send immediately, even before its batch promise settles; late success/error responses cannot restore the removed attachment. Failed uploads offer retry/removal, and retry completion updates both status and gating. All selected files are registered before yielding so none can escape the gate.

The supplied screenshot contains two distinct PDFs: a ready poster and an uploading programme. It does not establish that the programme upload completed. This change repairs the demonstrated stale batch-gate mechanism and retains the correct gate while another attachment is genuinely uploading.

Validation

• 28 tests passed across chatAttachmentWorkflowInput, conversationImageRecovery and conversationVisuals: completion/send, mixed ready/uploading PDFs, failure/retry, removal/cancellation, duplicate and late settlement, conversation isolation, request retry and metadata binding.
• Changed-file frontend static lint and git diff checks passed.
• Chromium component check passed using the actual attachment module and local fixture transport (node tests/browser/attachmentLifecycle.cjs). Evidence retained in .run/attachment-lifecycle/. This is component acceptance, not authenticated backend or public upload acceptance.

Merge decision: ready for the bounded lifecycle/gating claim. No deployment requested.

Von task: #V#task_agent_a847f5aa3de30eaf7453b7ccbaf19fce.
Source screenshot: #V#computer_file_copy_c54e96b78e0c4f58ab8665bab8209db4, SHA-256 c46f4480c94fe297d706abb339c05b8fef9f6b3c31aeaff40cd62cbfe291af36.