阶段 5

2026-03-27 13:27:14 +08:00
parent ff9ee1291f
commit e5851795c7
43 changed files with 1544 additions and 35 deletions
@@ -0,0 +1,40 @@
+## ADDED Requirements
+
+### Requirement: Session lifecycle distinguishes transport and login state
+The shared networking core SHALL expose an explicit session lifecycle model that distinguishes transport connectivity from login/authentication success. Hosts MUST be able to observe at least disconnected, transport-connected, login-pending, logged-in, login-failed, timed-out, and reconnecting lifecycle states without inferring them from unrelated message handlers.
+
+#### Scenario: Transport connect does not imply login success
+- **WHEN** the transport establishes a usable remote session but no login success message has been accepted yet
+- **THEN** the shared lifecycle reports a transport-connected or login-pending state
+- **THEN** it does not report the session as logged in
+
+#### Scenario: Login success advances lifecycle independently
+- **WHEN** the client or server session manager receives a successful login/authentication result for an active transport session
+- **THEN** the shared lifecycle transitions that session into the logged-in state
+- **THEN** hosts can react to that state change without conflating it with transport establishment
+
+### Requirement: Heartbeat is limited to liveness, RTT, and time sync
+The shared session lifecycle SHALL treat heartbeat traffic as infrastructure input for liveness detection, round-trip-time measurement, and clock synchronization only. Heartbeat processing MUST NOT itself own login success, login failure, or reconnect policy decisions.
+
+#### Scenario: Heartbeat updates liveness and RTT only
+- **WHEN** a heartbeat response is received for an active session
+- **THEN** the session manager updates last-seen or timeout bookkeeping and RTT or clock-sync data
+- **THEN** it does not mark the session logged in solely because the heartbeat succeeded
+
+#### Scenario: Missing heartbeat triggers timeout state
+- **WHEN** the configured heartbeat timeout elapses without a required heartbeat or other liveness signal
+- **THEN** the session lifecycle transitions the session into a timed-out state
+- **THEN** reconnect handling is delegated to the lifecycle reconnect policy rather than hidden inside the heartbeat handler itself
+
+### Requirement: Timeout and reconnect are session-manager responsibilities
+The shared networking core SHALL manage timeout detection, disconnect transitions, and reconnect scheduling through a session-manager component rather than implementing those decisions inside business message handlers.
+
+#### Scenario: Timeout produces an observable reconnect transition
+- **WHEN** a reconnect-capable host has a session that times out
+- **THEN** the session manager emits a timeout-related lifecycle transition
+- **THEN** it can subsequently move the session into a reconnecting or reconnect-pending state according to configured policy
+
+#### Scenario: Login failure is distinct from transport disconnect
+- **WHEN** authentication or login fails while the transport session is still active
+- **THEN** the shared lifecycle reports a login-failed state
+- **THEN** hosts can handle that failure separately from a transport disconnect or heartbeat timeout
@@ -0,0 +1,14 @@
+## ADDED Requirements
+
+### Requirement: Shared runtime owns host-agnostic session lifecycle orchestration
+The shared network foundation SHALL include host-agnostic session lifecycle orchestration alongside transport startup and message routing. Client and server hosts MUST be able to compose the same shared runtime with a session manager that consumes transport events, login results, and heartbeat signals without depending on Unity-specific runtime types.
+
+#### Scenario: Client host composes runtime with lifecycle manager
+- **WHEN** the Unity client constructs its shared networking runtime
+- **THEN** that runtime includes shared session lifecycle management in addition to transport and message routing
+- **THEN** Unity-specific code remains responsible only for reacting to lifecycle state changes and driving host behavior
+
+#### Scenario: Server host observes the same lifecycle vocabulary
+- **WHEN** a non-Unity server host composes the shared networking runtime
+- **THEN** it uses the same lifecycle state model and session-manager abstractions as the client-side shared runtime
+- **THEN** server-specific cleanup or admission behavior stays in the server host adapter rather than forking the shared core contract