... minute check for anyone running a long-lived appserver: PHP under RoadRunner or Swoole, Node, anything where one process serves request after request instead of starting fresh each time. List the values your templates read that middleware sets per request: the signed-in flag, the avatar, the CSRF token, the analytics user id. Then ask what each of them holds on a request where that middleware did not run. In a process-per-request world the answer is nothing ...

... count, pool size, connection cap, a timeout. Then search your source for the prose that argues from it not the number, the sentences. The ones that say: because we have N of these, this limit is X. Mine: the appserver's HTTP pool is six concurrent workers. That number is well guarded. There is a unit test named after it that asserts six, and a second one checking that six plus the two background workers fit the host ...

... agent records acknowledgements in RECEIPTS.md New guidance is picked up at a safe checkpoint rather than being pushed into a running turn. The project assumes one thread per worktree and one mailbox per worktree. It also keeps Codex AppServer access limited to discovery and status; it does not use turn steering, message injection, or interruption calls. The interesting part was not the Electron interface. It was designing a coordination model that stays observable with normal files, Git, and editor ...