57 Commits

Include renames

Author	SHA1	Message	Date
jochen	a0754ab06d	Point R164 at the merge of its fix (mesh-controller #298) now it is merged	2026-10-13 13:11:01 +02:00
jochen	adaf525a88	Register R164: a credential only a person can give was made anyway (hq issue 164) ... The replay lives in mesh-controller (TestReplay164) and is proved against the main its fix branched from until the fix merges: go run ./cmd/prove R164 says it fails before and passes on the fix.	2026-10-13 13:10:03 +02:00
mesh-admin	a8d86bb10b	Merge pull request 'Register R614: a new SDK planned alone, rebuilding neither its toolchain nor its bundles (hq issue 614)' (#100) from fix/614-replay into main	2026-10-13 09:40:22 +00:00
jochen	9deefc6370	R614's fix is the merge of mesh-controller #296 (hq issue 614) ... Proved against the merge: fails on its first parent, passes on it.	2026-10-13 11:36:37 +02:00
jochen	7806a42c45	Register R614: a new SDK planned alone, rebuilding neither its toolchain nor the bundles in it (hq issue 614) ... Its replay (mesh-controller #296) holds the plan of 2026-10-13, "builds mesh-sdk, sent nowhere", against the fix that reads a built module's build edges from what is kept of it. Proved: fails on main, passes on the fix.	2026-10-13 11:10:16 +02:00
jochen	ba2806b985	Measure that the postgres module's image initialises where genesis now raises the store (hq issue 609, ADR 0338 §5) ... The genesis bundle raises the store as the postgres module's server: its pgvector image, its data in a directory made before the store starts and owned as the module declares it, its password from a file. The decision names one measurement before it is relied on: that image, on such a directory, empty, initialises a store that answers with that password. The image and the owner are read from the catalogue's manifest, so the measurement moves with the module's pin.	2026-10-13 10:47:34 +02:00
jochen	3b4ba29bec	Register the replay of issue 239: a module's name is not taken over by another repository ... Its replay (mesh-controller #294) holds the photo app's outage of 2026-10-04 against the fix that refuses a build from a repository other than the module's own (mesh-controller #174).	2026-10-13 07:25:26 +02:00
jochen	5f13bf0aff	Register R363: a README-only merge made a new digest of an unchanged Go program (hq issue 363) ... Proved with replays/cmd/prove: it fails on mesh-controller #292's first parent and passes on its merge.	2026-10-13 07:01:47 +02:00
jochen	becff66e0a	Register R348: a fault from before a send failed the builds sent after it (hq issue 348) ... Proved with replays/cmd/prove: it fails on mesh-controller #179's first parent and passes on the fix. The resolver's half (mesh-catalog #161) has no replay: the module had no Go before it, and the binding's loss never reproduced past its burst; the entry says so.	2026-10-13 06:09:50 +02:00
mesh-admin	2aebf8f40e	Merge pull request 'Register R349: a merge acted on late superseded the merge after it (hq issue 349)' (#95) from fix/349-replay into main	2026-10-13 03:54:15 +00:00
mesh-admin	0ca7a83e0b	Merge pull request 'Register R92 as a bed: genesis on a runtime that trusts no registry (hq issue 92) — NOT PROVED, blocked by issue 146' (#85) from fix/92-replay into main	2026-10-13 03:49:20 +00:00
jochen	d16c3db9d2	Point R349 at the replay that reaches main's batch cut (review of mesh-controller #290)	2026-10-13 05:49:05 +02:00
jochen	39ec294853	Register R349: a merge acted on late superseded the merge after it (hq issue 349) ... Issue 349 is a core issue and resolves with a replay. The replay lives in mesh-controller (#290) and is proved to fail on #179's parent and pass on it.	2026-10-13 05:22:56 +02:00
jochen	ea24e7890f	Register R340: a verb set what every agent session obeys (hq issue 340) ... Issue 340 is a core issue and resolves with a replay; the test lives in mesh-controller and is proved against the commit before #172.	2026-10-13 03:00:43 +02:00
jochen	0714f7a509	Pin R92 to today's genesis: main with every genesis fix, and the same without #91 (hq issue 92) ... At the fix's merge no genesis got past step 6 (issue 146), so neither side of the replay reached the push it replays. Fix is mesh-host main 0d11b4fc; Before is that main with #91 reverted, on the unmerged branch replay/r92-before; the controller and catalogue at their mains on both sides.	2026-10-13 02:59:45 +02:00
jochen	d03f87b00d	Register R92 as a bed: genesis on a runtime that trusts no registry (hq issue 92) ... The lab's base image trusts the documentation ranges as plain-HTTP registries, so no genesis bed could see the push to an untrusted registry that issue 92 is about (reviews 73 and 76 on mesh-host #91). The bed takes that trust off the anchor before the installer runs and asks the runtime it trusts loopback only, then runs genesis with --registry 192.0.2.10:5000 and holds that the control plane reaches the registry, trusted by the mesh's name too. The prover gains a bed kind: it builds the node-engine and its installer at each commit, the carried builder from the pinned controller, and raises the bed; a bed that never reached the step it replays skips, and a skip is an error, never the fault reproduced. Not proved yet: genesis stops at step 6 on both sides, because the temporary controller has no MESH_BUS_NATS and the bus template is refused by the installer (issue 146).	2026-10-13 02:57:21 +02:00
jochen	671d56a08a	Register R279 and R412: a folder could not follow its module's account; a seat named no paths (hq issues 279, 412) ... Both proved with cmd/prove: each fails on the commit before its fix (mesh-controller #260, #267) and passes on it. The replays' files are in mesh-controller fix/279-412-replays (3bdab29).	2026-10-13 02:40:08 +02:00
jochen	87eca0c9a9	Register R166: a requirement could not be optional (hq issue 166) ... Issue 166 resolves with its replay. TestReplay166 in the controller (mesh-controller #287) uses only what the catalogue had before #281, so the prover lays it over the commit before: it fails there and passes on the fix.	2026-10-13 02:28:18 +02:00
jochen	a96226f228	Register R201: a plan sent the control node a controller older than the one running there (hq issue 201) ... Proved: fails on mesh-controller 84deb53^1, passes on 84deb53 (the fix, #273). The replay is mesh-controller #275's TestReplay201ThePlansSend, since the fix's own TestReplay201 reads what the fix added.	2026-10-12 21:18:59 +02:00
jochen	3c655d83e1	Register R561: a plan's id was pasted into the SQL that reads it (hq issue 561) ... Proved: fails on mesh-controller f8daec0^1, passes on f8daec0 (the fix, #268).	2026-10-12 19:01:18 +02:00
jochen	e63459dd70	Register R401: the send made a value for an own secret issued outside the mesh that nobody gave (hq issue 401) ... Proved: fails on mesh-controller 1e28342^1, passes on 1e28342 (the fix, #262). The replay is mesh-controller #274's TestReplay401, since the fix's own test reads what the fix added.	2026-10-12 18:37:30 +02:00
jschoubben	79108a72a0	Register R341: a check judged the head alone and let a merge that does not compile through ... Proved with replays/cmd/prove: TestReplay341 fails on the controller's main and passes on its fix (novox/hq ADR 0323, issue 341).	2026-10-12 17:29:59 +02:00
mesh-admin	39531a9972	Register R233: a declaration that restores the package manager applies while it does not answer (hq issue 233) ... Proved with go run ./cmd/prove R233: fails on mesh-host#90's commit before (36704b5), passes on the fix (a1f9856, mesh-host#90). Placed after R237, which merged first (#83); replaces #82.	2026-10-12 14:41:40 +00:00
mesh-admin	bd33abf3dd	Register R237: assign's answer agrees with plan right after the act (hq issue 237) ... Rebase of #81 (a020f60) onto main after #80 (R358) merged into the same spot in register.go. The R237 block is byte-identical to the one approved at a020f60; only its place in the file differs, now after R358. Proved with go run ./cmd/prove R237: fails on mesh-controller #253's commit before (72edb45), passes on the fix (5facd8b, mesh-controller #253). TestReplay237 needs MESH_TEST_POSTGRES (inventory.ForTest raises a throwaway database), same as the controller's other store-backed replays.	2026-10-12 14:24:32 +00:00
jochen	26a0f45269	Register R358: a parent swapped for a link leaves its target untouched (hq issue 358) ... Proved with go run ./cmd/prove R358: fails on mesh-host#87's commit before (dce0eef), passes on the fix (36704b5, mesh-host#87).	2026-10-12 15:23:17 +02:00
jochen	8c78bcf9ce	Register R294: a quote in a command line's value is said, and an open quote refused naming where (hq issue 294)	2026-10-10 19:31:32 +02:00
jochen	95736b0eab	Register R368: a moved path is no shrink, and a shrink at the new path still is (hq issue 368)	2026-10-10 18:09:19 +02:00
jochen	719ca7ae0b	R362: the fix's commit after its branch was rebuilt without a binary (13ffae7)	2026-10-10 13:06:01 +02:00
jochen	bdb6efa8c6	Register R362: two merges seconds apart are delivered by one walk without a person ... Proved with cmd/prove: fails on 52f34d3, passes on f8c4bc5 (mesh-catalog #171).	2026-10-10 12:55:51 +02:00
jochen	fb5bb1e3de	Register R336: a send held for the bus's planned step is told to the operator ... hq issue 336 is a core issue and resolves with its replay. TestReplay336 in the controller, merged with #173 (b13a0f7), fails on its first parent and passes on it: prove R336 says PROVED.	2026-10-09 09:25:29 +02:00
jochen	06fa70d081	Register R335, so a passed gate failed by later reports fails before a core merge ... hq issue 335: a build that passed its gate was failed and put back when the first machine's later reports went quiet. Proved: fails on 8170fc5^1, passes on 8170fc5.	2026-10-08 21:52:19 +02:00
jochen	c9582ce041	Prove R327 against the merge of its fix	2026-10-08 21:33:28 +02:00
jochen	e99c2b22cb	Prove R327 against the fix rebased on the dead-letter merge	2026-10-08 21:32:25 +02:00
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