process TODO.md step6

2026-03-29 09:53:33 +08:00
parent d3d25c8921
commit 4826bf15a5
20 changed files with 668 additions and 10 deletions
@@ -1,4 +1,4 @@
-# multi-session-lifecycle Specification
+# multi-session-lifecycle Specification

 ## Purpose
 Define the shared orchestration model for hosts that manage multiple concurrent network sessions while preserving the existing per-session lifecycle vocabulary.
@@ -32,3 +32,16 @@ The multi-session lifecycle coordinator SHALL support explicit removal or discon
 - **WHEN** one remote peer disconnects or is evicted by the host
 - **THEN** the coordinator updates or removes that peer's managed session
 - **THEN** other managed sessions remain queryable and keep their own lifecycle state
+
+### Requirement: Multi-session server lifecycle can be owned by a runtime entry point
+The multi-session lifecycle model SHALL support being created, owned, and torn down through a concrete server runtime entry point. Starting the entry point MUST provide access to the `MultiSessionManager` through the hosted `ServerNetworkHost`, and stopping the entry point MUST clear managed sessions without requiring callers to remove peers individually.
+
+#### Scenario: Entry point startup exposes multi-session lifecycle ownership
+- **WHEN** a server runtime entry point starts successfully
+- **THEN** the hosted `ServerNetworkHost` exposes its `MultiSessionManager` for per-peer lifecycle observation
+- **THEN** callers do not need to manually construct or inject a separate multi-session coordinator
+
+#### Scenario: Entry point shutdown clears all managed peers
+- **WHEN** the server runtime entry point is stopped while one or more managed sessions exist
+- **THEN** the hosted `ServerNetworkHost` removes all managed sessions as part of shutdown
+- **THEN** no unrelated external cleanup step is required to reset multi-session lifecycle state