@papi-ai/server 0.7.74 → 0.7.76

package/dist/backfill-cycle-metrics.js

@@ -1240,6 +1240,9 @@ var init_proxy_adapter = __esm({
       // getToolCallCount + updatePhaseStatus are ABSENT: they now have edge handlers and
       // are served through the forwarder (getToolCallCount = SUP-2026-026 handler #1).
       "getContributorRole",
+      // task-3018 (C356): storeDocBody + getDocBodyUsage are now WIRED — edge case
+      // handlers + ALLOWED_METHODS/WRITE_METHODS entries exist, so they forward and
+      // hosted callers get body storage. Removed from this list, as task-3017 required.
       // task-2728 (C331): createOwnerAction REMOVED from NO_FORWARD — the PRODUCER half
       // of the owner-action queue. Six readers were wired C329 (task-2412) but the
       // producer stayed here, so the hosted Owner Action Queue was structurally empty
@@ -1267,7 +1270,7 @@ var init_proxy_adapter = __esm({
       // now works for hosted users without exposing one member's owner actions to another.
       // task-2393 (C329) — Batch B wired: markCycleLearningResolved (the P1 — hosted
       // discovered_issue_resolve hard-errored), correctLatestBuildReportEffort,
-      // updateStageExitCriteria, updateDocAction, resolveLearningsForDoneTasks all have
+      // updateStageExitCriteria, updateDocAction all have
       // edge case handlers + ALLOWED_METHODS/WRITE_METHODS entries now, so they forward.
       // task-2489 (C320): recordProgressStep is now wired to the edge data-proxy
       // (case handler + ALLOWED_METHODS/WRITE_METHODS entries), so it forwards for
@@ -1851,9 +1854,19 @@ Check PAPI_PROJECT_ID in your .mcp.json config. Find your project ID in the PAPI
         return this.invoke("updateDocStatus", [id, status, supersededBy]);
       }
       // --- Cycle Learnings ---
-      appendCycleLearnings(learnings) {
-        return this.invoke("appendCycleLearnings", [learnings]);
+      /**
+       * task-2999 / task-2998 (C356): the edge handler now calls append_cycle_learnings
+       * and returns { id, findingKey, inserted } per row, so hosted callers get the same
+       * per-row signal the pg path does. The [] normalisation stays as a floor for an
+       * edge deployed BEFORE that change — callers must read [] as "no signal
+       * available", never as "nothing was new".
+       */
+      async appendCycleLearnings(learnings) {
+        const result = await this.invoke("appendCycleLearnings", [learnings]);
+        return Array.isArray(result) ? result : [];
       }
+      // task-2998: includeResolved was missing here, so the flag could not even be SENT
+      // to the edge — the hosted caught->fixed ledger had no way to ask for history.
       getCycleLearnings(opts) {
         return this.invoke("getCycleLearnings", [opts]);
       }