Chat On Issue

HIS COMMENT IN AN ISSUE'S ACTIVITY, ANSWERED AT ONCE (owner, 2026-10-14: "in the comments section … i expect a natural response really fast from the llm, not the full cycle").

His words are a row in the matter's room, as every comment is; Stormy's answer is one quick read (runtime/issue_chat.py) of the record, the page drawn for it and the conversation, kept on that row and returned here, so it is on his screen with no second read. Only when the read says his words handed it work does the desk wake — through the follow-up's own door (_follow), linked to his row so its lines land under the answer, and AFTER the answer has gone back: the wake writes the record and accepts a turn, seconds he never waits on. A read that fails hands his words to the desk instead, before answering: a comment never goes unanswered.