Convert the active batch with isolated results and retry

[Andesha]

Parent

#192

What to build

Extend Recording to BIDS to process the active manifest and Configuration as a best-effort batch while preserving the established single-recording conversion experience. Users can move through individual recordings and inspect or adjust applicable settings, while batch execution processes every ready recording independently.

A failure must not roll back successful recordings or attempt unresolved rows. Report success or failure per recording and allow selective retry of failed recordings after preflight is refreshed. The Batch workbench does not own execution or results.

Acceptance criteria

• Recording to BIDS accepts only the active versioned manifest plus current Configuration.
• Users can navigate and inspect individual recordings using the existing Recording to BIDS workflow.
• Ready recordings are processed independently and unresolved or conflicting rows are skipped.
• One recording failure does not prevent other ready recordings from succeeding.
• Each attempted recording receives a clear success or failure result with useful error context.
• Users can retry only failed recordings without duplicating successful outputs.
• Retry refreshes output preflight before writing.
• Conversion outcomes do not silently mutate the source manifest; any future resumable job state remains a separate explicit artifact.
• Automated coverage verifies mixed success/failure batches and idempotent selective retry behavior.

Blocked by

• Ticket 5 — Validate and preview the batch in the conversion workflow.