@papi-ai/server 0.7.41 → 0.7.43

package/design-assets/agents/frontend-design-engineer.md

@@ -82,7 +82,12 @@ Your output is **not done** if ANY of these is true (these are falsifiable — c
 - [ ] Gradient text or gradient fill used decoratively (the generic-AI look).
 - [ ] Your brand accent used as a glow / dark-mode-only sheen instead of solid, intentional colour.
 - [ ] An "earned" signal colour (insight/intelligence/premium) used as a plain decorative fill.
-- [ ] No single dominant above-the-fold hero, or two elements competing for dominance.
+- [ ] Two elements competing for dominance (both fight for the eye). NOTE: a page with NO hero is
+      fine when nothing must lead — do not manufacture one to satisfy this line; only *competing*
+      dominance fails (see The core principle).
+- [ ] Guidance, state, or a next action explained in a sentence of helper text where a visual cue
+      (position, size, colour, icon, a signpost, motion-on-change) would carry it — prose used as a
+      crutch for missing visual steering.
 - [ ] More than ~3 sections fully visible above the fold.
 - [ ] Identical-sized cards in a uniform row (flat hierarchy — needs a dominant 2×+ cell).
 - [ ] Monospace on labels, status, timestamps, or nav.
@@ -121,6 +126,16 @@ Return a tight report (this is data, not prose):
 
 ## The core principle
 
-**Composition > decoration.** A page with perfect tokens and flat hierarchy is worse than one with
-slightly-off tokens and a clear hero, reading order, and earned elements. One hero, clear reading
-order, everything earns its space.
+**Composition > decoration, and show > tell.** A page with perfect tokens and flat hierarchy is
+worse than one with slightly-off tokens and a clear reading order where every element earns its
+space. Two rules generalist agents keep getting wrong:
+
+- **Steer with visuals, not text.** When the user needs guidance — what to do, where to look, what
+  state something is in — reach for a VISUAL cue first: position, size, colour, an icon, a
+  connecting line, a spatial signpost, motion on change. A sentence of helper text is the last
+  resort, not the first. Over-explaining in prose is the default AI failure mode; a well-placed
+  arrow, a pulse, or a bolded number beats a paragraph. Visual steering and motion beat words.
+- **A hero is conditional, not mandatory.** Give the page one dominant focal point WHEN it has a
+  single thing that must lead. Dense tool, list, board, and settings surfaces can carry a calm, even
+  hierarchy — do not manufacture a hero, an oversized stat, or a promoted banner where the content
+  has no natural lead. Only *competing* dominance is always wrong; the absence of a hero is not.

package/design-assets/skills/design-critique/SKILL.md

@@ -48,15 +48,17 @@ Plus a one-line page read: `kind / audience / the one thing they must see first`
 3. **Read the target page in full** — not just the component you're editing. You need full page
    context to judge compositional hierarchy.
 4. **List all sibling components** on the page. You'll weigh each one's visual weight against the others.
-5. **Check both states:** populated and empty/zero-data. Both need a hero and hierarchy.
+5. **Check both states:** populated and empty/zero-data. Both need clear hierarchy (a hero only where one is warranted — see Check 1).
 
 ## Step 2: The Seven Checks
 
 For each, give ✅ Pass / ⚠️ Weak / ❌ Fail plus a one-line reason.
 
-### Check 1: Hero Element
-> Every page has exactly ONE dominant visual element above the fold.
-Name it. If you can't, or two things compete, it's ❌. Squint test: blurred, only the hero shows.
+### Check 1: Hero Element (conditional — NOT every page needs one)
+> Give the page one dominant element WHEN it has one thing that must lead. A hero is not mandatory.
+Does this page have a single thing that must lead? If yes: name it; missing/weak = ⚠️/❌. If no (a
+dense tool / list / board / settings surface): a calm, even hierarchy is ✅ — do NOT manufacture a
+hero to pass this check. Two elements *competing* for dominance is ALWAYS ❌ (the real failure).
 
 ### Check 2: Reading Order
 > hero → primary action → supporting content → tertiary.
@@ -101,7 +103,11 @@ Run through every named anti-pattern and flag matches. Common universal ones:
 - Gradient text or gradient fill used decoratively.
 - Brand accent as a glow / dark-only sheen instead of solid intentional colour.
 - A "signal" colour used as a plain decorative fill.
-- No single dominant above-fold hero, or two competing for it.
+- Two elements competing for dominance (both fight for the eye). NOT a fail: a page with no hero
+  when nothing must lead (see Check 1) — only *competing* dominance fails here.
+- Guidance, state, or a next action carried by a sentence of helper text where a visual cue
+  (position, size, colour, an icon, a signpost, motion-on-change) would do — prose as a crutch for
+  missing visual steering. Prefer showing over telling.
 - Identical-sized cards in a uniform row (flat hierarchy).
 - Monospace on labels / status / timestamps / nav.
 - Header, label, and value at the same size+weight.
@@ -158,5 +164,10 @@ The pre-build critique catches composition; this catches what's only visible in
 
 ## The Core Principle
 
-**Composition > Decoration.** A page with perfect tokens and flat hierarchy is worse than one with
-slightly-off tokens and clear hierarchy. One hero, clear reading order, everything earns its space.
+**Composition > Decoration, and show > tell.** A page with perfect tokens and flat hierarchy is
+worse than one with slightly-off tokens and clear hierarchy. Two things generalist agents keep
+getting wrong: (1) **steer with visuals, not text** — reach for position, size, colour, an icon, a
+signpost, or motion-on-change before a sentence of helper text; over-explaining in prose is the
+default AI failure mode. (2) **A hero is conditional** — give a page one dominant element only when
+it has one thing that must lead; dense list / tool / settings surfaces carry a calm, even hierarchy,
+so do not manufacture a hero. Clear reading order, everything earns its space, show before you tell.

package/dist/backfill-cycle-metrics.js

@@ -73,7 +73,7 @@ __export(git_exports, {
   taskBranchName: () => taskBranchName,
   withBaseBranchSync: () => withBaseBranchSync
 });
-import { execFileSync } from "child_process";
+import { execFileSync, spawnSync } from "child_process";
 function isGitAvailable() {
   try {
     execFileSync("git", ["--version"], { stdio: "ignore" });
@@ -317,21 +317,24 @@ function gitPull(cwd) {
   }
 }
 function gitPush(cwd, branch) {
-  try {
-    execFileSync("git", ["push", "-u", "origin", branch], {
-      cwd,
-      encoding: "utf-8",
-      timeout: GIT_NETWORK_TIMEOUT_MS
-    });
-    return { success: true, message: `Pushed branch '${branch}' to origin.` };
-  } catch (err) {
-    const msg = err instanceof Error ? err.message : String(err);
-    const isTimeout = msg.includes("ETIMEDOUT") || msg.includes("killed");
-    return {
-      success: false,
-      message: isTimeout ? `Push timed out after 30s.` : `Push failed: ${msg}`
-    };
+  const result = spawnSync("git", ["push", "-u", "origin", branch], {
+    cwd,
+    encoding: "utf-8",
+    timeout: GIT_NETWORK_TIMEOUT_MS
+  });
+  if (result.error) {
+    const msg = result.error.message;
+    const isTimeout = msg.includes("ETIMEDOUT") || result.signal === "SIGTERM" || msg.includes("killed");
+    return { success: false, pushed: false, message: isTimeout ? "Push timed out after 30s." : `Push failed: ${msg}` };
   }
+  const output = `${result.stdout ?? ""}${result.stderr ?? ""}`.trim();
+  if (result.status !== 0) {
+    return { success: false, pushed: false, message: `Push failed: ${output || `git exited ${result.status}`}` };
+  }
+  if (/Everything up-to-date/i.test(output)) {
+    return { success: true, pushed: false, message: `'${branch}' already up to date on origin \u2014 nothing to push.` };
+  }
+  return { success: true, pushed: true, message: `Pushed '${branch}' to origin.` };
 }
 function isGhAvailable() {
   try {
@@ -1012,6 +1015,48 @@ var init_git = __esm({
   }
 });
 
+// src/lib/install-id.ts
+import { randomUUID as randomUUID7 } from "crypto";
+import { mkdirSync, readFileSync, writeFileSync, chmodSync } from "fs";
+import { homedir } from "os";
+import { join as join2 } from "path";
+var PAPI_HOME_DIR, INSTALL_ID_FILE;
+var init_install_id = __esm({
+  "src/lib/install-id.ts"() {
+    "use strict";
+    PAPI_HOME_DIR = join2(homedir(), ".papi");
+    INSTALL_ID_FILE = join2(PAPI_HOME_DIR, "install-id.json");
+  }
+});
+
+// src/lib/telemetry.ts
+function reportTelemetryEmitFailure(reason, ctx) {
+  consecutiveTelemetryFailures += 1;
+  console.error(
+    `[telemetry] emit failed (${reason}) tool=${ctx.toolName} event=${ctx.eventType} project=${ctx.projectId}`
+  );
+  if (consecutiveTelemetryFailures >= TELEMETRY_BLACKOUT_THRESHOLD) {
+    console.error(
+      `[telemetry] BLACKOUT: ${consecutiveTelemetryFailures} consecutive telemetry emit failures \u2014 activation metrics are under-counting for this pod. Check the data-proxy /telemetry path (auth/RLS/network/schema).`
+    );
+  }
+}
+function noteTelemetryEmitSuccess() {
+  consecutiveTelemetryFailures = 0;
+}
+var HOSTED_SUPABASE_URL, DEFAULT_TELEMETRY_ENDPOINT, MD_PINGS_SUPABASE_URL, consecutiveTelemetryFailures, TELEMETRY_BLACKOUT_THRESHOLD;
+var init_telemetry = __esm({
+  "src/lib/telemetry.ts"() {
+    "use strict";
+    init_install_id();
+    HOSTED_SUPABASE_URL = process.env["PAPI_HOSTED_SUPABASE_URL"] ?? "https://guewgygcpcmrcoppihzx.supabase.co";
+    DEFAULT_TELEMETRY_ENDPOINT = `${HOSTED_SUPABASE_URL}/functions/v1/data-proxy`;
+    MD_PINGS_SUPABASE_URL = process.env["PAPI_MD_PINGS_URL"] ?? HOSTED_SUPABASE_URL;
+    consecutiveTelemetryFailures = 0;
+    TELEMETRY_BLACKOUT_THRESHOLD = 3;
+  }
+});
+
 // src/proxy-adapter.ts
 var proxy_adapter_exports = {};
 __export(proxy_adapter_exports, {
@@ -1058,6 +1103,7 @@ var JSONB_PASSTHROUGH_KEYS, DISPLAY_ID_METHODS, ProxyPapiAdapter;
 var init_proxy_adapter = __esm({
   "src/proxy-adapter.ts"() {
     "use strict";
+    init_telemetry();
     JSONB_PASSTHROUGH_KEYS = /* @__PURE__ */ new Set([
       "buildHandoff",
       "stateHistory",
@@ -1420,6 +1466,7 @@ Check PAPI_PROJECT_ID in your .mcp.json config. Find your project ID in the PAPI
        * telemetry failure must never surface as a tool error.
        */
       emitTelemetry(event) {
+        const ctx = { projectId: event.projectId, toolName: event.toolName, eventType: event.eventType };
         fetch(`${this.endpoint}/telemetry`, {
           method: "POST",
           headers: {
@@ -1433,7 +1480,11 @@ Check PAPI_PROJECT_ID in your .mcp.json config. Find your project ID in the PAPI
             metadata: event.metadata ?? {}
           }),
           signal: AbortSignal.timeout(5e3)
-        }).catch(() => {
+        }).then((res) => {
+          if (res.ok) noteTelemetryEmitSuccess();
+          else reportTelemetryEmitFailure(`HTTP ${res.status}`, ctx);
+        }).catch((err) => {
+          reportTelemetryEmitFailure(err instanceof Error ? err.name : "network error", ctx);
         });
       }
       readToolMetrics() {
@@ -1525,6 +1576,19 @@ Check PAPI_PROJECT_ID in your .mcp.json config. Find your project ID in the PAPI
       getStrategyReviews(limit, includeFullAnalysis) {
         return this.invoke("getStrategyReviews", [limit, includeFullAnalysis]);
       }
+      // --- Strategy Review Agenda (SUP-2026-026 — hosted parity) ---
+      // Present on the pg/md adapters since C302 but never forwarded here, so
+      // `strategy_agenda` failed for every hosted user. The proxy-parity guard missed
+      // it because it only checked forwarded⊆allowed, never pg⊆forwarded (now fixed).
+      addAgendaTopic(input) {
+        return this.invoke("addAgendaTopic", [input]);
+      }
+      getPendingAgendaTopics() {
+        return this.invoke("getPendingAgendaTopics");
+      }
+      markAgendaTopicsAddressed(ids, cycleNumber) {
+        return this.invoke("markAgendaTopicsAddressed", [ids, cycleNumber]);
+      }
       // --- Dogfood ---
       writeDogfoodEntries(entries) {
         return this.invoke("writeDogfoodEntries", [entries]);
@@ -1763,12 +1827,12 @@ import { pathToFileURL } from "url";
 import path2 from "path";
 import { execSync } from "child_process";
 
-// ../adapter-md/dist/index.js
+// ../../../../../packages/adapter-md/dist/index.js
 import { readFile, writeFile, access } from "fs/promises";
 import { randomUUID as randomUUID6 } from "crypto";
 import { join } from "path";
 
-// ../shared/dist/index.js
+// ../../../../../packages/shared/dist/index.js
 var VALID_TRANSITIONS = {
   "Backlog": ["In Cycle", "Ready", "In Progress", "Blocked", "Cancelled", "Deferred", "Done"],
   "In Cycle": ["In Progress", "Backlog", "Blocked", "Cancelled"],
@@ -1787,7 +1851,7 @@ function isLiveDecision(d) {
   return true;
 }
 
-// ../adapter-md/dist/index.js
+// ../../../../../packages/adapter-md/dist/index.js
 import { randomUUID } from "crypto";
 import { randomUUID as randomUUID3 } from "crypto";
 import yaml from "js-yaml";
@@ -4064,8 +4128,8 @@ function detectUserId() {
   }
   return void 0;
 }
-var HOSTED_SUPABASE_URL = process.env["PAPI_HOSTED_SUPABASE_URL"] ?? "https://guewgygcpcmrcoppihzx.supabase.co";
-var HOSTED_PROXY_ENDPOINT = `${HOSTED_SUPABASE_URL}/functions/v1/data-proxy`;
+var HOSTED_SUPABASE_URL2 = process.env["PAPI_HOSTED_SUPABASE_URL"] ?? "https://guewgygcpcmrcoppihzx.supabase.co";
+var HOSTED_PROXY_ENDPOINT = `${HOSTED_SUPABASE_URL2}/functions/v1/data-proxy`;
 var PLACEHOLDER_PATTERNS = [
   "<YOUR_DATABASE_URL>",
   "your-database-url",