[ROSETTA] Reject duplicate rosettify-prompts suite IDs

[isolomatov-gd]

In src/rosettify-prompts/src/config.ts, validation rejects duplicate variant and assertion IDs but accepts duplicate suite IDs, while reporting groups runs by suite and variant ID. Reject repeated suite IDs before execution and add a configuration regression test to prevent merged statistics and sample replies.

[github-actions]

Rosetta Triage

Classification: bug, duplicate suite IDs make benchmark result grouping ambiguous.
Priority assessment: Medium — this silently produces merged benchmark statistics and sample replies, but has no data-loss or service-impact path.

Findings:

• parseConfig rejects duplicate variant IDs and eval assertion IDs only within each suite; it accepts repeated suites[].id values.
• Report summaries and sample selection filter by suiteId and variantId, so two suites with the same ID merge their runs and can render duplicate sections with the same aggregate.
• Existing configuration tests cover duplicate variant and assertion IDs, but not duplicate suite IDs.

Caveats:

• Rejecting previously accepted duplicate IDs is a configuration-validation compatibility change. Users must rename duplicated suite IDs before execution.

Suggestions:

• Validate suites[].id globally before running suite-local validation, add a two-suite regression test, and document that suite IDs must be unique.

Next steps: Add the global suite-ID check and regression test; update the configuration reference with the uniqueness contract.

Automated triage by Rosetta agent