@damper/mcp 0.10.5 → 0.10.7

package/dist/index.js

@@ -484,13 +484,15 @@ server.registerTool('start_task', {
 server.registerTool('add_note', {
     title: 'Add Note',
     description: 'Add a note to a task. Use ONLY for non-obvious approach decisions and blockers.\n\n' +
-        '**When to use:**\n' +
-        '- Decisions: "Decision: Using X because Y"\n' +
-        '- Blockers: "Blocked: X needs Y before we can proceed"\n\n' +
-        '**Do NOT use for:** Session start/end ceremony, commit logging (use `add_commit`), or restating what code changes do.',
+        '**Do NOT use for:** Session start/end ceremony, commit logging (use `add_commit`), or restating what code changes do.\n\n' +
+        '**Templates** (copy and fill in):\n\n' +
+        'Decision:\n```\n**Decision:** Chose `libraryName` over `alternative` because it supports X and has fewer dependencies\n```\n\n' +
+        'Blocker:\n```\n**Blocked:** Cannot proceed with `featureName` until:\n- Dependency X is merged\n- API endpoint Y is available\n```\n\n' +
+        'Observation:\n```\n**Note:** Found that `componentName` already handles X via `methodName` — reusing instead of reimplementing\n```',
     inputSchema: z.object({
         taskId: z.string(),
-        note: z.string(),
+        note: z.string().describe('Markdown-formatted note. Start with a **bold label** (Decision/Blocked/Note), ' +
+            'use `code` for technical names, and bullet lists for multiple points.'),
     }),
     outputSchema: z.object({
         taskId: z.string(),
@@ -851,7 +853,7 @@ This project uses Damper MCP for task tracking. **You MUST follow this workflow.
 ### While Working
 - **Do NOT commit or complete tasks without explicit user confirmation** - Always ask the user before running \`git commit\` or calling \`complete_task\`
 - \`add_commit\` after each commit with hash and message
-- \`add_note\` for decisions: "Decision: chose X because Y"
+- \`add_note\` for decisions (use markdown: **bold** labels, \`code\`, bullet lists)
 - \`update_subtask\` to mark subtask progress
 - **Follow patterns from project context** - Don't reinvent; use existing conventions
 - When you need architecture context mid-task, use \`get_section_block_content\` to load specific blocks rather than full sections
@@ -1390,6 +1392,9 @@ server.registerTool('get_feedback', {
         f.linkedTaskId ? `Linked: ${f.linkedTaskId}` : '',
         `\n${f.description}`,
     ].filter(Boolean);
+    if (f.aiSummary) {
+        parts.push(`\n## AI Summary\n${f.aiSummary}`);
+    }
     if (f.metadata && typeof f.metadata === 'object' && Object.keys(f.metadata).length > 0) {
         const meta = f.metadata;
         parts.push(`\n## Debug Info`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@damper/mcp",
-  "version": "0.10.5",
+  "version": "0.10.7",
   "description": "MCP server for Damper task management",
   "author": "Damper <hello@usedamper.com>",
   "repository": {