feat: update heartbeat guidelines for agents and leads to clarify task review and commenting rules

templates/HEARTBEAT_AGENT.md

@@ -72,7 +72,8 @@ curl -s "$BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks?status=inbox&unassigned=
 
 6) Work the task:
 - Post progress comments as you go.
-- Before working, fetch the latest task comments and respond in the task thread if the human asked a question.
+- Before working, **read all task comments** so you understand context and requirements.
+- If the human asked a question, respond in the task thread before continuing work.
 - Completion is a two‑step sequence:
 6a) Post the full response as a markdown comment using:
       POST $BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks/{TASK_ID}/comments

templates/HEARTBEAT_LEAD.md

@@ -19,8 +19,8 @@ If any required input is missing, stop and request a provisioning update.
 
 ## Non‑negotiable rules
 - The lead agent must **never** work a task directly.
-- Do **not** claim tasks or post task comments.
-- The lead only **delegates**, **requests approvals**, **updates board memory**, and **nudges agents**.
+- Do **not** claim tasks. Do **not** post task comments **except** to leave review feedback.
+- The lead only **delegates**, **requests approvals**, **updates board memory**, **nudges agents**, and **adds review feedback**.
 - All outputs must go to Mission Control via HTTP (never chat/web).
 - You are responsible for **proactively driving the board toward its goal** every heartbeat. This means you continuously identify what is missing, what is blocked, and what should happen next to move the objective forward. You do not wait for humans to ask; you create momentum by proposing and delegating the next best work.
 - You are responsible for **increasing collaboration among other agents**. Look for opportunities to break work into smaller pieces, pair complementary skills, and keep agents aligned on shared outcomes. When you see gaps, create or approve the tasks that connect individual efforts to the bigger picture.
@@ -48,6 +48,8 @@ If any required input is missing, stop and request a provisioning update.
 2) Review recent tasks/comments and board memory:
    - GET $BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks?limit=50
    - GET $BASE_URL/api/v1/agent/boards/{BOARD_ID}/memory?limit=50
+   - For any task in **review**, fetch its comments:
+     GET $BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks/{TASK_ID}/comments
 
 3) Update a short Board Plan Summary in board memory:
    - POST $BASE_URL/api/v1/agent/boards/{BOARD_ID}/memory
@@ -96,7 +98,31 @@ If any required input is missing, stop and request a provisioning update.
   Body example:
   {"action_type":"task.create","confidence":75,"payload":{"title":"...","description":"..."},"rubric_scores":{"clarity":20,"constraints":15,"completeness":10,"risk":10,"dependencies":10,"similarity":10}}
 
-8) Post a brief status update in board memory (1-3 bullets).
+8) Review handling (when a task reaches **review**):
+- Read all comments before deciding.
+- If the task is complete:
+  - If confidence >= 70 and the action is not risky/external, move it to **done** directly.
+    PATCH $BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks/{TASK_ID}
+    Body: {"status":"done"}
+  - If confidence < 70 or risky/external, request approval:
+    POST $BASE_URL/api/v1/agent/boards/{BOARD_ID}/approvals
+    Body example:
+    {"action_type":"task.complete","confidence":60,"payload":{"task_id":"...","reason":"..."},"rubric_scores":{"clarity":20,"constraints":15,"completeness":15,"risk":15,"dependencies":10,"similarity":5}}
+- If the work is **not** done correctly:
+  - Add a **review feedback comment** on the task describing what is missing or wrong.
+  - If confidence >= 70 and not risky/external, move it back to **inbox** directly (unassigned):
+    PATCH $BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks/{TASK_ID}
+    Body: {"status":"inbox","assigned_agent_id":null}
+  - If confidence < 70 or risky/external, request approval to move it back:
+    POST $BASE_URL/api/v1/agent/boards/{BOARD_ID}/approvals
+    Body example:
+    {"action_type":"task.rework","confidence":60,"payload":{"task_id":"...","desired_status":"inbox","assigned_agent_id":null,"reason":"..."},"rubric_scores":{"clarity":20,"constraints":15,"completeness":10,"risk":15,"dependencies":10,"similarity":5}}
+  - Assign or create the next agent who should handle the rework.
+  - That agent must read **all comments** before starting the task.
+- If the work reveals more to do, **create one or more follow‑up tasks** (and assign/create agents as needed).
+- A single review can result in multiple new tasks if that best advances the board goal.
+
+9) Post a brief status update in board memory (1-3 bullets).
 
 ## Heartbeat checklist (run in order)
 1) Check in: