diff --git a/04-ISSUES/348-a-resolver-that-stopped-answering-ran-on-unnoticed-and-builds-sent-after-it-were-blamed/01-diagnosis.md b/04-ISSUES/348-a-resolver-that-stopped-answering-ran-on-unnoticed-and-builds-sent-after-it-were-blamed/01-diagnosis.md
index 00a9e8ce..91f3aaa4 100644
--- a/04-ISSUES/348-a-resolver-that-stopped-answering-ran-on-unnoticed-and-builds-sent-after-it-were-blamed/01-diagnosis.md
+++ b/04-ISSUES/348-a-resolver-that-stopped-answering-ran-on-unnoticed-and-builds-sent-after-it-were-blamed/01-diagnosis.md
@@ -175,4 +175,5 @@ registry, is the operator's decision.
 A replay in mesh-lab's register is still owed before this core issue resolves (ADR 0237).
 
 The controller's own test of the resolver's manifest (`TestTheResolverForwardsToFixedUpstreamsAndNeverReadsResolvConf`)
-now asks for `bind-interfaces` and refuses `bind-dynamic`, so the two pull requests land together.
+reads the catalogue beside it, so for now it takes either binding; once the catalogue's main binds once,
+it should refuse `bind-dynamic` (a follow-up in the controller).