@papi-ai/server 0.7.44 → 0.7.46

package/dist/prompts.js

@@ -512,6 +512,16 @@ function buildPlanUserMessage(ctx) {
     if (ctx.board) {
       parts.push("### Board", "", ctx.board, "");
     }
+    if (ctx.resurfacedBlockers) {
+      parts.push(
+        "### Ready to Unblock (typed blockers now resolved)",
+        "",
+        "These tasks are Blocked but their typed dependency has cleared. Treat them as actionable candidates \u2014 resurface them into the cycle (or confirm they still belong Blocked), do not leave them sitting.",
+        "",
+        ctx.resurfacedBlockers,
+        ""
+      );
+    }
     if (ctx.candidateTaskFullNotes) {
       parts.push("### Full Notes for Candidate Tasks", "", ctx.candidateTaskFullNotes, "");
     }
@@ -649,6 +659,14 @@ function buildHandoffsOnlyUserMessage(inputs) {
   }
   return parts.join("\n");
 }
+function extractDependencyChain(displayText) {
+  const match = displayText.match(
+    /^##\s+Dependency Chain[^\n]*\n([\s\S]*?)(?=\n#{2,3}\s|$(?![\s\S]))/m
+  );
+  if (!match) return void 0;
+  const body = match[1].trim();
+  return body.length > 0 ? body : void 0;
+}
 function parseStructuredOutput(raw) {
   const marker = "<!-- PAPI_STRUCTURED_OUTPUT -->";
   const markerIdx = raw.indexOf(marker);
@@ -664,6 +682,7 @@ function parseStructuredOutput(raw) {
   try {
     const parsed = JSON.parse(jsonMatch[1].trim());
     const data = coerceStructuredOutput(parsed);
+    data.dependencyChain = extractDependencyChain(displayText);
     return { displayText, data };
   } catch {
     return { displayText, data: null };
@@ -751,6 +770,7 @@ IMPORTANT: You are running as a non-interactive API call. Do NOT ask the user qu
 - **Product impact first, process second.** The reader wants to know: what got better for users, what's broken, what opportunities exist. Internal machinery (AD wording, taxonomy labels, hierarchy status) is secondary \u2014 handle it in a compact appendix, not the main review.
 - **Lead with insight, not data recitation.** Open each section with the strategic takeaway or pattern, THEN support it with cycle data and task references. Bad: "C131 built task-700, C132 built task-710." Good: "The last 5 cycles show a clear shift from infrastructure to user-facing work \u2014 80% of tasks were dashboard or onboarding, up from 30% in the prior review window."
 - **Cycle data first, conversation context second.** Base your review on build reports, cycle logs, board state, and ADs \u2014 not on whatever was discussed earlier in the conversation. If recent conversation context conflicts with the data, flag it but trust the data.
+- **Verify before claiming \u2014 your context is a snapshot, not live state.** The task bodies, doc summaries, prior strategy reviews, and zoom-out framing you were given were written in the cycle they are dated; the product and codebase have moved since. Treat every present-tense claim about current product or code state \u2014 "X is broken", "Y only works in Z", "feature not built", "metric unmeasured", a stalled task "still needs building" \u2014 as a HYPOTHESIS to check, not a fact. If you have tools to inspect the live code or dashboard (grep, file read, running app), verify the claim before asserting it. If you cannot verify, attribute and hedge it explicitly ("per task-NNNN's C303 framing \u2014 unverified against current code") rather than stating it as current fact. A confident claim the reader can falsify in one grep destroys the review's credibility. **Stalled tasks are the highest-risk case:** a task sitting in Backlog for many cycles is frequently already shipped under another task and never closed \u2014 check the code before recommending you build, cancel, or defer it.
 - **Be concise and scannable.** Use short paragraphs, bullet points, and clear headings. Avoid walls of text. The review should be readable in 3 minutes, not 15. Format cycle summaries as compact bullet points, not multi-paragraph narratives.
 - **Every conditional section earns its place.** If a conditional section has nothing meaningful to say, skip it entirely. Do not write "No issues found" or "No concerns" \u2014 just omit the section.
 - **AD housekeeping is an appendix, not the centerpiece.** Just list changes and make them. Don't score every AD individually. Don't ask for approval on wording tweaks \u2014 small changes (confidence bumps, deleting stale ADs, fixing wording) should just happen. Only flag ADs that represent a genuine strategic question.
@@ -1491,6 +1511,7 @@ export {
   buildReviewSystemPrompt,
   buildReviewUserMessage,
   buildVisionTasksPrompt,
+  extractDependencyChain,
   parseReviewStructuredOutput,
   parseStrategyChangeOutput,
   parseStructuredOutput

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@papi-ai/server",
-  "version": "0.7.44",
-  "description": "PAPI MCP server — AI-powered sprint planning, build execution, and strategy review for software projects",
+  "version": "0.7.46",
+  "description": "PAPI MCP server \u2014 AI-powered sprint planning, build execution, and strategy review for software projects",
   "license": "Elastic-2.0",
-  "mcpName": "io.github.cathalos92/papi",
+  "mcpName": "io.github.getpapi/papi",
   "type": "module",
   "main": "./dist/index.js",
   "exports": {
@@ -53,6 +53,7 @@
     "@modelcontextprotocol/sdk": "^1.27.1",
     "@papi-ai/adapter-md": "^0.2.0",
     "@papi-ai/adapter-pg": "^0.2.0",
+    "@papi-ai/shared": "^0.1.0",
     "@papi-ai/skills": "^0.1.0",
     "js-yaml": "^4.1.0"
   },

package/skills/papi-cycle/papi-advanced/SKILL.md

@@ -7,13 +7,13 @@ description: Invoke for cross-project patterns, dogfood-derived workflows, or ad
 
 ## When to Start a New Conversation
 
-Your AI host manages its own context — it compacts automatically as a conversation grows, so you rarely need to restart. **Stay in the same conversation by default.** Keep building, planning, and reviewing in one place; `orient` re-grounds you whenever you need it.
+Your AI host manages its own context — it compacts automatically as a conversation grows, so you almost never need to restart. **Stay in the same conversation.** Keep building, planning, and reviewing in one place; `orient` re-grounds you whenever you need it.
 
-Only consider a fresh conversation when:
-- **Context pressure is real** — your host signals it's compacting, or you notice earlier messages have dropped. Let that be the trigger, not a timer or a task count.
-- **You deliberately change modes** — e.g. you've just released a cycle and are sitting down to plan the next one, where a clean slate genuinely helps.
+The **only** trigger for suggesting a fresh conversation is a real context signal:
+- Your host tells you it just compacted, or you notice earlier messages have dropped.
+- You're near the context/window limit, or a verified context-usage reading is high.
 
-Do NOT restart based on elapsed time or number of tasks built. A fresh conversation costs a full re-orient — only pay it when context pressure is actually there.
+Below that, say nothing about restarting. Do NOT suggest a fresh conversation because of the task type (a design session, a strategy review, "starting the next cycle"), the number of tasks built, elapsed time, or a sense that "we've done a lot" — none of those are context signals. A fresh conversation costs a full re-orient; only pay it when context pressure is actually there.
 
 ## Advanced Patterns
 

package/skills/papi-cycle/papi-strategy/SKILL.md

@@ -10,7 +10,7 @@ description: Invoke when running strategy_review or making Active Decision chang
 Every 5 cycles, PAPI offers a strategy review — a deep analysis of velocity, estimation accuracy, active decisions, and project direction.
 
 - **Don't skip them.** They're where compounding value comes from.
-- If your session is already heavy with build context, run the review fresh for cleaner output — a genuinely fresh session needs no restart.
+- Run the review in your current conversation — a fresh one is only warranted if you're genuinely under context pressure (your host just compacted, or you're near the limit), never just because a review is next.
 - Reviews produce recommendations that feed into the next plan.
 - If the review recommends AD changes, use `strategy_change` to apply them.