Architecture and ownership of state

The layers are Server transport/process supervision → Engine application primitives → HTTP or WS engine → middleware/router → application callbacks/controllers → response encoding. Console starts/manages the app; component bootstraps configure DB/session/events, and plugins extend selected integration points.

Transport readiness is separate from application readiness. A shared request alias does not make the conflicting HTTP/WS engines interchangeable. Worker-local memory is not a shared database. Service containers may cache objects; event registries are local; sessions use a chosen handler; template assignment uses the current request while pre/post renderer lists can persist. Define ownership and cleanup at each boundary.

Review configuration/bootstrap, component lifecycles, Web, WS limitations and release gates. Do not infer async SQL/HTTP behavior merely from running inside an event loop.