feat: implement task creation endpoint for board leads and enhance board chat functionality

templates/AGENTS.md

@@ -36,4 +36,5 @@ Write things down. Do not rely on short-term context.
 - Do not post task updates in chat/web channels under any circumstance.
 - You may include comments directly in task PATCH requests using the `comment` field.
 - Comments should be clear, well‑formatted markdown. Use headings, bullets, checklists, or tables when they improve clarity.
+- When you create or edit a task description, write it in clean markdown with short sections and bullets where helpful.
 - Every status change must include a comment within 30 seconds (see HEARTBEAT.md).

templates/HEARTBEAT_AGENT.md

@@ -22,12 +22,19 @@ If any required input is missing, stop and request a provisioning update.
 - When it improves clarity, use headings, bullets, checklists, tables, or short sections. You do not need to use them for every comment.
 - Every status change must have a comment within 30 seconds.
 - Do not claim a new task if you already have one in progress.
+- If you edit a task description, write it in clean markdown (short sections, bullets/checklists when helpful).
 
 ## Task mentions
 - If you receive a TASK MENTION message or see your name @mentioned in a task comment, reply in that task thread even if you are not assigned.
 - Do not change task status or assignment unless you are the assigned agent.
 - Keep the reply focused on the mention request.
 
+## Board chat messages
+- If you receive a BOARD CHAT message or BOARD CHAT MENTION message, reply in board chat.
+- Use: POST $BASE_URL/api/v1/agent/boards/{BOARD_ID}/memory
+  Body: {"content":"...","tags":["chat"]}
+- Do not change task status based on board chat unless you are assigned the relevant task.
+
 ## Mission Control Response Protocol (mandatory)
 - All outputs must be sent to Mission Control via HTTP.
 - Always include: `X-Agent-Token: {{ auth_token }}`

templates/HEARTBEAT_LEAD.md

@@ -19,7 +19,7 @@ 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. Do **not** post task comments **except** to leave review feedback.
+- Do **not** claim tasks. Do **not** post task comments **except** to leave review feedback, respond to a @mention, or add clarifying questions on tasks you created.
 - 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.
@@ -30,6 +30,12 @@ If any required input is missing, stop and request a provisioning update.
 - If you are @mentioned in a task comment, you may reply **regardless of task status**.
 - Keep your reply focused and do not change task status unless it is part of the review flow.
 
+## Board chat messages
+- If you receive a BOARD CHAT message or BOARD CHAT MENTION message, reply in board chat.
+- Use: POST $BASE_URL/api/v1/agent/boards/{BOARD_ID}/memory
+  Body: {"content":"...","tags":["chat"]}
+- Board chat is your primary channel with the human; respond promptly and clearly.
+
 ## Mission Control Response Protocol (mandatory)
 - All outputs must be sent to Mission Control via HTTP.
 - Always include: `X-Agent-Token: {{ auth_token }}`
@@ -97,15 +103,21 @@ If any required input is missing, stop and request a provisioning update.
   }
 
 7) Creating new tasks:
-- Leads cannot create tasks directly (admin‑only).
-- If a new task is needed, request approval:
+- Leads **can** create tasks directly when confidence >= 70 and the action is not risky/external.
+  POST $BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks
+  Body example:
+  {"title":"...","description":"...","priority":"high","status":"inbox","assigned_agent_id":null}
+- Task descriptions must be written in clear markdown (short sections, bullets/checklists when helpful).
+- If confidence < 70 or the action is risky/external, request approval instead:
   POST $BASE_URL/api/v1/agent/boards/{BOARD_ID}/approvals
   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}}
+  {"action_type":"task.create","confidence":60,"payload":{"title":"...","description":"..."},"rubric_scores":{"clarity":20,"constraints":15,"completeness":10,"risk":10,"dependencies":10,"similarity":10}}
+- If you have follow‑up questions, still create the task and add a comment on that task with the questions. You are allowed to comment on tasks you created.
 
 8) Review handling (when a task reaches **review**):
 - Read all comments before deciding.
 - If the task is complete:
+  - Before marking **done**, leave a brief markdown comment explaining *why* it is done so the human can evaluate your reasoning.
   - 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"}
@@ -158,7 +170,7 @@ curl -s "$BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks?status=inbox&unassigned=
 
 ## Common mistakes (avoid)
 - Claiming or working tasks as the lead.
-- Posting task comments.
+- Posting task comments outside review, @mentions, or tasks you created.
 - Assigning a task to yourself.
 - Marking tasks review/done (lead cannot).
 - Using non‑agent endpoints or Authorization header.