feat: add Atomizer HQ multi-agent cluster infrastructure

- 8-agent OpenClaw cluster (Manager, Tech-Lead, Secretary, Auditor,
  Optimizer, Study-Builder, NX-Expert, Webster)
- Orchestration engine: orchestrate.py (sync delegation + handoffs)
- Workflow engine: YAML-defined multi-step pipelines
- Agent workspaces: SOUL.md, AGENTS.md, MEMORY.md per agent
- Shared skills: delegate, orchestrate, atomizer-protocols
- Capability registry (AGENTS_REGISTRY.json)
- Cluster management: cluster.sh, systemd template
- All secrets replaced with env var references

hq/skills/atomizer-protocols/protocols/OP_09_AGENT_HANDOFF.md

@@ -0,0 +1,60 @@
+# OP_09 — Agent Handoff Protocol
+
+## Purpose
+Defines how agents pass work to each other in a structured, traceable way.
+
+## When to Use
+- Manager assigns work to a specialist
+- One agent's output becomes another's input
+- An agent needs help from another agent's expertise
+
+## Handoff Format
+
+When handing off work, include ALL of the following:
+
+```
+## Handoff: [Source Agent] → [Target Agent]
+
+**Task:** [What needs to be done — clear, specific, actionable]
+**Context:** [Why this is needed — project, deadline, priority]
+**Inputs:** [What the target agent needs — files, data, previous analysis]
+**Expected Output:** [What should come back — format, level of detail]
+**Protocol:** [Which protocol applies — OP_01, SYS_15, etc.]
+**Deadline:** [When this is needed — explicit or "ASAP"]
+**Thread:** [Link to relevant Slack thread for context]
+```
+
+## Rules
+
+1. **Manager initiates most handoffs.** Other agents don't directly assign work to peers unless specifically authorized.
+2. **Always include context.** The target agent shouldn't need to search for background.
+3. **One handoff per message.** Don't bundle multiple tasks.
+4. **Acknowledge receipt.** Target agent confirms they've received and understood the handoff.
+5. **Report completion.** Target agent posts results in the same thread and notifies the source.
+
+## Escalation
+If the target agent can't complete the handoff:
+1. Reply in the same thread explaining why
+2. Propose alternatives
+3. Manager decides next steps
+
+## Examples
+
+### Good Handoff
+```
+## Handoff: Manager → Technical Lead
+
+**Task:** Break down the StarSpec M1 WFE optimization requirements
+**Context:** New client project. Contract attached. Priority: HIGH.
+**Inputs:** Contract PDF (attached), model files in knowledge_base/projects/starspec-m1/
+**Expected Output:** Parameter list, objectives, constraints, solver recommendation
+**Protocol:** OP_01 (Study Lifecycle) + OP_10 (Project Intake)
+**Deadline:** EOD today
+**Thread:** #starspec-m1-wfe (this thread)
+```
+
+### Bad Handoff
+```
+@technical do the breakdown thing for the new project
+```
+*(Missing: context, inputs, expected output, deadline, protocol)*