3 Commits

Include renames

Author	SHA1	Message	Date
jochen	af0a32a780	asks: a replayed tap is said as the answer already recorded, on its acknowledgement (issue 393) ... Since issue 372 the router answers the same answer again from the same account with 'You already chose Approve at HH:MM: recorded.', on the tap's acknowledgement rather than in the chat. The proof from #74 still waited for a chat refusal, so it failed on every mesh-lab pull request. The lab's phone now keeps a tap's acknowledgement words, and the replay subtest waits for them; its checks that nothing more is done stay.	2026-10-10 18:22:22 +02:00
jschoubben	01a541cadf	asks: prove the reviewed flow — the controller's root-free word asked before an approval, the desk on its own account, a tap only on the words shown, the question saying who asks and what each answer does, and a rehearsal at the terminal for the live acceptance	2026-10-09 12:44:21 +02:00
jschoubben	3a486014fc	Prove the operator's answers end to end before anybody uses them (hq ADR 0259) ... The bus the controller composes and raises, at its commit, for one machine; the mesh's runtime serving the router and the Telegram channel on their own credentials; a fake Bot API as the phone. It links the operator's account with the code shown on the desk, refuses an approval in the hour after a link, performs an approval exactly once with who and how in the warrant and the router's record, refuses a replayed tap and a redelivered warrant, tells the operator when another account answers, drops a tap from a group, does nothing on Decline and on expiry, offers no approval while an agent can become root where the channel runs, and has the bus refuse every forged warrant, ask and tap. live-acceptance.sh is the same after rollout, with a drill the operator approves on the phone.	2026-10-09 11:08:42 +02:00