E-3: mesh_wait takes any event name (issue 1966)

waitAnswer no longer reads the membership: each name becomes its subjects
through buscompose.EventSubjects, optionally narrowed by from (seat, module or
stream), at most 16 names, a subject once; the heard event is named by
buscompose.EventName with its namespace and its own time, and a decided event
says the operator's answer is read only with claude_code_answer. WaitIssued and
Membership.Waits go; the refusals are one table.

Builds: design 34 every-event §13, §15, §17, §19, §26

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

node-tools/internal/bus/bus.go

@@ -75,9 +75,6 @@ type Membership struct {
 	// Hears are the module streams the module hears, each through a durable consumer on that stream the
 	// runtime binds beside the one on EVENTS (ADR 0363 §8).
 	Hears []HeardIssued `json:"hears,omitempty"`
-	// Waits are the event families a session may wait on through the mesh MCP server (novox/hq ADR 0367 §2):
-	// the tool runner's alone, composed from its manifest with the grant that lets it subscribe them.
-	Waits []WaitIssued `json:"waits,omitempty"`
 	// Bindings are the module's bus state in the new form, by local name (novox/hq ADR 0595 §1, mesh-sdk
 	// membership.BusBinding): its object stores, streams, work queues and ledgers, its own alone (bindings.go).
 	Bindings []membership.BusBinding `json:"bindings,omitempty"`

node-tools/internal/bus/wait.go

@@ -17,13 +17,6 @@ import (
 // subscribes the subjects when called and unsubscribes them before it answers, so an event published
 // between two calls is not heard — a session reads the state from its owner after every wake (§4).
 
-// WaitIssued is one event family the mesh issued this account to wait on (ADR 0367 §2): the name a session
-// asks for, and the subject it lands on. Only the tool runner's membership carries any.
-type WaitIssued struct {
-	Event   string `json:"event"`
-	Subject string `json:"subject"`
-}
-
 // Heard is one event a wait heard: the subject it arrived on, its body, when it arrived, and when it was published, the
 // event's own header `x-time` as its emitter wrote it, empty for an event that carries none (design 34 every-event §12).
 type Heard struct {