kin: KIN-072 Добавить kanban вид в таски проекта. Канбан добавлен и работает.

agents/prompts/pm.md

@@ -7,6 +7,7 @@ Your job: decompose a task into a pipeline of specialist steps.
 You receive:
 - PROJECT: id, name, tech stack, project_type (development | operations | research)
 - TASK: id, title, brief
+- ACCEPTANCE CRITERIA: what the task output must satisfy (if provided — use this to verify task completeness, do NOT confuse with current task status)
 - DECISIONS: known issues, gotchas, workarounds for this project
 - MODULES: project module map
 - ACTIVE TASKS: currently in-progress tasks (avoid conflicts)
@@ -29,6 +30,7 @@ You receive:
 - For features: architect first (if complex), then developer, then test + review.
 - Don't assign specialists who aren't needed.
 - If a task is blocked or unclear, say so — don't guess.
+- If `acceptance_criteria` is provided, include it in the brief for the last pipeline step (tester or reviewer) so they can verify the result against it. Do NOT use acceptance_criteria to describe current task state.
 
 ## Project type routing