From b75eb512eac6b7a217c86ead83d8530744f3af10 Mon Sep 17 00:00:00 2001
From: gamer147 <gamer147@gmail.com>
Date: Mon, 1 Jun 2026 21:23:09 -0400
Subject: [PATCH] docs(battle-node): refresh ScriptedBotParticipant <remarks>
 to match Phase 2 wiring

Task 1's refactor made BattleSession read other.Context for the
Matched / BattleStart opponent half, but the class doc still claimed
the Context was ignored. Update it to match the new wiring.
---
 .../Sessions/Participants/ScriptedBotParticipant.cs       | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/SVSim.BattleNode/Sessions/Participants/ScriptedBotParticipant.cs b/SVSim.BattleNode/Sessions/Participants/ScriptedBotParticipant.cs
index 30eb321..5872e9c 100644
--- a/SVSim.BattleNode/Sessions/Participants/ScriptedBotParticipant.cs
+++ b/SVSim.BattleNode/Sessions/Participants/ScriptedBotParticipant.cs
@@ -14,10 +14,10 @@ namespace SVSim.BattleNode.Sessions.Participants;
 /// </summary>
 /// <remarks>
 /// ViewerId, Context are fixtures matching <see cref="ScriptedLifecycle.FakeOpponentViewerId"/>
-/// and a scripted opponent profile. Used by Phase 1 to preserve the v1.2 burst
-/// behavior under the new participant abstraction; the session synthesizes
-/// Matched/BattleStart/Deal using only the OTHER (real) participant's Context for now —
-/// the scripted bot's Context is ignored for those frames in Phase 1.
+/// and a scripted opponent profile. The Context fixture is the source of truth for the
+/// scripted opponent's half of Matched and BattleStart (cosmetics, deck count, class/chara) —
+/// <see cref="BattleSession.ComputeFrames"/> reads <c>other.Context</c> for those frames.
+/// Deal still uses fixed scripted frames that ignore Context.
 /// </remarks>
 public sealed class ScriptedBotParticipant : IBattleParticipant
 {