MAINT Breaking: Rename Scenario Strategies to Techniques

[rlundeen2]

Summary

Renames the scenario-layer strategy → technique vocabulary for the 1.0 release. The CLI already selects techniques (the --strategies flag chose techniques), and the codebase already uses AttackTechnique / AttackTechniqueRegistry — ScenarioStrategy was the lone holdout. This aligns the naming end-to-end.

This is a hard break with no backward-compatibility aliases (intended for 1.0).

Key changes

• ScenarioStrategy → ScenarioTechnique (base enum + module rename)
• Scenario technique enums: Foundry/Cyber/Leakage/RapidResponse/Benchmark/Adversarial/TextAdaptive/Psychosocial*Strategy → *Technique
• Params/registry: scenario_strategies/strategy_converters → scenario_techniques/technique_converters; _resolve_strategies_and_converters → _resolve_techniques_and_converters
• Models/API (JSON fields): strategies, strategies_used, default_strategy, aggregate_strategies, all_strategies → techniques, techniques_used, default_technique, aggregate_techniques, all_techniques; ScenarioResult.get_strategies_used() → get_techniques_used()
• CLI: --strategies/-s → --techniques/-t
• Docs (scanner + scenarios + resiliency notebooks) and scenarios.instructions.md updated

Explicitly NOT touched (deferred)

Executor AttackStrategy/attack_strategy, WorkflowStrategy, PromptGeneratorStrategy, converter *SelectionStrategy, and StrategyResult are unrelated concepts and are preserved.

Verification

• In-scope unit suite green; executor/converter safety suite green
• ruff lint + format clean; ty check pyrit clean
• CLI --help shows --techniques, -t; repo-wide sweep confirms no dangling old scenario symbols

End-to-end / live testing (nothing broken)

Ran the scanner path against a live OpenAI target and exercised the renamed API surface:

• doc/scanner/1_pyrit_scan.ipynb — executed end-to-end (start-server → --list-scenarios/--list-initializers → real foundry.red_team_agent --techniques base64 scan → custom ScenarioTechnique subclass → stop-server). 0 cell errors; output shows the renamed vocabulary (scenario_techniques, technique_converters, techniques: N/N progress).
• Direct CLI scan foundry.red_team_agent --target openai_chat --initializers target --techniques base64 — completed cleanly (Total Techniques: 2, per-group baseline / base64 breakdown).
• doc/scanner/foundry.ipynb — executed the programmatic scenario + output_scenario_async rendering path. 0 cell errors (Scenario: RedTeamAgent, Atomic attacks: 2, Total Techniques: 2).
• Renamed-enum smoke check — with the registry initialized, resolved every renamed technique enum used across the scanner notebooks and confirmed get_all_techniques() / get_aggregate_techniques() work: FoundryTechnique, RapidResponseTechnique, PsychosocialTechnique, CyberTechnique, JailbreakTechnique, LeakageTechnique, ScamTechnique, EncodingTechnique, DoctorTechnique, WebInjectionTechnique.

Also fixed a stale scanner-doc flag surfaced during testing: --scenario-techniques → --techniques (the doc referenced a non-existent flag).