3 Commits

Include renames

Author	SHA1	Message	Date
jochen	8adb7f1a05	Give each pending assignment its own condition, and keep a raised row until it clears ... Second review of #150: one key per machine and module let a newer failure be cleared in the tick that raised it, pruning could orphan an open condition, and a build no longer waited for read as never asked although it may still run.	2026-10-08 16:45:43 +02:00
jochen	249d97d1c8	Make pending assignments safe to race, settle them on a tick, and say only what was checked ... Review of #150: a withdrawal could land between the look and the act, a failed ask read as a build in flight, a request kept the wrong asker, a build being registered read as not built, build "true" could ask a build nothing waited on, and a status read changed state. Claim a row under the machine's hold before making it, keep a request only once asked, settle on the controller's own tick, raise an assignment not made as a condition until it is answered, and tie each row to its machine.	2026-10-08 16:38:11 +02:00
jochen	7d63d2e68c	Say why assign finds no module, and keep an assignment pending on its build ... A merge asks for a new module's build, and assign answered "no module of that name" until the build registered it, which read as a module nobody registered (hq issue 325). Keep every build request, tell a build in flight, a module known and not built, and an unknown name apart, and make an assignment made while the build runs when the build registers the module.	2026-10-08 16:38:11 +02:00