6 Commits

Include renames

Author	SHA1	Message	Date
jochen	35c4de7d08	messenger, telegram: a second tap on the recorded answer is said as recorded, and the fallback claims nothing (issue 372 review) ... The review found that a double tap while the phone's spinner turned would be answered 'That answer was not taken', reading as if the approval failed; it is now 'You already chose Approve at 13:30: recorded.' and does nothing more. The fallback toast no longer promises a change that may not come (a stranger's tap), the wait outlasts the router's 10 s wait for the controller's root word, the channel's own refusals stay in the chat too, and the store's error words stay in the journal.	2026-10-10 14:05:41 +02:00
jochen	020c05fe65	messenger, telegram: show the operator at once what a tap did, and change the question to its outcome (hq issue 372) ... 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.	2026-10-10 13:59:54 +02:00
jschoubben	723e5f8cce	telegram: say the desktop client's gap is a known one the router does not enforce (hq issue 344)	2026-10-09 17:08:17 +02:00
jschoubben	711e674ab1	telegram: take a tap only on a message showing the words this channel put there, and say where an approval from Telegram means something ... The review of 2026-10-09 (M4): another holder of the token can change a message's words and leave its buttons, so the operator taps Release under words that say something else. Each message's words are now kept as a digest, per chat and message, and a tap on a message whose words differ, or that this channel never showed, is refused on the phone and never said to the router. The README says, as the operator directed (H5), that an approval from Telegram is meaningful only where agents run under their own account without sudo, without the operator's X display, and with Telegram Desktop's data readable by the operator alone; until then, approve from the phone.	2026-10-09 17:08:17 +02:00
jochen	0d9ec84a9c	Run telegram as its own account in a runtime of its own, keep its offset per update, and keep no copy of a secret on the desk (hq ADR 0259 §8)	2026-10-09 17:08:17 +02:00
jochen	a412389725	Add telegram and the desk as channels of their own, each judging nothing and holding only its own secret (hq ADR 0259)	2026-10-09 17:08:17 +02:00