jochen dcaf843b8a The lab's phone shows an HTML message as Telegram does, so a tap carries back the words shown (issue 692) ...

Since mesh-catalog #278 the channel sends every message in HTML (issues 383, 639). The fake Bot API kept
the text as sent, tags and entities included, and gave that back on a tap; the channel compares a tap by
the plain words it showed, so the proof's tap was refused as "this message does not show what the mesh put
there". Telegram reads the markup and gives the plain words back; the fake now does too.

2026-10-14 02:37:06 +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

The lab's phone shows an HTML message as Telegram does, so a tap carries back the words shown (issue 692)

2026-10-14 02:37:06 +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

The lab's phone shows an HTML message as Telegram does, so a tap carries back the words shown (issue 692)

2026-10-14 02:37:06 +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