Network 层的迁移与强化已完成，TODO.md 与 MobaSyncMVP.md 给出后续方向

openspec/specs/shared-network-foundation/spec.md

@@ -1,4 +1,4 @@
-# shared-network-foundation Specification
+# shared-network-foundation Specification
 
 ## Purpose
 Define the shared transport, session-lifecycle, and message-routing foundation that both client and server hosts use without depending on Unity-specific runtime host classes.
@@ -31,12 +31,17 @@ The shared message-routing layer SHALL execute received business handlers throug
 - **THEN** the shared message-routing layer still processes received messages correctly through that host-selected strategy
 
 ### Requirement: Shared core preserves current transport and message contracts
-The shared client/server foundation SHALL preserve the existing `ITransport` send/receive contract and the envelope-based `MessageManager` routing model so client and server hosts exchange the same business payload format through the same transport abstractions.
+The shared client/server foundation SHALL preserve the envelope-based business-message contract across client and server hosts while allowing delivery-policy selection behind the shared message-routing layer. Reliable control traffic MUST continue to use the existing `ITransport` contract, and high-frequency sync traffic MUST be composable through a host-agnostic sync strategy without introducing Unity-specific runtime types into the shared networking core.
 
-#### Scenario: Shared hosts exchange the same envelope format
-- **WHEN** a client host sends a business message through the shared core to a server host using the shared core
-- **THEN** the message is encoded using the same envelope contract on the client side
-- **THEN** the server host decodes and routes it through the shared message-routing layer without a host-specific protocol fork
+#### Scenario: Shared hosts exchange the same envelope format across delivery lanes
+- **WHEN** a client host sends a business message through either the reliable control path or the high-frequency sync path
+- **THEN** the payload is encoded with the same shared envelope and message-type contract
+- **THEN** the server host decodes and routes it through shared networking logic without a host-specific protocol fork
+
+#### Scenario: Hosts compose delivery-policy selection without Unity dependencies
+- **WHEN** a non-Unity server host constructs the runtime networking stack with reliable control traffic and a high-frequency sync lane
+- **THEN** it uses shared delivery-policy abstractions without depending on Unity frame-loop types
+- **THEN** the Unity client can use the same abstractions while still supplying its own host-specific dispatch behavior
 
 ### 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 shared foundation with session orchestration that consumes transport events, login results, and heartbeat signals without depending on Unity-specific runtime types, while supporting both single-session client composition and multi-session server composition.
@@ -49,4 +54,4 @@ The shared network foundation SHALL include host-agnostic session lifecycle orch
 #### Scenario: Server host composes shared foundation with multi-session orchestration
 - **WHEN** a non-Unity server host constructs the runtime networking stack for multiple remote peers
 - **THEN** it uses the shared transport and message-routing foundation together with shared multi-session lifecycle orchestration
-- **THEN** server-specific cleanup, admission, and gameplay reactions stay in the server host adapter rather than forking the shared lifecycle contract
+- **THEN** server-specific cleanup, admission, and gameplay reactions stay in the server host adapter rather than forking the shared lifecycle contract