8 Commits

Include renames

Author	SHA1	Message	Date
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