mesh-lab

460 Commits 3 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
jochen	dcaf843b8a	The lab's phone shows an HTML message as Telegram does, so a tap carries back the words shown (issue 692) mesh/merge-gate head dcaf843b8a6e merged into trunk 1316a405a630 — pass: the change touches no module of the mesh's graph Details mesh/repo-check head dcaf843b8a6e merged into trunk 1316a405a630 — pass: THE CHANGE ALTERS ITS OWN CHECK (asks/merge-check.sh): main's version judged it; t… Details mesh/delivery delivered Details 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
jschoubben	a076ccfe51	Run the proof of the operator's answers in the Go toolchain on every pull request, and say NOT RUN loudly where it cannot The review of 2026-10-09: the build seat runs the lab's merge-check.sh in the TypeScript toolchain, which holds no Go, so the proof never ran there. It is now a declared part of its own (mesh-check-also), run against the controller, runtime and catalogue cloned beside the lab; a missing clone or a controller without the proof's fixture is said NOT RUN in capitals instead of failing every lab change.	2026-10-09 12:02:28 +02:00
jschoubben	3a486014fc	Prove the operator's answers end to end before anybody uses them (hq ADR 0259) mesh/merge-gate pass: the change touches no module of the mesh's graph Details mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it… Details mesh/delivery superseded: a newer head of the same pull request Details 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

Author

SHA1

Message

Date

jochen

dcaf843b8a

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

mesh/merge-gate head dcaf843b8a6e merged into trunk 1316a405a630 — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head dcaf843b8a6e merged into trunk 1316a405a630 — pass: THE CHANGE ALTERS ITS OWN CHECK (asks/merge-check.sh): main's version judged it; t…

Details

mesh/delivery delivered

Details

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

jschoubben

a076ccfe51

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

The review of 2026-10-09: the build seat runs the lab's merge-check.sh in the TypeScript toolchain, which
holds no Go, so the proof never ran there. It is now a declared part of its own (mesh-check-also), run
against the controller, runtime and catalogue cloned beside the lab; a missing clone or a controller
without the proof's fixture is said NOT RUN in capitals instead of failing every lab change.

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

jschoubben

3a486014fc

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

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…

Details

mesh/delivery superseded: a newer head of the same pull request

Details

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