App-server test suites and protocol verification

This stage is the app server’s safety workshop. It is not part of normal startup, daily work, or shutdown. Instead, it runs during development and continuous testing to prove that the server still speaks the right language, starts correctly, connects to clients, and supports real workflows.

The protocol tests act like a ruler for messages. They check that JSON-RPC and remote-control data keep the exact shapes clients expect, and that generated schemas have not changed by accident. The daemon and transport tests check the background server process, update decisions, socket connections, client routing, and the special test client used to exercise the system safely.

The unit tests look inside the app server’s smaller parts, such as configuration import, command-line overrides, tracing, error reporting, and conversation state. Shared fixtures build a pretend world with fake accounts, models, saved sessions, and AI responses, so tests do not need real services.

Finally, the integration suites put everything together. They start the server like a real client would, send requests, run conversations, use tools and plugins, and verify the visible behavior from end to end.