Files
simplexmq/scripts
brenzi-agentandbrenzi-agent 89c8ba9c98 resolver: read .simplex reservations from the name policy (#1993)
* resolver: read .simplex reservations from the name policy

simplex-network/ens-contracts#42 moved reservedNames from SimplexController
to SimplexNamePolicy. SNRC_NAME_POLICY_<TLD> names it; where it is unset the
controller is read as before, as on .testing.

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: keep the reserved read's shape, explicit policy in tests, describe contracts by behavior

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: pin the name policy in every test that reads reservations, one policy test that fails without the read, note setNamePolicy

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: no env pins the suite does not keep elsewhere, no comment repeating the docstring

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: name what the .testing controller keeps

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: an empty name policy reply is refused too

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: read each controller's name policy at startup in place of SNRC_NAME_POLICY_<TLD>

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: workers open their own RPC connections, docs of the startup read, test names and docstrings that say what holds

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: a controller with no contract behind it stops the startup read, so the container restarts until the node reaches it

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: an empty name policy reply falls back again, so a chain without .testing's controller still starts; new functions after the ones they join, compose lines added only

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: tests of the workers' own connections, an address without a contract and an unconfigured controller; docs of which TLDs answer 502

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: a controller naming no policy is logged as the other fallbacks are, a test of the startup exit, no redundant default

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: the startup test above the worker tests' Linux guard, without a controller it does not need

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: the startup test runs one worker, a test of an unconfigured controller, the fallbacks described once

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: compose names the 502 of a policy the node has not reached, the worker test sets its own reservation, no repeated README clauses

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: every worker test reads the name's reservation from the policy, so its answer stays in setUp

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: docstrings that say where reservations are read from, no comment that does not hold

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: each reservation read picks the policy over the controller itself, no helper for two sites

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

* resolver: address review: the quick start's restart for a TLD with a name policy, the startup read's docstring

Claude-Session: https://claude.ai/code/session_01BxsKd45qytTbangMqJs93F

---------

Co-authored-by: brenzi-agent <346870783+brenzi-agent@users.noreply.github.com>
2026-10-29 12:13:37 +00:00
..
2022-09-18 13:36:02 +01:00