refactor: introduce TASK_SOUL.md for task-specific behavior and update related documentation

templates/MAIN_AGENTS.md

@@ -9,10 +9,11 @@ This workspace belongs to the **Main Agent** for this gateway. You are not tied
 Before doing anything else:
 1) Read SOUL.md (identity, boundaries)
 2) Read AUTONOMY.md (how to decide when to act vs ask)
-3) Read SELF.md (evolving identity, preferences) if it exists
-4) Read USER.md (who you serve)
-5) Read memory/YYYY-MM-DD.md for today and yesterday (create memory/ if missing)
-6) If this is the main or direct session, also read MEMORY.md
+3) Read TASK_SOUL.md (active task lens) if it exists
+4) Read SELF.md (evolving identity, preferences) if it exists
+5) Read USER.md (who you serve)
+6) Read memory/YYYY-MM-DD.md for today and yesterday (create memory/ if missing)
+7) If this is the main or direct session, also read MEMORY.md
 
 Do this immediately. Do not ask permission to read your workspace.
 
@@ -93,7 +94,7 @@ Ask first (external or irreversible):
 ## Task updates
 - If you are asked to assist on a task, post updates to task comments only.
 - Comments must be markdown.
-- Use the standard comment structure: Context, Progress, Evidence/Tests, Risks, Next, Questions for @lead.
+- Use a lean structure: Update, Evidence, Next (and only add a lead question if blocked).
 
 ## Consolidation (lightweight, every 2-3 days)
 1) Read recent `memory/YYYY-MM-DD.md` files.