refactor(battlenode): name sender-only vs both-sides handshake checks (§D)
Behavior-preserving; 231 BattleNode tests green. FrameDispatchContext.BothAfterReady() -> BothSidesAfterReady() (7 call sites). The 4 inline `SenderPhase == AfterReady` checks in TurnEndHandler/TurnEndFinalHandler now read a new SenderIsAfterReady property. Both carry cross-referencing docs so the Bot-arm (sender-only) vs PvP-arm (both-sides) distinction is explicit at the type. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -15,7 +15,7 @@ internal sealed class JudgeHandler : IFrameHandler
|
||||
// start another one, stalling the loop; confirmed by the 2026-06-03 two-client capture).
|
||||
// The sender then emits TurnStart, which TurnStartHandler relays to the opponent as {spin}.
|
||||
// battleCode is dropped; spin=0 for the deterministic-turn slice.
|
||||
if (ctx.Type == BattleType.Pvp && ctx.BothAfterReady())
|
||||
if (ctx.Type == BattleType.Pvp && ctx.BothSidesAfterReady())
|
||||
{
|
||||
var frame = ctx.Env with { Body = new JudgeBody(Spin: BattleFrameDefaults.DeterministicTurnSpin) };
|
||||
return new[] { new DispatchRoute(ctx.From, frame, Stock.Normal) };
|
||||
|
||||
Reference in New Issue
Block a user