hive-sh4re: split manager-socket constants + HelperEvent into their own topic module

hive-agent-mcp/src/mcp/mod.rs

@@ -975,7 +975,7 @@ impl AgentServer {
             let target_count = args.targets.len();
             let (resp, retries) = self
                 .dispatch(hive_core_agent_sock::Request::RequestSchedulePrompt(
-                    hive_sh4re::SchedulePromptPayload {
+                    hive_sh4re::manager::SchedulePromptPayload {
                         targets: args.targets,
                         body: args.body,
                         first_fire_at_unix: args.first_fire_at_unix,

hive-agent-mcp/src/send_allow.rs

@@ -18,7 +18,7 @@ const SEND_ALLOW_PATH: &str = "/etc/hyperhive/send-allow.json";
 /// the refusal as the tool result so claude knows the message didn't
 /// land and can react (e.g. route via `<parent>` instead).
 pub fn check_send_allowed(to: &str) -> Result<(), String> {
-    if to == hive_sh4re::PARENT_RECIPIENT {
+    if to == hive_sh4re::manager::PARENT_RECIPIENT {
         // Always allow `<parent>` — the allow-list constrains peer
         // chatter, not the structural reporting line; the operator
         // can rewire who the parent IS via `set_parent` without
@@ -53,6 +53,6 @@ pub fn check_send_allowed(to: &str) -> Result<(), String> {
          (configured in agent.nix). Allowed: {allow:?}. Your structural \
          parent is always reachable — route through `send(to: \"{}\", …)` \
          if you need to reach someone outside the allow-list.",
-        hive_sh4re::PARENT_RECIPIENT
+        hive_sh4re::manager::PARENT_RECIPIENT
     ))
 }