Issue 340: say plainly which test refuses the new url
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request

This commit is contained in:
jochen
2026-10-09 09:43:12 +02:00
parent 523bb9c55a
commit 0badde3a56
@@ -122,9 +122,9 @@ at the controller's terminal. An agent's attempt through any mesh tool is refuse
some, of each kind, is refused through the tools and the import tool, and lands when set in the module's
settings at the terminal. The home scope is refused for any node but the one serving the call, and there
wherever the home is the operator's own; it is taken only where the home is an agent account's own, and a
home item on the bus is never placed in the operator's home. So is a new `url` on a
module whose mergeable runtime configuration starts empty, while a file marked `"trusted": false` stays the
verb's. The layer is
home item on the bus is never placed in the operator's home. Through the settings verb, a new `url` on a
module whose mergeable runtime configuration starts empty is refused too, while a file marked
`"trusted": false` stays the verb's. The layer is
unchanged after every refusal. At the terminal the same is taken. These tests fail on the commit before
the fix.
- **Live, after both are taken:** the calls in the diagnosis's last section are each refused, and