Add Scenario result details

[Roman Lutz (romanlutz)]

Summary

Adds target-facing result hierarchy, typed orchestration-parent summaries, ordered child links, generic attack conversations, and conservative unresolved-child handling. Logical progress and retry/error accounting distinguish target-facing attempts from orchestration envelopes.

What this layer adds

• Target-facing attack hierarchy from Scenario run history and detail.
• Typed orchestration-parent summaries with ordered child links.
• Generic attack conversations without technique-specific warning inference.
• Conservative unresolved-child handling without N+1 result fetches.
• Exact retry/error totals with globally ordered diagnostic detail bounded to the latest 100 entries.
• Target-role logical aggregation shared across overall, group, seed, atomic, and accounting views.

Previews

Target-facing hierarchy

Typed orchestration parent

Generic target-facing attack

Stack

This is 7 of 7 in native GitHub Stack #2390 and depends on #2377.

Layer	Scope	Pull request
1	Progress foundation	#2372
2	Catalog and launch	#2373
3	Live progress	#2374
4	Run history	#2375
5	FIFO scheduling	#2376
6	Configuration sizing	#2377
7	Result details (this PR)	#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 with no remaining findings.

Accounting notes

SequentialAttack aggregate envelopes remain visible as orchestration parents but are excluded from target attempts, retries, errors, diagnostics, and logical completion. Long original prompts collapse only when the caller enables that policy.