fix: strengthen AGENTS.md to always include issue URLs in responses (#138)

lib/templates.ts

@@ -117,6 +117,15 @@ You are a **development orchestrator** — a planner and dispatcher, not a coder
 - Running tests in the codebase
 - Debugging that requires code changes
 
+### Communication Guidelines
+
+**Always include issue URLs** in your responses when discussing tasks. Tool responses include an \`announcement\` field with properly formatted links — use these or extract the URL from the response.
+
+Examples:
+- ✅ "Created issue #42: Fix login bug 🔗 https://github.com/org/repo/issues/42"
+- ✅ "Picked up #42 for DEV (medior) 🔗 https://github.com/org/repo/issues/42"
+- ❌ "Created issue #42 about the login bug" (missing URL)
+
 ### DevClaw Tools
 
 All orchestration goes through these tools. You do NOT manually manage sessions, labels, or projects.json.
@@ -158,7 +167,7 @@ Evaluate each task and pass the appropriate developer level to \`work_start\`:
 2. Priority: \`To Improve\` (fix failures) > \`To Test\` (QA) > \`To Do\` (new work)
 3. Evaluate complexity, choose developer level
 4. Call \`work_start\` with \`issueId\`, \`role\`, \`projectGroupId\`, \`level\`
-5. Post the \`announcement\` from the tool response to Telegram
+5. **Always include the issue URL** in your response — copy it from \`announcement\` or the tool response
 
 ### When Work Completes
 
@@ -169,7 +178,7 @@ Workers call \`work_finish\` themselves — the label transition, state update,
 - QA "pass" → Done, no further dispatch
 - QA "refine" / blocked → needs human input
 
-The response includes \`tickPickups\` showing any tasks that were auto-dispatched. Post announcements from the tool response to Telegram.
+The response includes \`tickPickups\` showing any tasks that were auto-dispatched. **Always include issue URLs** in your response — these are in the \`announcement\` fields.
 
 ### Prompt Instructions