e2e: assigned sonarr + grafana prove the two runtime config paths (ADR 0051/0052)

assigned-sonarr proves the Servarr detection path: the runtime discovers its API
key from the app's config.xml and serves its tools. assigned-grafana proves the
settings path: the operator states URL and token as settings, the mesh merges them
into the module's config file, and the runtime serves from that with nothing in the
manifest. Both green.

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

scenarios/sonarr-node.yml

@@ -0,0 +1,28 @@
+# One machine that becomes a mesh and assigns itself sonarr's tool runtime.
+#
+# plex-node proved a tools+events module that self-detects its token from a mounted config dir; this
+# proves the same self-configuring pattern generalises to the Servarr family (novox/hq ADR 0052):
+# sonarr's runtime detects its API key from the server's config.xml and serves sonarr's tools over a
+# mesh-issued scoped account, with no live Sonarr to reach.
+scenario: sonarr-node
+
+segments:
+  hosting:
+    kind: public
+    cidr: [192.0.2.0/24]
+
+machines:
+  anchor:
+    at: { segment: hosting, address: [192.0.2.10] }
+    inbound: allow
+    memory: 3GiB
+    cpus: 2
+
+images:
+  - postgres:17-alpine
+  - cloudamqp/lavinmq:latest
+  - mesh-control:development
+  - mesh-runtime-sonarr:development
+
+place:
+  all: [host, runtime]