From 167f82a9466929c97b9241d1050e49960d797d41 Mon Sep 17 00:00:00 2001
From: Copilot <223556219+Copilot@users.noreply.github.com>
Date: Sun, 2 Aug 2026 01:42:08 -0700
Subject: [PATCH] DOC Correct scenario baseline parameter guidance

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 4b171813-5be5-487b-91c6-188b938319cd
---
 doc/code/scenarios/0_scenarios.ipynb | 7 ++++---
 doc/code/scenarios/0_scenarios.py    | 7 ++++---
 2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/doc/code/scenarios/0_scenarios.ipynb b/doc/code/scenarios/0_scenarios.ipynb
index c25cd3481b..c96b9b1abd 100644
--- a/doc/code/scenarios/0_scenarios.ipynb
+++ b/doc/code/scenarios/0_scenarios.ipynb
@@ -437,9 +437,10 @@
     "\n",
     "Every scenario can optionally include a **baseline attack** — a `PromptSendingAttack` that sends\n",
     "each objective directly to the target without any converters or multi-turn techniques. This is\n",
-    "controlled by the `include_baseline` parameter on `initialize_async`; when omitted, each\n",
-    "scenario falls back to its own `BASELINE_ATTACK_POLICY` class attribute (most scenarios default\n",
-    "it on; `Jailbreak` defaults it off). See\n",
+    "controlled by the `include_baseline` scenario parameter, supplied through the CLI, config, or\n",
+    "`set_params_from_args` before `initialize_async`; when omitted, each scenario falls back to its\n",
+    "own `BASELINE_ATTACK_POLICY` class attribute (most scenarios default it on; `Jailbreak` defaults\n",
+    "it off). See\n",
     "[Common Scenario Parameters](./1_common_scenario_parameters.ipynb) for a worked example.\n",
     "\n",
     "Custom scenarios should choose their `BASELINE_ATTACK_POLICY` based on whether an unmodified\n",
diff --git a/doc/code/scenarios/0_scenarios.py b/doc/code/scenarios/0_scenarios.py
index db143ed444..459fb6754f 100644
--- a/doc/code/scenarios/0_scenarios.py
+++ b/doc/code/scenarios/0_scenarios.py
@@ -178,9 +178,10 @@ async def _build_atomic_attacks_async(self, *, context):
 #
 # Every scenario can optionally include a **baseline attack** — a `PromptSendingAttack` that sends
 # each objective directly to the target without any converters or multi-turn techniques. This is
-# controlled by the `include_baseline` parameter on `initialize_async`; when omitted, each
-# scenario falls back to its own `BASELINE_ATTACK_POLICY` class attribute (most scenarios default
-# it on; `Jailbreak` defaults it off). See
+# controlled by the `include_baseline` scenario parameter, supplied through the CLI, config, or
+# `set_params_from_args` before `initialize_async`; when omitted, each scenario falls back to its
+# own `BASELINE_ATTACK_POLICY` class attribute (most scenarios default it on; `Jailbreak` defaults
+# it off). See
 # [Common Scenario Parameters](./1_common_scenario_parameters.ipynb) for a worked example.
 #
 # Custom scenarios should choose their `BASELINE_ATTACK_POLICY` based on whether an unmodified