DOC Document attack outcomes and scenario resiliency

[romanlutz]

Summary

• document the two independent axes of attack execution health and objective outcome in the Scenario resiliency guide
• clarify that handled model refusals are persistable, scorable completed responses rather than execution failures
• add a Mermaid flow covering target responses, retries, scoring, completed and incomplete objectives, partial failures, and Scenario run states
• expand undersized Mermaid diagrams into the right margin with MyST col-page-right and refine layouts to prevent clipping, crossings, and overlaps

Before and after

Screenshots use the same 1366px browser viewport. Before is main at 630061a80; after is this PR at 24dea2a5b.

Page	Before	After
Framework architecture
Multi-turn attack flow
Scoring architecture blog
Memory schema
Scorer hierarchy
Combining scorers
Attack technique selection
Scenario outcomes and resiliency

Validation

• uv run jupyter-book build --html
• Jupytext round-trip checks for synchronized notebooks
• file-scoped pre-commit hooks
• rendered Mermaid clipping and geometry audit