E-5 marked waits: a wait on a marked event runs only on the operator's warrant for that one wait

mesh_wait goes through the runner's approval gate (node-tools/internal/approval, Gate.Waited): a wait whose
subjects overlap a marked subject of any module the catalog half lists (the newest entry of every followed
branch, with the served entry of each module this runner serves) is an act of the runner's own module and
build (MESH_FINGERPRINT at its start), asked once on operator-channel as "Wait on <names> on <node>?", and
held, subscribing nothing but its ask's decided, until its timeout, its caller's going or the choice. On a
warrant it subscribes, its timeout running from then, and answers {answer, approval}. Before the marks are
read nothing is asked; a wait from a seat is never marked. The state fixture moves to meshtest so the
console's table can hold a gate.

Builds: design 34 every-event §34, §35, §36, §37; design 47 G lead answer A-168

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

node-tools/internal/firstview/approval.go

@@ -78,6 +78,20 @@ func (c approvalCatalog) Definitions() map[string]seatdef.Definition {
 	return c.defs()
 }
 
+func (c approvalCatalog) Entries() []catalogseat.CatalogEntry {
+	halves, err := c.v.Halves()
+	if err != nil {
+		return nil
+	}
+	var out []catalogseat.CatalogEntry
+	for _, half := range halves {
+		for _, e := range half.Entries {
+			out = append(out, e)
+		}
+	}
+	return out
+}
+
 type notFollowed struct{}
 
 func (notFollowed) Error() string { return "the catalog half is not followed by this runner" }