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

..

asker_test.go

asks: move to mesh-sdk 76902998, where an act is named fields digested canonically

2026-10-09 12:02:39 +02:00

doc.go

Prove the operator's answers end to end before anybody uses them (hq ADR 0259)

2026-10-09 11:08:42 +02:00

faketelegram_test.go

asks: a replayed tap is said as the answer already recorded, on its acknowledgement (issue 393)

2026-10-10 18:22:22 +02:00

go.mod

asks: move to mesh-sdk go/v0.1.10

2026-10-09 16:25:00 +02:00

go.sum

asks: move to mesh-sdk go/v0.1.10

2026-10-09 16:25:00 +02:00

harness_test.go

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

live-acceptance.sh

asks: the live acceptance says when a new link can approve, and asks through mesh-cli

2026-10-09 15:37:57 +02:00

merge-check.sh

Run the proof of the operator's answers in the Go toolchain on every pull request, and say NOT RUN loudly where it cannot

2026-10-09 12:02:28 +02:00

proof_test.go

asks: a replayed tap is said as the answer already recorded, on its acknowledgement (issue 393)

2026-10-10 18:22:22 +02:00