Check the Go replays in the Go toolchain, and register R301 and R302 (hq issues 301, 302) #59

Merged

mesh-admin merged 1 commits from fix/the-replays-are-checked-in-go into main

2026-10-07 22:26:27 +00:00

Author	SHA1	Message	Date
jochen	c4f57432e1	Check the Go replays in the Go toolchain, and register R301 and R302 (hq issues 301, 302) mesh/merge-gate pass: the change touches no module of the mesh's graph Details mesh/repo-check pass: its merge-check.sh passed Details mesh/delivery delivered Details The lab's check ran in the TypeScript toolchain, which holds no Go compiler, so the replays register was never compiled before a merge. merge-check.sh now declares replays/merge-check.sh as its Go part, which the build seat runs in the Go toolchain: gofmt, go vet and the register's own tests. Both new replays are proved: each fails on the commit before its fix and passes on it.	2026-10-08 00:13:46 +02:00

Author

SHA1

Message

Date

jochen

c4f57432e1

Check the Go replays in the Go toolchain, and register R301 and R302 (hq issues 301, 302)

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

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

The lab's check ran in the TypeScript toolchain, which holds no Go compiler,
so the replays register was never compiled before a merge. merge-check.sh now
declares replays/merge-check.sh as its Go part, which the build seat runs in
the Go toolchain: gofmt, go vet and the register's own tests. Both new
replays are proved: each fails on the commit before its fix and passes on it.

2026-10-08 00:13:46 +02:00