@papi-ai/server 0.7.76 → 0.7.77

package/dist/backfill-cycle-metrics.js

@@ -1236,6 +1236,14 @@ var init_proxy_adapter = __esm({
       // (1) local-only
       "close",
       "initRls",
+      // task-3207 (C357): commitBuildComplete, commitReviewSubmit, commitRelease have no
+      // edge case handler and no ALLOWED_METHODS entry — forwarding them 403s at the edge
+      // with no try/catch at the call site, crashing build_execute/review_submit/release
+      // completion for every hosted user. Restores the intended graceful degradation
+      // (separate appendBuildReport + updateTaskStatus calls) until they're atomically wired.
+      "commitBuildComplete",
+      "commitReviewSubmit",
+      "commitRelease",
       // (2) not-yet-wired hosted gaps — shrink as data-proxy handlers land (task-2390).
       // getToolCallCount + updatePhaseStatus are ABSENT: they now have edge handlers and
       // are served through the forwarder (getToolCallCount = SUP-2026-026 handler #1).
@@ -2943,6 +2951,59 @@ var ACCURACY_HEADER = "| Cycle | Reports | Match Rate | MAE | Bias |";
 var ACCURACY_SEPARATOR = "|--------|---------|------------|-----|------|";
 var VELOCITY_HEADER = "| Cycle | Completed | Partial | Failed | Effort Points |";
 var VELOCITY_SEPARATOR = "|--------|-----------|---------|--------|---------------|";
+var EFFORT_SCALE = {
+  XS: 1,
+  S: 2,
+  M: 3,
+  L: 4,
+  XL: 5
+};
+function effortOrdinal(effort) {
+  const normalized = effort.trim().toUpperCase();
+  return EFFORT_SCALE[normalized];
+}
+function calculateCycleMetrics(reports, currentCycle, window = 5) {
+  const recentReports = reports.filter(
+    (r) => r.cycle > currentCycle - window && r.cycle <= currentCycle
+  );
+  const perCycle = /* @__PURE__ */ new Map();
+  for (const r of recentReports) {
+    const group = perCycle.get(r.cycle) ?? [];
+    group.push(r);
+    perCycle.set(r.cycle, group);
+  }
+  const accuracy = [];
+  const velocity = [];
+  const sortedCycles = [...perCycle.keys()].sort((a, b) => a - b);
+  for (const cycle of sortedCycles) {
+    const reps = perCycle.get(cycle);
+    const deltas = [];
+    for (const r of reps) {
+      const actual = effortOrdinal(r.actualEffort);
+      const estimated = effortOrdinal(r.estimatedEffort);
+      if (actual !== void 0 && estimated !== void 0) {
+        deltas.push(actual - estimated);
+      }
+    }
+    if (deltas.length > 0) {
+      accuracy.push({
+        cycle,
+        reports: deltas.length,
+        matchRate: Math.round(deltas.filter((d) => d === 0).length / deltas.length * 100),
+        mae: Math.round(deltas.reduce((s, d) => s + Math.abs(d), 0) / deltas.length * 10) / 10,
+        bias: Math.round(deltas.reduce((s, d) => s + d, 0) / deltas.length * 10) / 10
+      });
+    }
+    velocity.push({
+      cycle,
+      completed: reps.filter((r) => r.completed === "Yes").length,
+      partial: reps.filter((r) => r.completed === "Partial").length,
+      failed: reps.filter((r) => r.completed === "No").length,
+      effortPoints: reps.reduce((s, r) => s + (effortOrdinal(r.actualEffort) ?? 0), 0)
+    });
+  }
+  return { accuracy, velocity };
+}
 function serializeAccuracyRow(a) {
   return `| ${a.cycle} | ${a.reports} | ${a.matchRate}% | ${a.mae} | ${a.bias >= 0 ? "+" : ""}${a.bias} |`;
 }
@@ -4726,13 +4787,14 @@ function computeSnapshotsFromBuildReports(reports, tasks) {
     const cycleReports = reportsByCycle.get(sn) ?? [];
     const cycleTaskRows = tasksByCycle.get(sn);
     const withEffort = cycleReports.filter((r) => r.estimatedEffort && r.actualEffort);
-    const accurate = withEffort.filter((r) => r.estimatedEffort === r.actualEffort).length;
-    const matchRate = withEffort.length > 0 ? Math.round(accurate / withEffort.length * 100) : 0;
+    const [computedAccuracy] = calculateCycleMetrics(withEffort, sn, 1).accuracy;
     const { completed, total, plannedPoints, deliveredPoints } = computeCycleEffort(cycleTaskRows, cycleReports);
     snapshots.push({
       cycle: sn,
       date: (/* @__PURE__ */ new Date()).toISOString(),
-      accuracy: [{ cycle: sn, reports: cycleReports.length, matchRate, mae: 0, bias: 0 }],
+      // No report in this cycle carried BOTH an estimate and an actual, so there
+      // is genuinely nothing to measure. Zeros here mean "no data", not "no bias".
+      accuracy: [computedAccuracy ?? { cycle: sn, reports: 0, matchRate: 0, mae: 0, bias: 0 }],
       velocity: [{
         cycle: sn,
         completed,

package/dist/index.js

@@ -1353,6 +1353,14 @@ var init_proxy_adapter = __esm({
       // (1) local-only
       "close",
       "initRls",
+      // task-3207 (C357): commitBuildComplete, commitReviewSubmit, commitRelease have no
+      // edge case handler and no ALLOWED_METHODS entry — forwarding them 403s at the edge
+      // with no try/catch at the call site, crashing build_execute/review_submit/release
+      // completion for every hosted user. Restores the intended graceful degradation
+      // (separate appendBuildReport + updateTaskStatus calls) until they're atomically wired.
+      "commitBuildComplete",
+      "commitReviewSubmit",
+      "commitRelease",
       // (2) not-yet-wired hosted gaps — shrink as data-proxy handlers land (task-2390).
       // getToolCallCount + updatePhaseStatus are ABSENT: they now have edge handlers and
       // are served through the forwarder (getToolCallCount = SUP-2026-026 handler #1).
@@ -5259,6 +5267,15 @@ var HELP_FOOTER_MD = `
 var STRATEGY_REVIEW_OFFER_GAP = 5;
 var STRATEGY_REVIEW_BLOCK_GAP = 7;
 var ZOOM_OUT_OFFER_GAP = 25;
+function isDatabaseBackedAdapter(known) {
+  if (known) return known === "pg" || known === "proxy";
+  try {
+    const { adapterType } = loadConfig();
+    return adapterType === "pg" || adapterType === "proxy";
+  } catch {
+    return process.env.PAPI_ADAPTER !== "md";
+  }
+}
 function loadConfig() {
   const projectArgIdx = process.argv.indexOf("--project");
   const configuredRoot = projectArgIdx !== -1 ? process.argv[projectArgIdx + 1] : process.env.PAPI_PROJECT_DIR;
@@ -6324,6 +6341,48 @@ function effortOrdinal(effort) {
   const normalized = effort.trim().toUpperCase();
   return EFFORT_SCALE[normalized];
 }
+function calculateCycleMetrics(reports, currentCycle, window = 5) {
+  const recentReports = reports.filter(
+    (r) => r.cycle > currentCycle - window && r.cycle <= currentCycle
+  );
+  const perCycle = /* @__PURE__ */ new Map();
+  for (const r of recentReports) {
+    const group = perCycle.get(r.cycle) ?? [];
+    group.push(r);
+    perCycle.set(r.cycle, group);
+  }
+  const accuracy = [];
+  const velocity = [];
+  const sortedCycles = [...perCycle.keys()].sort((a, b2) => a - b2);
+  for (const cycle of sortedCycles) {
+    const reps = perCycle.get(cycle);
+    const deltas = [];
+    for (const r of reps) {
+      const actual = effortOrdinal(r.actualEffort);
+      const estimated = effortOrdinal(r.estimatedEffort);
+      if (actual !== void 0 && estimated !== void 0) {
+        deltas.push(actual - estimated);
+      }
+    }
+    if (deltas.length > 0) {
+      accuracy.push({
+        cycle,
+        reports: deltas.length,
+        matchRate: Math.round(deltas.filter((d) => d === 0).length / deltas.length * 100),
+        mae: Math.round(deltas.reduce((s, d) => s + Math.abs(d), 0) / deltas.length * 10) / 10,
+        bias: Math.round(deltas.reduce((s, d) => s + d, 0) / deltas.length * 10) / 10
+      });
+    }
+    velocity.push({
+      cycle,
+      completed: reps.filter((r) => r.completed === "Yes").length,
+      partial: reps.filter((r) => r.completed === "Partial").length,
+      failed: reps.filter((r) => r.completed === "No").length,
+      effortPoints: reps.reduce((s, r) => s + (effortOrdinal(r.actualEffort) ?? 0), 0)
+    });
+  }
+  return { accuracy, velocity };
+}
 function serializeAccuracyRow(a) {
   return `| ${a.cycle} | ${a.reports} | ${a.matchRate}% | ${a.mae} | ${a.bias >= 0 ? "+" : ""}${a.bias} |`;
 }
@@ -8402,6 +8461,16 @@ function formatBuildReports(reports, opts) {
 _\u2026and ${reports.length - capped.length} older build report(s) omitted to bound context size._` : "";
   return body + omitted;
 }
+function extractReferencedTaskIds(report) {
+  const prose = [report.surprises, report.architectureNotes, report.deadEnds, report.discoveredIssues].filter((s) => typeof s === "string" && s.length > 0).join("\n");
+  const own = report.taskId?.toLowerCase();
+  const found = /* @__PURE__ */ new Set();
+  for (const m of prose.matchAll(/\btask-\d+\b/gi)) {
+    const id = m[0].toLowerCase();
+    if (id !== own) found.add(id);
+  }
+  return [...found].sort();
+}
 function formatRecentlyShippedCapabilities(reports) {
   const completed = reports.filter((r) => r.completed === "Yes" || r.completed === "Partial");
   if (completed.length === 0) return void 0;
@@ -8416,13 +8485,39 @@ function formatRecentlyShippedCapabilities(reports) {
     }
     return parts.join("\n");
   });
-  return [
+  const namedBy = /* @__PURE__ */ new Map();
+  const completedIds = new Set(completed.map((r) => r.taskId?.toLowerCase()).filter(Boolean));
+  for (const r of completed) {
+    for (const ref of extractReferencedTaskIds(r)) {
+      if (completedIds.has(ref)) continue;
+      const namers = namedBy.get(ref) ?? [];
+      namers.push(r.taskId);
+      namedBy.set(ref, namers);
+    }
+  }
+  const out = [
     `${completed.length} task(s) completed in recent cycles:`,
     "",
     ...lines,
     "",
     "Cross-reference candidate tasks against this list. If >80% of a candidate task's scope appears here, recommend cancellation or scope reduction instead of scheduling."
-  ].join("\n");
+  ];
+  if (namedBy.size > 0) {
+    out.push(
+      "",
+      "### \u26A0 Named by a shipped task \u2014 VERIFY BEFORE SCHEDULING",
+      "",
+      "These task IDs are referenced in the build reports above but are NOT themselves",
+      "completed. A discovery is often fixed as a side effect of a sibling task's diff and",
+      "never marked done, so it survives into this plan carrying notes that are no longer",
+      "true (C357 gave task-3043 a P1 slot this way \u2014 task-2998 had already fixed it).",
+      "For each one below: check the naming report and the live code BEFORE scheduling it.",
+      "If it is already fixed, close it with a boardCorrection instead of spending a slot.",
+      "",
+      ...[...namedBy.entries()].sort(([a], [b2]) => a.localeCompare(b2)).map(([ref, namers]) => `- **${ref}** \u2014 named by ${namers.join(", ")}`)
+    );
+  }
+  return out.join("\n");
 }
 function formatCycleLog(entries) {
   if (entries.length === 0) return "No cycle log entries yet.";
@@ -8669,13 +8764,14 @@ function computeSnapshotsFromBuildReports(reports, tasks) {
     const cycleReports = reportsByCycle.get(sn) ?? [];
     const cycleTaskRows = tasksByCycle.get(sn);
     const withEffort = cycleReports.filter((r) => r.estimatedEffort && r.actualEffort);
-    const accurate = withEffort.filter((r) => r.estimatedEffort === r.actualEffort).length;
-    const matchRate = withEffort.length > 0 ? Math.round(accurate / withEffort.length * 100) : 0;
+    const [computedAccuracy] = calculateCycleMetrics(withEffort, sn, 1).accuracy;
     const { completed, total, plannedPoints, deliveredPoints } = computeCycleEffort(cycleTaskRows, cycleReports);
     snapshots.push({
       cycle: sn,
       date: (/* @__PURE__ */ new Date()).toISOString(),
-      accuracy: [{ cycle: sn, reports: cycleReports.length, matchRate, mae: 0, bias: 0 }],
+      // No report in this cycle carried BOTH an estimate and an actual, so there
+      // is genuinely nothing to measure. Zeros here mean "no data", not "no bias".
+      accuracy: [computedAccuracy ?? { cycle: sn, reports: 0, matchRate: 0, mae: 0, bias: 0 }],
       velocity: [{
         cycle: sn,
         completed,
@@ -9196,7 +9292,7 @@ var PLAN_FRAGMENT_RESEARCH = `
 var PLAN_FRAGMENT_BUG = `
    **Bug task detection:** When a task's task type is "bug" or the title starts with "Bug:" or "Fix:", apply these rules:
    - **Auto-P1:** If the task's current priority is P2 or lower, upgrade it to "P1 High" via a boardCorrections entry in Part 2. Note the upgrade in Part 1 analysis.
-   - Replace the standard SCOPE (DO THIS) section with bug-specific sections:
+   - Inside SCOPE (DO THIS), use these bug-specific subsections. KEEP the "SCOPE (DO THIS)" header and put these subsections INSIDE it \u2014 the handoff parser only recognises the standard headers (packages/adapter-md build-handoff.ts SECTION_HEADERS) and a handoff with no SCOPE section is rejected outright (task-3050, C357):
      - **REPRODUCE:** Exact steps to reproduce the bug before touching any code. If the task notes describe the symptoms, include them. If not, the first build step is "confirm the bug reproduces."
      - **ROOT CAUSE:** One-sentence hypothesis for the root cause (what is wrong, not what the user sees). The builder must confirm or correct this before implementing a fix.
      - **MINIMAL FIX:** The smallest code change that resolves the root cause. "Bug fix \u2014 minimal blast radius. Change only what is necessary. Do not refactor surrounding code or expand scope."
@@ -9221,7 +9317,7 @@ var PLAN_FRAGMENT_SPIKE = `
    - Keep SCOPE BOUNDARY, SECURITY CONSIDERATIONS, and PRE-BUILD VERIFICATION as normal.
    - Spikes should be estimated conservatively: XS or S. If a spike needs M+ effort, it's not a spike \u2014 reclassify as a research task.`;
 var PLAN_FRAGMENT_DESIGN_BRIEF = `
-   **Design brief task detection:** When a task's task type is "design-brief", generate a DESIGN BRIEF handoff. Replace the standard SCOPE (DO THIS) section with these type-specific sections:
+   **Design brief task detection:** When a task's task type is "design-brief", generate a DESIGN BRIEF handoff. Inside SCOPE (DO THIS), use these type-specific subsections. KEEP the "SCOPE (DO THIS)" header and put these subsections INSIDE it \u2014 the handoff parser only recognises the standard headers (packages/adapter-md build-handoff.ts SECTION_HEADERS) and a handoff with no SCOPE section is rejected outright (task-3050, C357):
    - AUDIENCE: Who this design is for \u2014 persona and context of use (e.g. "non-technical Owner, first dashboard visit")
    - BRAND CONSTRAINTS: Palette, typography, tone \u2014 pull from \`.impeccable.md\` (dev patterns, anti-patterns, component rules) AND \`docs/branding/brand-book.html\` (brand identity, positioning, voice canon) if present. If neither exists, state "No brand doc \u2014 Owner should define constraints before starting."
    - DELIVERABLE FORMAT: What the output looks like \u2014 design handoff package / annotated mockup / style spec. Be specific so the person doing the work knows what "done" means.
@@ -9229,7 +9325,7 @@ var PLAN_FRAGMENT_DESIGN_BRIEF = `
    Keep SCOPE BOUNDARY, ACCEPTANCE CRITERIA, SECURITY CONSIDERATIONS, and PRE-BUILD VERIFICATION sections as normal.
    Add to ACCEPTANCE CRITERIA: "[ ] Deliverable format confirmed with Owner before starting" and "[ ] Design output is self-contained \u2014 includes enough context for a developer to implement without further clarification."`;
 var PLAN_FRAGMENT_RESEARCH_BRIEF = `
-   **Research brief task detection:** When a task's task type is "research-brief", generate a RESEARCH BRIEF handoff. Replace the standard SCOPE (DO THIS) section with:
+   **Research brief task detection:** When a task's task type is "research-brief", generate a RESEARCH BRIEF handoff. Inside SCOPE (DO THIS), use these subsections. KEEP the "SCOPE (DO THIS)" header and put these subsections INSIDE it \u2014 the handoff parser only recognises the standard headers (packages/adapter-md build-handoff.ts SECTION_HEADERS) and a handoff with no SCOPE section is rejected outright (task-3050, C357):
    - GOAL: The specific question this research answers \u2014 one sentence, phrased as a question (e.g. "What onboarding patterns do our top 3 competitors use?")
    - TIME-BOX: Maximum effort allowed \u2014 XS or S. Stop when the time-box is hit and report what was found, even if incomplete.
    - OUTPUT: Where findings land \u2014 a doc at \`docs/research/[topic]-findings.md\` or inline in the build report. State the path.
@@ -9237,7 +9333,7 @@ var PLAN_FRAGMENT_RESEARCH_BRIEF = `
    Keep SCOPE BOUNDARY, ACCEPTANCE CRITERIA, SECURITY CONSIDERATIONS, and PRE-BUILD VERIFICATION as normal.
    Add to ACCEPTANCE CRITERIA: "[ ] Question answered OR time-box hit \u2014 whichever comes first" and "[ ] Findings doc saved before any follow-up tasks are submitted."`;
 var PLAN_FRAGMENT_MARKETING_BRIEF = `
-   **Marketing brief task detection:** When a task's task type is "marketing-brief", generate a MARKETING BRIEF handoff. Replace the standard SCOPE (DO THIS) section with:
+   **Marketing brief task detection:** When a task's task type is "marketing-brief", generate a MARKETING BRIEF handoff. Inside SCOPE (DO THIS), use these subsections. KEEP the "SCOPE (DO THIS)" header and put these subsections INSIDE it \u2014 the handoff parser only recognises the standard headers (packages/adapter-md build-handoff.ts SECTION_HEADERS) and a handoff with no SCOPE section is rejected outright (task-3050, C357):
    - AUDIENCE: Who this marketing content targets \u2014 persona, awareness level, channel context (e.g. "cold Discord visitor, zero PAPI context")
    - CHANNEL: Where this content lives \u2014 Discord, landing page, email, social, etc.
    - MESSAGE FRAME: The core message to land \u2014 one sentence. What does the reader need to believe after seeing this? (e.g. "PAPI makes AI-assisted building systematic, not chaotic.")
@@ -9245,7 +9341,7 @@ var PLAN_FRAGMENT_MARKETING_BRIEF = `
    Keep SCOPE BOUNDARY, ACCEPTANCE CRITERIA, SECURITY CONSIDERATIONS, and PRE-BUILD VERIFICATION as normal.
    Add to ACCEPTANCE CRITERIA: "[ ] Message Frame confirmed with Owner before drafting" and "[ ] Final content reviewed by Owner before publishing."`;
 var PLAN_FRAGMENT_OPS_BRIEF = `
-   **Ops brief task detection:** When a task's task type is "ops-brief", generate an OPS BRIEF handoff. Replace the standard SCOPE (DO THIS) section with:
+   **Ops brief task detection:** When a task's task type is "ops-brief", generate an OPS BRIEF handoff. Inside SCOPE (DO THIS), use these subsections. KEEP the "SCOPE (DO THIS)" header and put these subsections INSIDE it \u2014 the handoff parser only recognises the standard headers (packages/adapter-md build-handoff.ts SECTION_HEADERS) and a handoff with no SCOPE section is rejected outright (task-3050, C357):
    - SYSTEM: Which system or service this ops task touches \u2014 Vercel, Railway, Supabase, GitHub Actions, DNS, etc.
    - RISK: What could go wrong \u2014 data loss, downtime, broken deployments. Include estimated blast radius (e.g. "affects all authenticated users").
    - ROLLBACK PLAN: Exact steps to undo the change if something breaks. Must be specific enough to execute under pressure.
@@ -10888,8 +10984,9 @@ async function applyHandoffs(adapter2, rawLlmOutput, cycleNumber, force = false)
       }
       const invalidFields = validateHandoffScope(parsed);
       if (invalidFields.length > 0) {
+        const scopeMissing = invalidFields.includes("scope");
         warnings.push(
-          `Rejected handoff for ${handoff.taskId}: missing or empty ${invalidFields.join(", ")}. Handoffs without explicit scope produce ambiguous builds.`
+          `Rejected handoff for ${handoff.taskId}: missing or empty ${invalidFields.join(", ")}. Handoffs without explicit scope produce ambiguous builds.` + (scopeMissing ? ` If this is a bug/design-brief/research-brief/marketing-brief/ops-brief task, KEEP the "SCOPE (DO THIS)" header and nest the type-specific sections (REPRODUCE / ROOT CAUSE / MINIMAL FIX / \u2026) inside it \u2014 the parser only recognises the standard headers, so replacing SCOPE outright drops it entirely.` : "")
         );
         continue;
       }
@@ -12894,7 +12991,7 @@ async function assertSingleActiveCycle(adapter2, opts = {}) {
   }
   return notes;
 }
-async function validateAndPrepare(adapter2, force, callerUserId) {
+async function validateAndPrepare(adapter2, force, callerUserId, adapterType) {
   let mode;
   let cycleNumber;
   let strategyReviewWarning = "";
@@ -12956,7 +13053,7 @@ Run \`strategy_review\` first, or pass \`force: true\` to bypass this gate.`
     if (err instanceof Error && (err.message.startsWith("Strategy Review") || err.message.startsWith("Cycle ") || err.message.startsWith("Stale reviews"))) {
       throw err;
     }
-    const isPg = process.env.PAPI_ADAPTER === "pg" || process.env.PAPI_ADAPTER === "proxy";
+    const isPg = isDatabaseBackedAdapter(adapterType);
     throw new Error(
       isPg ? "Could not read cycle health from the database. Check your DATABASE_URL and verify the project exists." : "Could not read cycle health from PLANNING_LOG.md. Run setup first to initialise your PAPI project."
     );
@@ -13074,7 +13171,7 @@ async function preparePlan(adapter2, config2, filters, focus, force, handoffsOnl
   tracker?.mark("validate_and_prepare");
   let t = startTimer();
   const prepareScope = await resolvePlanScope(adapter2, config2);
-  const { mode, cycleNumber, strategyReviewWarning } = await validateAndPrepare(adapter2, force, prepareScope.callerUserId);
+  const { mode, cycleNumber, strategyReviewWarning } = await validateAndPrepare(adapter2, force, prepareScope.callerUserId, config2.adapterType);
   const validateMs = t();
   const incomingCycle = cycleNumber + 1;
   tracker?.setStreamScope({ cycle: incomingCycle });
@@ -16007,7 +16104,7 @@ async function prepareStrategyReview(adapter2, force, projectRoot, adapterType,
       };
     }
   } catch {
-    const isPg = process.env.PAPI_ADAPTER === "pg" || process.env.PAPI_ADAPTER === "proxy";
+    const isPg = isDatabaseBackedAdapter(adapterType);
     throw new Error(
       isPg ? "Could not read cycle health from the database. Check your DATABASE_URL and verify the project exists." : "Could not read cycle health from PLANNING_LOG.md. Run setup first to initialise your PAPI project."
     );
@@ -16451,13 +16548,13 @@ ${cleanContent}`;
 ${evidenceWarnings.map((w) => `- ${w}`).join("\n")}` : displayText;
   return { cycleNumber, displayText: fullText, writeBackFailed };
 }
-async function prepareStrategyChange(adapter2, text) {
+async function prepareStrategyChange(adapter2, text, adapterType) {
   let cycleNumber;
   try {
     const health = await adapter2.getCycleHealth();
     cycleNumber = health.totalCycles;
   } catch {
-    const isPg = process.env.PAPI_ADAPTER === "pg" || process.env.PAPI_ADAPTER === "proxy";
+    const isPg = isDatabaseBackedAdapter(adapterType);
     throw new Error(
       isPg ? "Could not read cycle health from the database. Check your DATABASE_URL and verify the project exists." : "Could not read cycle health from PLANNING_LOG.md. Run setup first to initialise your PAPI project."
     );
@@ -16976,7 +17073,7 @@ Decision event logged.`
       return errorResponse("text is required for strategy_change. Describe the strategic shift to apply.");
     }
     {
-      const result = await prepareStrategyChange(adapter2, text);
+      const result = await prepareStrategyChange(adapter2, text, _config.adapterType);
       return textResponse(
         `## PAPI Strategy Change \u2014 Prepare Phase (Cycle ${result.cycleNumber})
 

package/dist/prompts.js

@@ -216,7 +216,7 @@ var PLAN_FRAGMENT_RESEARCH = `
 var PLAN_FRAGMENT_BUG = `
    **Bug task detection:** When a task's task type is "bug" or the title starts with "Bug:" or "Fix:", apply these rules:
    - **Auto-P1:** If the task's current priority is P2 or lower, upgrade it to "P1 High" via a boardCorrections entry in Part 2. Note the upgrade in Part 1 analysis.
-   - Replace the standard SCOPE (DO THIS) section with bug-specific sections:
+   - Inside SCOPE (DO THIS), use these bug-specific subsections. KEEP the "SCOPE (DO THIS)" header and put these subsections INSIDE it \u2014 the handoff parser only recognises the standard headers (packages/adapter-md build-handoff.ts SECTION_HEADERS) and a handoff with no SCOPE section is rejected outright (task-3050, C357):
      - **REPRODUCE:** Exact steps to reproduce the bug before touching any code. If the task notes describe the symptoms, include them. If not, the first build step is "confirm the bug reproduces."
      - **ROOT CAUSE:** One-sentence hypothesis for the root cause (what is wrong, not what the user sees). The builder must confirm or correct this before implementing a fix.
      - **MINIMAL FIX:** The smallest code change that resolves the root cause. "Bug fix \u2014 minimal blast radius. Change only what is necessary. Do not refactor surrounding code or expand scope."
@@ -241,7 +241,7 @@ var PLAN_FRAGMENT_SPIKE = `
    - Keep SCOPE BOUNDARY, SECURITY CONSIDERATIONS, and PRE-BUILD VERIFICATION as normal.
    - Spikes should be estimated conservatively: XS or S. If a spike needs M+ effort, it's not a spike \u2014 reclassify as a research task.`;
 var PLAN_FRAGMENT_DESIGN_BRIEF = `
-   **Design brief task detection:** When a task's task type is "design-brief", generate a DESIGN BRIEF handoff. Replace the standard SCOPE (DO THIS) section with these type-specific sections:
+   **Design brief task detection:** When a task's task type is "design-brief", generate a DESIGN BRIEF handoff. Inside SCOPE (DO THIS), use these type-specific subsections. KEEP the "SCOPE (DO THIS)" header and put these subsections INSIDE it \u2014 the handoff parser only recognises the standard headers (packages/adapter-md build-handoff.ts SECTION_HEADERS) and a handoff with no SCOPE section is rejected outright (task-3050, C357):
    - AUDIENCE: Who this design is for \u2014 persona and context of use (e.g. "non-technical Owner, first dashboard visit")
    - BRAND CONSTRAINTS: Palette, typography, tone \u2014 pull from \`.impeccable.md\` (dev patterns, anti-patterns, component rules) AND \`docs/branding/brand-book.html\` (brand identity, positioning, voice canon) if present. If neither exists, state "No brand doc \u2014 Owner should define constraints before starting."
    - DELIVERABLE FORMAT: What the output looks like \u2014 design handoff package / annotated mockup / style spec. Be specific so the person doing the work knows what "done" means.
@@ -249,7 +249,7 @@ var PLAN_FRAGMENT_DESIGN_BRIEF = `
    Keep SCOPE BOUNDARY, ACCEPTANCE CRITERIA, SECURITY CONSIDERATIONS, and PRE-BUILD VERIFICATION sections as normal.
    Add to ACCEPTANCE CRITERIA: "[ ] Deliverable format confirmed with Owner before starting" and "[ ] Design output is self-contained \u2014 includes enough context for a developer to implement without further clarification."`;
 var PLAN_FRAGMENT_RESEARCH_BRIEF = `
-   **Research brief task detection:** When a task's task type is "research-brief", generate a RESEARCH BRIEF handoff. Replace the standard SCOPE (DO THIS) section with:
+   **Research brief task detection:** When a task's task type is "research-brief", generate a RESEARCH BRIEF handoff. Inside SCOPE (DO THIS), use these subsections. KEEP the "SCOPE (DO THIS)" header and put these subsections INSIDE it \u2014 the handoff parser only recognises the standard headers (packages/adapter-md build-handoff.ts SECTION_HEADERS) and a handoff with no SCOPE section is rejected outright (task-3050, C357):
    - GOAL: The specific question this research answers \u2014 one sentence, phrased as a question (e.g. "What onboarding patterns do our top 3 competitors use?")
    - TIME-BOX: Maximum effort allowed \u2014 XS or S. Stop when the time-box is hit and report what was found, even if incomplete.
    - OUTPUT: Where findings land \u2014 a doc at \`docs/research/[topic]-findings.md\` or inline in the build report. State the path.
@@ -257,7 +257,7 @@ var PLAN_FRAGMENT_RESEARCH_BRIEF = `
    Keep SCOPE BOUNDARY, ACCEPTANCE CRITERIA, SECURITY CONSIDERATIONS, and PRE-BUILD VERIFICATION as normal.
    Add to ACCEPTANCE CRITERIA: "[ ] Question answered OR time-box hit \u2014 whichever comes first" and "[ ] Findings doc saved before any follow-up tasks are submitted."`;
 var PLAN_FRAGMENT_MARKETING_BRIEF = `
-   **Marketing brief task detection:** When a task's task type is "marketing-brief", generate a MARKETING BRIEF handoff. Replace the standard SCOPE (DO THIS) section with:
+   **Marketing brief task detection:** When a task's task type is "marketing-brief", generate a MARKETING BRIEF handoff. Inside SCOPE (DO THIS), use these subsections. KEEP the "SCOPE (DO THIS)" header and put these subsections INSIDE it \u2014 the handoff parser only recognises the standard headers (packages/adapter-md build-handoff.ts SECTION_HEADERS) and a handoff with no SCOPE section is rejected outright (task-3050, C357):
    - AUDIENCE: Who this marketing content targets \u2014 persona, awareness level, channel context (e.g. "cold Discord visitor, zero PAPI context")
    - CHANNEL: Where this content lives \u2014 Discord, landing page, email, social, etc.
    - MESSAGE FRAME: The core message to land \u2014 one sentence. What does the reader need to believe after seeing this? (e.g. "PAPI makes AI-assisted building systematic, not chaotic.")
@@ -265,7 +265,7 @@ var PLAN_FRAGMENT_MARKETING_BRIEF = `
    Keep SCOPE BOUNDARY, ACCEPTANCE CRITERIA, SECURITY CONSIDERATIONS, and PRE-BUILD VERIFICATION as normal.
    Add to ACCEPTANCE CRITERIA: "[ ] Message Frame confirmed with Owner before drafting" and "[ ] Final content reviewed by Owner before publishing."`;
 var PLAN_FRAGMENT_OPS_BRIEF = `
-   **Ops brief task detection:** When a task's task type is "ops-brief", generate an OPS BRIEF handoff. Replace the standard SCOPE (DO THIS) section with:
+   **Ops brief task detection:** When a task's task type is "ops-brief", generate an OPS BRIEF handoff. Inside SCOPE (DO THIS), use these subsections. KEEP the "SCOPE (DO THIS)" header and put these subsections INSIDE it \u2014 the handoff parser only recognises the standard headers (packages/adapter-md build-handoff.ts SECTION_HEADERS) and a handoff with no SCOPE section is rejected outright (task-3050, C357):
    - SYSTEM: Which system or service this ops task touches \u2014 Vercel, Railway, Supabase, GitHub Actions, DNS, etc.
    - RISK: What could go wrong \u2014 data loss, downtime, broken deployments. Include estimated blast radius (e.g. "affects all authenticated users").
    - ROLLBACK PLAN: Exact steps to undo the change if something breaks. Must be specific enough to execute under pressure.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@papi-ai/server",
-  "version": "0.7.76",
+  "version": "0.7.77",
   "description": "PAPI MCP server — AI-powered sprint planning, build execution, and strategy review for software projects",
   "license": "Elastic-2.0",
   "mcpName": "io.github.getpapi/papi",