feat(battle-node): thread MatchContext through bridge to BattleSession
IMatchingBridge.RegisterPendingBattle now takes a MatchContext; PendingBattle carries it; BattleSession stores it. ArenaTwoPickBattleController builds ctx from IMatchContextBuilder. ScriptedLifecycle still uses ScriptedProfiles for the player half — Tasks 5/6 migrate the lifecycle. Existing tests updated: MatchingBridgeTests, BattleNodeFlowTests, InMemoryBattleSessionStoreTests, BattleSessionDispatchTests, BattleSession PumpTests, ArenaTwoPickBattleControllerTests (which now seeds a TK2 run + adds a no-active-run 400 case). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
@@ -3,10 +3,10 @@ namespace SVSim.BattleNode.Bridge;
|
||||
public interface IMatchingBridge
|
||||
{
|
||||
/// <summary>
|
||||
/// Mint a battle id, register a pending session for the given viewer, and return the
|
||||
/// URL the client should open a socket to.
|
||||
/// Mint a battle id, register a pending session for the given viewer with their per-battle
|
||||
/// MatchContext snapshot, and return the URL the client should open a socket to.
|
||||
/// </summary>
|
||||
PendingMatch RegisterPendingBattle(long viewerId);
|
||||
PendingMatch RegisterPendingBattle(long viewerId, MatchContext context);
|
||||
}
|
||||
|
||||
public sealed record PendingMatch(string BattleId, string NodeServerUrl);
|
||||
|
||||
Reference in New Issue
Block a user