A registration under a stranger's name is said and skipped, not fatal

A module implementing a seat its credential does not (yet) claim registered tools under the seat's
name; the runtime treated them as the module's own, refused to serve another module's key, and the
whole runtime restarted in a loop — postgres on the control node, 2026-10-01, whose credential predated
the claims. Such a registration is now named in the log and left out; the module's own tools serve.

src/runtime.ts

@@ -59,7 +59,14 @@ export async function runTools(opts: RuntimeOptions): Promise<() => void> {
   // both: its tools are the module's and the seat's verbs alike.
   const self = opts.credential?.module;
   const seatNames = new Set((opts.credential?.claims ?? []).map((c) => c.seat));
-  const ownRegistrations = collectTools().filter(({ module }) => module === self || !seatNames.has(module));
+  // A registration under a name that is neither this module nor a seat it claims is not served:
+  // said, and left out, rather than fatal — on 2026-10-01 the credential of a module that had just
+  // learned to implement a seat did not yet name the claim, and the whole runtime restarted for it.
+  const ownRegistrations = collectTools().filter(({ module }) => {
+    if (module === self || !self || seatNames.has(module)) return module === self || !self;
+    console.log(`[mesh-tools] ${self} registers tools under "${module}", which is neither this module nor a seat its credential claims; not served until the mesh issues the claim`);
+    return false;
+  });
   const tools = ownRegistrations.flatMap(({ module, tools: own }) => own.map((t) => ({ module, name: t.name })));
   const stops: Array<() => void> = [];
   const stop = (): void => stops.splice(0).forEach((s) => s());