feat: update .gitignore to include flows directory and adjust clawteam templates exclusion; enhance LEARNINGS.md and RULES.md with critical spawn method guidelines; revise TOOLS.md to emphasize tmux usage; modify SKILL.md files to prohibit subprocess backend; increase memory limit in docker-compose.yml

.openclaw/workspace/RULES.md

@@ -149,5 +149,20 @@ When PM receives escalated issue:
 4. If re-assigning: new worker gets full context (error logs, target files, what was tried)
 5. Never add rework to existing blocked task — either unblock it or reassign entirely
 
-### 6. Usage Pattern
+### 6. Spawn Method (ABSOLUTE RULE — ZERO EXCEPTIONS)
+**ALWAYS** use `clawteam spawn tmux openclaw --team <team> --agent-name <name> --agent-type <type> --task "<task>"`
+**NEVER EVER** use `clawteam spawn subprocess` — subprocess agents die immediately after the shell exits, resulting in:
+- All spawned agents dying instantly (0 workers alive)
+- Task counts stuck at 0 in_progress, 75+ tasks never started
+- False "completed" statuses (files created by manual copy, not by agents)
+- Zero dependency tracking despite clear ordering requirements
+- Complete project management failure
+
+**Verification after spawning:**
+- `tmux list-sessions | grep clawteam` — expect 1 session per agent
+- `clawteam task list <team> --status in_progress` — expect tasks actively working
+- `clawteam board attach <team>` — monitor progress in real-time
+- `clawteam task list <team> --status blocked` — check for blocked tasks and resolve
+
+### 7. Usage Pattern
 When the user requests to use ClawTeam, do NOT use `sessions_spawn` with `runtime="acp"`. Instead, follow the official ClawTeam CLI usage from its README: https://github.com/HKUDS/ClawTeam. Use the `clawteam` command directly (via `exec`) for team orchestration, worker spawning, and task management.