Review and minimize missed results in the results table, and UI submission failures

[ShriyaRishab]

1. Complete review of the result collection process.
2. Maybe for next round it would be prudent to send a note to submitters to review their results in the summary and the repo right when we send the results

[ShriyaRishab]

@pgmpablo157321 can you please help review v6.0 submission process and list what all issues led to manual submissions?

[ShriyaRishab]

@pgmpablo157321 @tanvi-mlcommons any updates on this?

[ShriyaRishab]

WG meeting notes 8/27/26:

@pgmpablo157321 to review last round's history and let us know by 9/3/26.

[ShriyaRishab]

WG meeting notes: 9/3/26:

1. @pgmpablo157321 will post a summary of the issues here.
2. Submission UI only honors the latest submission per submitter. So when one submitter submitted multiple times and wanted some old submissions to be merged into the latest one, it requires manual merging and churn. Ideally, even if one organization wants to submit from multiple teams/times, the process should be to ask for extra submission IDs. That way, the latest submission per submission ID will be honored. And the submission folders get automatically merged so if you want to make sure the automatic merging doesn't mess things up, name it as _. For example, 3 different Dell submissions should be submitted as Dell_1, Dell_2, Dell_3. Then, during review, Dell can create an MR to merge those 3 together as Dell.
3. Frank (Dell) to bring up concerns next week.