✨ Authenticated Iteration - Allow authenticated users to provide feedback and reprocess a dashboard with version history

Cc: @suiyangqiu @yaqi-lyu @calumjs @joshbermanssw
Hi Team!

🟥 Watch the video (1 min 26 sec)

Pain

Reports may contain issues or missing context, but there’s no way to authenticate who is viewing them, nor a structured way for users to provide feedback or request a better reprocessing of the same recording.

Acceptance Criteria

1. Signed-in users must be able to leave feedback/comments on a report.
2. A report must provide a “Reprocess” action that allows entering an additional prompt.
3. Reprocessing must create a new report version (e.g., V1, V2, V3).
4. Users must be able to select a report version from a dropdown.
5. Each version must show what changed compared to the previous version.

Screenshot

Thanks!

No files, tests, or implementation entry points are named. Start by locating the report view, authentication flow, report-processing path, and persistence model in the repository; then map feedback, reprocessing, version selection, and change display to those areas. Done means signed-in users can complete all five acceptance criteria with persisted report versions.