Add Scenario run history

[Roman Lutz (romanlutz)]

Summary

Adds filterable durable Scenario history with target, configuration, timing, work, success, retry, and error summaries plus provenance-preserving navigation. Legacy or malformed stored plans degrade to readable legacy summaries rather than making run detail fail.

What this layer adds

• Filterable, paged Scenario run history and durable run detail.
• Target, configuration, timing, work, success, retry, and error summaries.
• Provenance-preserving navigation into attack conversations.
• Tolerant history/detail readability for legacy or malformed plans while progress validation stays strict.
• One canonical run-state list for selection and URL parsing, including QUEUED.

Preview

Stack

This is 4 of 7 in the Scenario GUI dependent PR stack and depends on #2374.

Layer	Scope	Pull request
1	Progress foundation	#2372
2	Catalog and launch	#2373
3	Live progress	#2374
4	Run history (this PR)	#2375
5	FIFO scheduling	#2376
6	Configuration sizing	#2377
7	Result details	#2378

See the full implementation, screenshots, walkthrough, validation, and operational notes.

Validation

• Backend: 15,212 passed, 120 skipped.
• Frontend: 68/68 suites, 1,286/1,286 tests; lint, TypeScript, and production build passed.
• Mock E2E, retries disabled: 91 passed, 0 failed, 0 skipped.
• Seeded E2E, retries disabled: 62 passed, 0 failed, 0 skipped.
• All configured pre-commit hooks passed; distinguished-engineer review approved the final stack.