Run records integrating tasks, results, reports, and reuse

[quinCode]

Run records integrating tasks, results, reports, and reuse

Parent

PRD #14: Run workspace usability rewrite

What to build

Replace separate task history and results surfaces with operator-facing run records. A run record should aggregate one run's status, configuration summary, progress, result availability, report links, and reusable configuration action.

The operator should no longer manually correlate a task with a result file or report. Result viewing, report generation, and reuse configuration should be reached from the relevant run record.

Acceptance criteria

• The 运行记录 region lists recent run records with status, configuration summary, progress/result availability, and key actions.
• A selected run record shows task status, progress summary, result table access, report links, and reuse action where available.
• Result viewing is reachable from the relevant run record and remains backed by the generated API client.
• Report generation gives immediate feedback and stores links on the relevant run record UI.
• Reuse configuration loads values into the RunDraft and marks validation stale.
• Empty state, loading state, error state, and hidden/restored record behavior are Chinese and local to the run records region.
• Frontend tests cover run record list, selecting a record, viewing results, generating reports, reusing config, and empty/error states.

Blocked by

• Issue 0018: Sample-level progress console with debug drawer

[quinCode]

Dependency note: blocked by #21.