The runtime serves a list of modules on one credential, naming a bundle that fails to load (hq ADR 0175, to-be 38 WP1)

One tool runtime per node, host-side, is what the runtime was written to be; the catalogue built a
container per module around it instead. This lets `serve` take a list — MESH_TOOL_MODULES as
<module>=<entrypoint> entries — and do for every assigned module what it did for one: read that
module's membership and follow it, serve its tools where the membership says, serve each held
seat's verbs on the seat's subjects. The seats come from the memberships now, so the node's
credential carries no claims; a module's own runtime still reads its credential's, so nothing
built today changes behaviour. A bare path in MESH_TOOL_MODULES stays the one-module form.

A bundle that throws on import is said in the log and in what `tools` answers for its module
(`failed`), which discovery lists with the reason instead of as "not answering"; the other bundles
serve. The filter that dropped every registration under a name but the one module goes; what
stays is that a registration under a seat's name is served only where some served module claims
the seat. A tool runs attributed to its module, so an event it emits lands on the module's
subject and not the runtime's. MESH_OPERATOR_ACCOUNT and MESH_OPERATOR_HOME are read and said;
tools take them from their environment.

Proven against a real bus: three bundles, one broken; five tools and two seat verbs answer on
their subjects; `tools` names the failed bundle; a membership re-issued mid-run re-serves.

src/client.ts

@@ -192,7 +192,12 @@ export async function toolsOn(bus: Broker): Promise<Listing> {
   }
   asked.forEach((outcome, i) => {
     const module = names[i]!;
-    if (outcome.status === "fulfilled" && Array.isArray(outcome.value?.tools)) {
+    if (outcome.status === "fulfilled" && typeof outcome.value?.failed === "string") {
+      // The runtime answered for it and serves nothing: the bundle failed to load (ADR 0175). Said
+      // with the reason, because "not answering" would send somebody to check an assignment that
+      // is fine.
+      notAnswering.push(`${module} (its tools bundle failed to load: ${outcome.value.failed})`);
+    } else if (outcome.status === "fulfilled" && Array.isArray(outcome.value?.tools)) {
       for (const t of outcome.value.tools) {
         tools.push({ module, name: t.name, description: t.description, input: t.input, subjects: t.subjects });
       }