Both clients map local event names to their own wire

A module names its events locally and each transport works out where they land.
That is what design 29 says and what neither client did: both passed the name
straight through, which happened to be right on the old bus because modules were
writing routing keys, and wrong on the new one (novox/hq 04-ISSUES/127).

The old bus's client now turns a local name into `module.<emitter>.<event>` on the
way out and back on the way in. Without that, converting the modules to local
names would have broken the mesh that is actually running.

**A handler and a manifest now say the same thing.** The key a module sees was the
event name alone, so a manifest declaring `consumes: builder.built` produced a
pattern that could never match what it was compared against — and a module
consuming one event from two emitters could only tell them apart by reading a
header. The subject already carries the emitter, so naming it in the key makes a
mismatch between manifest and code a typo instead of a category error.

Both matchers accept `**` for the rest of a name, which is how a manifest spells
it; the old bus's `#` still works, because both buses ship until the rollout.

src/broker-nats.ts

@@ -255,11 +255,23 @@ function toEnvelope<T>(msg: JsMsg): Envelope<T> {
   };
 }
 
-/** The event key inside a module's event subject. */
+/** The event key a module sees: the emitter and the event, which is exactly how its manifest names
+ *  what it consumes (novox/hq design 29 §1, 04-ISSUES/127).
+ *
+ *  **One vocabulary for the declaration and the handler.** This returned the event name alone, so a
+ *  manifest declaring `consumes: builder.built` produced a handler pattern that could never match
+ *  the key it was compared against — and a module consuming the same event from two emitters could
+ *  not tell them apart except by reading a header. The subject already carries the emitter; naming it
+ *  here makes a mismatch between manifest and code a typo rather than a category error. */
 function keyFromSubject(subject: string): string {
   const marker = ".event.";
   const at = subject.indexOf(marker);
-  return at < 0 ? subject : subject.slice(at + marker.length);
+  if (at < 0) return subject;
+  const event = subject.slice(at + marker.length);
+  // `mesh.mod.<emitter>.event.…` — the emitter is the token before the marker.
+  const before = subject.slice(0, at).split(".");
+  const emitter = before[before.length - 1];
+  return emitter ? `${emitter}.${event}` : event;
 }
 
 /** A module's own event subject. Derived, never taken from the caller: the module names its
@@ -325,7 +337,9 @@ export function topicMatches(pattern: string, key: string): boolean {
 
 function matchFrom(p: string[], pi: number, k: string[], ki: number): boolean {
   if (pi === p.length) return ki === k.length;
-  if (p[pi] === "#") {
+  // `**` is the mesh's wildcard for the rest of a name; `#` is the old bus's, accepted so a pattern
+  // written either way behaves the same while both buses ship (novox/hq design 29 §1).
+  if (p[pi] === "#" || p[pi] === "**") {
     for (let skip = ki; skip <= k.length; skip++) {
       if (matchFrom(p, pi + 1, k, skip)) return true;
     }