@papi-ai/server 0.7.40 → 0.7.42

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@papi-ai/server",
-  "version": "0.7.40",
+  "version": "0.7.42",
   "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",
@@ -16,11 +16,12 @@
   "files": [
     "dist",
     "skills",
+    "design-assets",
     "README.md"
   ],
   "scripts": {
     "build": "npm run build:skills && tsup",
-    "build:skills": "PAPI_SKILLS_OUT=skills/papi-cycle node scripts/export-skills.mjs",
+    "build:skills": "node scripts/export-skills.mjs --out skills/papi-cycle",
     "build:prompts": "tsup src/prompts.ts --format esm",
     "start": "node dist/index.js",
     "backfill-cycle-metrics": "node dist/backfill-cycle-metrics.js",

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

@@ -7,18 +7,13 @@ description: Invoke for cross-project patterns, dogfood-derived workflows, or ad
 
 ## When to Start a New Conversation
 
-Start a fresh window when:
-- **After a release** — cycle is done, context is heavy. New window orients in seconds via `orient`.
-- **After 3+ tasks built** — accumulated file reads, diffs, and discussions bloat context. Quality degrades.
-- **Switching modes** — going from building to planning, or from strategy review to building. Each mode benefits from clean context.
-- **After context compression fires** — if you notice earlier messages are missing, the window is getting stale. Open fresh.
+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.
 
-Stay in the same window when:
-- Building sequential tasks in a batch (especially XS/S tasks)
-- Mid-task and not yet complete
-- Having a strategic discussion that informs the next action
+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.
 
-**Rule of thumb:** If you've been in the same window for 30+ minutes or 3+ tasks, it's time for a fresh one.
+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.
 
 ## Advanced Patterns