Simplify and harden session lifecycle with an explicit state machine

Không có tệp hoặc điểm vào nào được nêu tên; hãy bắt đầu bằng cách xác định phần khởi tạo session hiện có, đường dẫn HTTP stateless và phần dọn dẹp AsyncExitStack. Xem lại issue #756 và các bài kiểm thử transport trong bộ nhớ được mô tả trong issue. Được xem là hoàn thành khi có các trạng thái vòng đời rõ ràng, một đường dẫn stateless chuyên dụng, việc dọn dẹp đáng tin cậy trên mọi đường thoát và các bài kiểm thử chuyển trạng thái cho các trường hợp lỗi và stateful/stateless.

Description

Summary

Server and client sessions use an internal initialization state machine combined with various flags and manual AsyncExitStack management. Stateless mode complicates this further by setting an "Initialized" state early as a workaround.

This makes the lifecycle hard to reason about and contributes to subtle bugs (e.g., past issues like #756 in stateless mode).

Problems

• Scattered state management: Initialization and teardown logic are spread across methods and files.
• Special cases for stateless mode: Stateless HTTP sets the session as initialized even though no real protocol negotiation has occurred.
• Resource management risk: If initialization fails midway, transport tasks and resources may not be cleaned up reliably.
• Testing difficulty: Tests often bypass parts of the lifecycle using in-memory transports.

Proposal

1. Introduce an explicit session state machine

   Represent distinct states as separate types, for example:

   • UninitializedSession
   • NegotiatingSession
   • ActiveSession
   • ClosedSession
   • StatelessSession (for per-request / ephemeral cases)

   Each state exposes only the operations that are valid in that state, and transitions return the next state type.

2. Model stateless mode explicitly

   • Instead of marking a stateful session as "Initialized" prematurely, model stateless HTTP as a dedicated StatelessSession type with a simpler lifecycle.
   • Make behavior differences clear in code and docs.

3. Centralize resource cleanup

   • Ensure that all lifecycle paths (happy path, error, cancellation) lead through code that:
     • cancels outstanding tasks,
     • closes transports,
     • releases resources stored in AsyncExitStack.

Why this matters

• Reliability: Fewer edge cases and surprise states where messages can be processed incorrectly.
• Debuggability: Easier to reason about what can happen in each state.
• Extensibility: Adding new lifecycle behavior (e.g., resuming sessions) becomes more manageable.

Acceptance criteria

• Session lifecycle is represented via explicit types or a clearly defined state machine.
• Stateless HTTP mode uses a dedicated path rather than setting "Initialized" as a hack.
• All entry/exit paths of sessions ensure proper cleanup of transports and tasks.
• Tests cover state transitions, including error cases and stateless/stat eful differences.

References

No response