Save and load a versioned batch manifest

[Andesha]

Parent

#192

What to build

Give the Batch workbench a final Review & handoff surface and make its primary output a versioned batch manifest. The review surface summarizes manifest completeness and provides the two explicit workbench actions: save the manifest to a file or load the same serialized representation directly into Configuration. Configuration can also open a previously saved manifest and establish it as the active batch without rerunning discovery, canonical prefilling, or user-defined mappings.

The review surface is a manifest review, not conversion preview. It may show participant and recording counts, included/excluded and ready/unresolved recordings, and manifest validation problems. It must not select an output directory or modality, propose BIDS destinations, run output preflight, or claim which recordings will convert; those responsibilities belong to Configuration and Recording to BIDS.

The manifest describes recordings and their explicit assignments; dataset-wide conversion settings remain owned by Configuration and are not duplicated into every recording row.

Acceptance criteria

• The workbench has a final Review & handoff tab or section summarizing participant and recording counts, included/excluded state, readiness, and manifest validation problems.
• The review surface provides a Save batch file action.
• The review surface provides a Load into Configuration action.
• The review surface contains no output-directory, modality, destination-preview, collision-preflight, or conversion controls.
• The workbench can save a versioned manifest containing source recordings, companion files, explicit recording assignments, participant linkage and demographics, inclusion/readiness state, and optional assignment provenance.
• The workbench can load the manifest directly into Configuration without requiring an intermediate file selection.
• Configuration can open the same serialized manifest format from disk.
• In-memory handoff and file loading use one schema and produce equivalent active-batch state.
• Reopening reconstructs the batch from saved explicit assignments without rerunning discovery, prefilling, or mappings.
• Saved mappings may be retained for audit or deliberate reuse, but are not required to reconstruct final assignments.
• Missing or changed source files are reported per recording rather than preventing the manifest from opening.
• Loading or changing Configuration does not silently rewrite the source manifest.
• Automated coverage verifies schema versioning, file round trips, equivalent direct handoff, and missing or changed source handling.

Blocked by

• Ticket 4 — Correct batches through bulk editing and participant review.

[Andesha]

Direction clarification: preserve the useful final workbench tab as a Review & handoff surface. It summarizes the manifest and hosts Save batch file / Load into Configuration, while conversion-specific preview and preflight remain in #197.

[Andesha]

Implemented on the umbrella branch in draft PR #200. This will land with the remaining #192 sub-issues. The current CI failure is an unrelated PyPI timeout in pip-audit and can be rerun before final review.