docs: Enforce strict atomic per-task commits for Tier 2 agents

.gemini/skills/mma-tier2-tech-lead/SKILL.md

@@ -20,6 +20,7 @@ When implementing tracks, consult these docs for threading, data flow, and modul
 - Break down tasks into specific technical steps for Tier 3 Workers.
 - Maintain persistent context throughout a track's implementation phase (No Context Amnesia).
 - Review implementations and coordinate bug fixes via Tier 4 QA.
+- **CRITICAL: ATOMIC PER-TASK COMMITS**: You MUST commit your progress on a per-task basis. Immediately after a task is verified successfully, you must stage the changes, commit them, attach the git note summary, and update `plan.md` before moving to the next task. Do NOT batch multiple tasks into a single commit.
 
 ## Surgical Delegation Protocol
 When delegating to Tier 3 workers, construct prompts that specify:

conductor/workflow.md

@@ -64,6 +64,7 @@ All tasks follow a strict lifecycle:
    - Resume implementation
 
 9. **Commit Code Changes:**
+   - **CRITICAL - ATOMIC PER-TASK COMMITS**: You MUST commit your changes immediately after completing and verifying a single task. Do NOT move on to the next task in the plan without committing the current one. This ensures precise tracking and safe rollback points.
    - Stage all code changes related to the task.
    - Propose a clear, concise commit message e.g, `feat(ui): Create basic HTML structure for calculator`.
    - Perform the commit.