@papi-ai/server 0.7.31 → 0.7.33

package/dist/prompts.js

@@ -394,7 +394,7 @@ ${AD_REJECTION_RULES}
    - **Surprises:** If a surprise reveals a gap (e.g. "schema assumed but not verified"), propose a task to close it.
    - **Architecture Notes:** If a pattern was established that needs follow-up (e.g. "shared service layer created, MCP migration needed"), propose the follow-up.
    - **Strategy gaps:** If an Active Decision has no board tasks supporting it, propose one.
-   - **Dogfood observations:** If unactioned dogfood entries are listed in context (with IDs), check if any map to existing tasks. If not, propose a new task. **CRITICAL: Include \`dogfood:<uuid>\` in the new task's \`notes\` field** (e.g. \`"notes": "Addresses recurring friction. dogfood:abc12345-..."\`). This links the task to the observation so the pipeline can track what was actioned. Without this annotation, the observation stays unactioned forever.
+   - **Dogfood observations:** Unactioned dogfood entries span FOUR categories (friction, methodology, signal, commercial) \u2014 consider ALL of them, not just friction. If an entry (with ID) maps to no existing task, propose one, matching task type to category: friction/signal \u2192 fix or improvement; methodology \u2192 process/tooling change; commercial \u2192 GTM/positioning. **CRITICAL: Include \`dogfood:<uuid>\` in the new task's \`notes\` field** (e.g. \`"notes": "dogfood:abc12345-..."\`). This links the task to the observation so the pipeline can track what was actioned. Without this annotation, the observation stays unactioned forever.
    Create new tasks via the \`newTasks\` array in Part 2. Use \`new-N\` IDs in \`cycleHandoffs\` to reference them. **Limit: 3 new tasks per cycle** to prevent backlog bloat.
    **\u26A0\uFE0F DUPLICATE CHECK:** Before adding a task to \`newTasks\`, scan the Cycle Board above for any existing task with the same or very similar title/scope. If a matching task already exists (even with slightly different wording), do NOT create a duplicate \u2014 reference the existing task ID instead. The board already contains all active tasks; re-creating them wastes IDs and bloats the board.
    **\u26A0\uFE0F ALREADY-BUILT CHECK:** Before creating a task, check the recent build reports and cycle log for evidence that this capability was already shipped. If a recent build report shows this feature was completed (even under a different task name), do NOT create a new task for it. This is especially important for UI features, data models, and integrations that may already exist.`);
@@ -776,7 +776,7 @@ For every stale or unresolved item you call out, propose a concrete next step (p
 
 6. **Security Posture Review** \u2014 Only if \`[SECURITY]\` tags exist in recent cycle logs.
 
-7. **Dogfood Friction \u2192 Task Conversion** \u2014 Scan dogfood observations for recurring friction (2+ occurrences without a board task). Convert up to 3 to task proposals via \`actionItems\` in Part 2. Skip if nothing recurring.
+7. **Dogfood Observations \u2192 Task Conversion** \u2014 Scan dogfood observations across ALL FOUR categories (friction, methodology, signal, commercial), not just friction, for recurring or clearly-actionable items with no board task. Convert up to 3 to task proposals via \`actionItems\` in Part 2, and tag each new task's notes with \`dogfood:<uuid>\` so the pipeline marks the observation actioned. Match task type to category: friction/signal \u2192 fix or improvement; methodology \u2192 process/tooling change; commercial \u2192 GTM/positioning. Skip if nothing actionable.
 
 8. **Architecture Health** \u2014 Only flag genuine broken data paths, config drift, or dead code. Keep it brief \u2014 bullet points, not paragraphs. Skip entirely if nothing found.
 ${compressionJob}
@@ -805,7 +805,7 @@ Write your Strategy Review in markdown. Cover the 5 mandatory sections in order:
 
 Then include conditional sections only if genuinely useful:
 - **Security Posture Review** \u2014 only if [SECURITY] tags exist
-- **Dogfood Friction \u2192 Tasks** \u2014 only if recurring unaddressed friction
+- **Dogfood Observations \u2192 Tasks** \u2014 only if recurring or clearly-actionable observations exist (any of the four categories: friction, methodology, signal, commercial)
 - **Architecture Health** \u2014 only if broken data paths or config drift found${compressionPart1}
 
 **FORMAT GUIDELINES:**

package/package.json

@@ -1,8 +1,9 @@
 {
   "name": "@papi-ai/server",
-  "version": "0.7.31",
+  "version": "0.7.33",
   "description": "PAPI MCP server — AI-powered sprint planning, build execution, and strategy review for software projects",
   "license": "Elastic-2.0",
+  "mcpName": "io.github.cathalos92/papi",
   "type": "module",
   "main": "./dist/index.js",
   "exports": {
@@ -48,6 +49,8 @@
   "dependencies": {
     "@anthropic-ai/sdk": "^0.82.0",
     "@modelcontextprotocol/sdk": "^1.27.1",
+    "@papi-ai/adapter-md": "^0.2.0",
+    "@papi-ai/adapter-pg": "^0.2.0",
     "@papi-ai/skills": "^0.1.0",
     "js-yaml": "^4.1.0"
   },