[DRAFT] FEAT Normalize simulated conversation prompt sources

[hannahwestra25]

Description

Work on #2494 highlighted a gap in the shared factory API: benchmark- or scenario-owned adversarial prompts may already exist as SeedPrompt objects, but with_simulated_conversation() only had a path-shaped input. That forced callers to keep prompt files coupled to the shared technique catalog or add one-off adaptation around the benchmark.

This PR pulls that general capability out as an independent change based directly on main. The preferred adversarial_chat_system_prompt input now accepts either an inline SeedPrompt or an explicit pathlib.Path. The factory resolves either form immediately and stores the canonical inline prompt, so #2494 and similar callers can own prompt content without moving prompt packaging into executors or changing persistence semantics. Plain strings are intentionally not accepted by the preferred input because non-path prompt APIs use strings for inline text; legacy string paths remain supported through adversarial_chat_system_prompt_path.

The old path-named parameter remains a silent compatibility alias for this first step, and direct or persisted legacy path-backed SeedSimulatedConversation records still execute normally. The other simulated-conversation *_system_prompt_path inputs stay unchanged here because generalizing them requires separate model, persistence, and execution compatibility work. This PR does not depend on #2494 or change AdversarialBenchmark itself.

Tests and Documentation

• 397 focused and adjacent unit tests passed
• Ruff check/format, ty, async-suffix, compile, and diff checks passed
• Jupytext paired sources and round-trip checks passed
• Updated the attack-techniques documentation pair

[Richard Lundeen (rlundeen2)]

I love that you found this! It's a legit gap

However, I want to normalize to SeedPrompts, I've put some effort into going this direction and away from file paths. One of the biggest reasons is in terms of attack generation. I want to easily see techniques and modify them (e.g. change some words in a system prompt) and that's tricky with file paths.

Instead of the fix you have here, can we can go towards only accepting the SeedPrompt and deprecating the file path route?

[Richard Lundeen (rlundeen2)]

E.g.

• Make adversarial_chat_system_prompt: SeedPrompt canonical—not SeedPrompt | Path.
• Load YAML with SeedPrompt.from_yaml_file(...) at setup/composition boundaries.
• Carry only SeedPrompt through SeedSimulatedConversation, AttackParameters, and the executor.
• Keep *_path only as a deprecated compatibility adapter and for reading legacy database records.