jochen
020c05fe65
mesh/merge-gate pass: builds messenger, telegram → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
At 13:30 on 2026-10-10 the operator approved two questions on Telegram and saw nothing happen: the channel acknowledged each tap with no words, before the router had judged it, and the edit that removed the buttons kept the question's title, adding only a line under it that rings nothing. The router now answers a chosen option in reply to the tap, once the ask's end is recorded and before the question is edited: "You chose Approve: recorded, and claude-code was told." (or, when the bus did not take the warrant, that it is told when it does). A refusal already replied with its reason. Telegram holds a tap's acknowledgement for the router's word and shows it as the tap's own toast; a word with a body (a refusal's reason, Details) also stays in the chat. Without a word in 8 seconds the toast claims nothing, and the late word goes to the chat. A secret is never a toast. An ask's own message, once answered, carries its outcome as its title: "You chose Approve at 13:30 on Telegram · <headline>", then whether the asker was told. The asks protocol carries no result back from the asker, so nothing more is claimed of what it did.