feat(gateway): add endpoint for user outreach via gateway main agent

templates/HEARTBEAT_LEAD.md

@@ -66,6 +66,12 @@ Comment template (keep it small; 1-3 bullets per section; omit what is not appli
 - Board chat is your primary channel with the human; respond promptly and clearly.
 - If someone asks for clarity by tagging `@lead`, respond with a crisp decision, delegation, or next action to unblock them.
 
+## Request user input via gateway main (OpenClaw channels)
+- If you need information from the human but they are not responding in Mission Control board chat, ask the gateway main agent to reach them via OpenClaw's configured channel(s) (Slack/Telegram/SMS/etc).
+- POST `$BASE_URL/api/v1/agent/boards/$BOARD_ID/gateway/main/ask-user`
+  - Body: `{"content":"<question>","correlation_id":"<optional>","preferred_channel":"<optional>"}`
+- The gateway main will post the user's answer back to this board as a NON-chat memory item tagged like `["gateway_main","user_reply"]`.
+
 ## Gateway main requests
 - If you receive a message starting with `GATEWAY MAIN`, treat it as high priority.
 - Do **not** reply in OpenClaw chat. Reply via Mission Control only.

templates/MAIN_AGENTS.md

@@ -62,6 +62,11 @@ Board lead replies:
 - Read replies via:
   - GET `$BASE_URL/api/v1/agent/boards/<BOARD_ID>/memory?is_chat=false&limit=50`
 
+## User outreach requests (from board leads)
+- If you receive a message starting with `LEAD REQUEST: ASK USER`, a board lead needs human input but cannot reach them in Mission Control.
+- Use OpenClaw's configured channel(s) to reach the user (Slack/Telegram/SMS/etc). If that fails, post the question into Mission Control board chat as a fallback.
+- When you receive the user's answer, write it back to the originating board as a NON-chat memory item tagged like `["gateway_main","user_reply"]` (the exact POST + tags will be included in the request message).
+
 ## Tools
 - Skills are authoritative. Follow SKILL.md instructions exactly.
 - Use TOOLS.md for environment-specific notes.

templates/MAIN_HEARTBEAT.md

@@ -19,6 +19,7 @@ If any required input is missing, stop and request a provisioning update.
 ## Schedule
 - If a heartbeat schedule is configured, send a lightweight check‑in only.
 - Do not claim or move board tasks unless explicitly instructed by Mission Control.
+- If you have any pending `LEAD REQUEST: ASK USER` messages in OpenClaw chat, handle them promptly (see MAIN_AGENTS.md).
 
 ## Heartbeat checklist
 1) Check in: