21 Commits

Include renames

Author	SHA1	Message	Date
jochen	617f95f2bf	Prove R327 against the fix as reviewed	2026-10-08 21:32:25 +02:00
jochen	06e86ccd05	Register R327: a verb that only reads opens no bus connection of its own (hq issue 327)	2026-10-08 21:32:25 +02:00
jochen	f91164863b	Prove R330 against the merge of its fix	2026-10-08 21:15:36 +02:00
jochen	54db7c3458	Register R330: a message a consumer gave up on is kept (hq issue 330)	2026-10-08 18:43:43 +02:00
jochen	3a3317b487	Register R331, so a tool check refused as no link fails before a core merge ... hq issue 331: every declared tool check read no link to the bus is open while the node-engine's link was up. Proved: fails on 824911d^1, passes on 824911d.	2026-10-08 17:11:04 +02:00
jochen	33e63ee5b4	Point R325 at #150's head after its second review ... The fix moved to 8adb7f1 on main fe00fec; proved again there.	2026-10-08 16:46:21 +02:00
jochen	5c128c1c18	Point R325 at #150's head after its rebase and review ... The fix moved to dd78357 on main 056414b; proved again there.	2026-10-08 16:22:30 +02:00
jochen	c02a8ec4c8	Register R325, so an assignment made while its build runs stays answered ... hq issue 325: assign said no module of that name a minute after the merge that asked for the module's build. Proved: fails on a759ac6, passes on b93dea8.	2026-10-08 15:50:18 +02:00
jochen	1455d9560e	Prove R318 on the fix's head, which gives the new condition its plain words (hq issue 318)	2026-10-08 14:37:35 +02:00
jochen	65ae6a9f89	Register R318: a wait for a person's new login passes the gate and stalls no walk (hq issue 318)	2026-10-08 13:42:33 +02:00
jochen	d452a47be0	Register R314: an answer larger than one message of the bus is paged, not lost (hq issue 314) ... Proved by the prover: fails on the controller's main before the fix (the caller times out), passes on mesh-controller 175b28e.	2026-10-08 13:07:43 +02:00
jochen	434bac93ce	Register the replay of issue 309 (hq ADR 0237) ... Proved with cmd/prove: TestReplay309 fails on the controller before c5a2edf (the group refused as a cycle) and passes on it.	2026-10-08 11:11:54 +02:00
jochen	157bb18fa8	Register R310: a pull request is judged by the base branch's merge-check.sh ... Proved: it fails on the commit before the controller's fix and passes on the fix (novox/hq issue 310).	2026-10-08 10:59:10 +02:00
jochen	09d347a045	Register the replay of issue 305, run in the catalogue module it lives in (hq ADR 0237) ... A catalogue module is a Go module of its own, so the prover runs a replay in the directory its register entry names. R305 fails on the commit before the fix and passes on it.	2026-10-08 10:11:57 +02:00
jochen	d0b0c7b02a	Register the replays of issues 292 and 298, each proved to fail before its fix and pass on it (hq ADR 0237)	2026-10-08 01:27:37 +02:00
jochen	c4f57432e1	Check the Go replays in the Go toolchain, and register R301 and R302 (hq issues 301, 302) ... 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
jochen	74c59661b1	Register the replays of issues 296, 299 and 300, each proved to fail before its fix and pass on it (hq ADR 0237)	2026-10-07 23:43:56 +02:00
jochen	14246bcf01	Name the merges R145 and R-crashloop replay at, not branches that are gone	2026-10-07 18:49:58 +02:00
jochen	d93f1e4eab	Replay the silent web application: its declared HTTP check raises it within two looks (hq ADR 0240 Phase B, issue 145) ... For eleven hours a web application's port was open and its program ran while every request hung; liveness and a TCP check both say it fine. R145 raises a web server whose application never answers, has the node-engine at its commit look at it with the module's declared HTTP check, and the controller at its commit raise the module's condition on the second look. Proved: it fails on the trunk before Phase B and passes on it.	2026-10-07 14:41:54 +02:00
jochen	5e3ae7b835	Replay the crash loop: a container that exits at start fails its gate on the first machine (hq ADR 0240) ... The agent server crash-looped about a hundred times behind every passing check. R-crashloop raises a container whose program exits at start, has the node-engine at its commit judge it through the runtime, and the controller at its commit judge the gate from what the engine said — two repositories, each at its own commit before the fix and on it.	2026-10-07 02:28:50 +02:00
jochen	70f62ee17b	Replay the core incidents, and prove each fails before its fix and passes on it (hq to-be 45 §9) ... Phase 5 is done when the replays of 236, 262, 263 and 266 fail on the commit before their fix and pass after. The register names every replay with its issue and fix; the bus replay (266) runs a consumer filtered like the controller's against a bus of a given release, the resolver replay (262) renders the catalogue's machine list and asks every machine's name by getaddrinfo under musl and glibc, and the prover runs each at both commits: all five (236, 262, 263, 266, 273) proved.	2026-10-06 21:01:39 +02:00