process TODO.md step 9
This commit is contained in:
@@ -41,4 +41,15 @@ The shared networking core SHALL manage timeout detection, disconnect transition
|
||||
#### 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 for that managed session
|
||||
- **THEN** hosts can handle that failure separately from a transport disconnect or heartbeat timeout
|
||||
- **THEN** hosts can handle that failure separately from a transport disconnect or heartbeat timeout
|
||||
|
||||
### Requirement: Sessions retain dual transport wiring
|
||||
Session lifecycle components SHALL initialize session-scoped networking services with both the primary reliable transport and the optional sync transport supplied by the integration layer.
|
||||
|
||||
#### Scenario: Client single-session initialization with dual transports
|
||||
- **WHEN** the client integration path creates a single session and a sync transport is configured
|
||||
- **THEN** the session-scoped services SHALL retain both transport references for subsequent message routing
|
||||
|
||||
#### Scenario: Server multi-session initialization with fallback transport
|
||||
- **WHEN** the server integration path creates session-scoped services without a dedicated sync transport
|
||||
- **THEN** each session SHALL continue to initialize successfully and SHALL use the primary reliable transport as the fallback lane
|
||||
|
||||
Reference in New Issue
Block a user