CAT-N8: a person's create, apply, recreate and drop are handed to the keeper as the caller the tool runner proved

The bus module's tools hold no grant of the seat's acting verbs (design 25
§ 12.3): nats_create, nats_apply, nats_recreate and nats_drop write a request
into the keeper's own state requests, stamped with stdio.CallerOf (a name in
the arguments is never the caller), and read its end back. recreate and drop
raise the operator's ask first, its option binding exactly that act; the
keeper acts only on the router's warrant for it (Warrant.For, Option.Performs),
after a snapshot of the entry's streams (bussnap, moved from the snapshot
command with a streams filter), says recreated or dropped, and records every
act as a hand act through mesh-hand-acts. A drop removes an orphan alone.

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

modules/nats/module.json

@@ -115,7 +115,11 @@
     "nats_bucket_remove",
     "nats_stream_remove",
     "nats_bucket_expiry",
-    "nats_history"
+    "nats_history",
+    "nats_create",
+    "nats_apply",
+    "nats_recreate",
+    "nats_drop"
   ],
   "guards": [
     8222
@@ -232,7 +236,8 @@
       "env": {
         "MESH_BROKER_FILE": "${dir:keeper-state}/broker-keeper",
         "MESH_NATS_FULL_RAISE": "75",
-        "MESH_NATS_FULL_CLEAR": "70"
+        "MESH_NATS_FULL_CLEAR": "70",
+        "MESH_NATS_SNAPSHOTS_DIR": "${dir:keeper-state}"
       },
       "bus": {
         "state": [