Question
What should the editable review table — where Core Team fixes AI extraction mistakes before the rows flow into the existing diff-schedule review — look and behave like?
To resolve via /prototype (HITL — build a rough UI to react to):
- Inline cell editing vs row-drawer editing for
artists / set name / stage / date / start time / end time?
- How multi-artist sets (pipe-separated) are edited without the separator being a foot-gun.
- Add-row / delete-row for sets the model missed or hallucinated.
- How per-image provenance is shown when a run merges several images (e.g. "from photo 2").
- Where the optional "Download CSV" affordance sits.
- How this step visually joins the existing wizard (
CsvUploadStep → review → DiffReviewStep).
Part of wayfinder map #179.
Question
What should the editable review table — where Core Team fixes AI extraction mistakes before the rows flow into the existing diff-schedule review — look and behave like?
To resolve via /prototype (HITL — build a rough UI to react to):
artists/set name/stage/date/start time/end time?CsvUploadStep→ review →DiffReviewStep).Part of wayfinder map #179.