@checkstack/healthcheck-backend 1.7.2 → 1.8.1

package/CHANGELOG.md

@@ -1,5 +1,82 @@
 # @checkstack/healthcheck-backend
 
+## 1.8.1
+
+### Patch Changes
+
+- Updated dependencies [bb6f0fe]
+- Updated dependencies [bb6f0fe]
+  - @checkstack/maintenance-common@1.6.0
+  - @checkstack/ai-backend@0.6.1
+  - @checkstack/sdk@0.107.1
+  - @checkstack/automation-backend@0.8.1
+  - @checkstack/secrets-backend@0.2.8
+  - @checkstack/catalog-backend@1.4.12
+  - @checkstack/incident-backend@1.7.4
+  - @checkstack/satellite-backend@0.6.12
+  - @checkstack/script-packages-backend@0.3.11
+
+## 1.8.0
+
+### Minor Changes
+
+- 4134ed9: Add a `healthcheck.runHistory` AI tool so the assistant can answer timeline and
+  root-cause questions ("what issues did system X have between T1 and T2", "show
+  the unhealthy runs in the last hour"). It projects the existing filtered
+  `getHistory` query, exposing the `systemId`, `startDate`/`endDate`, and
+  `statusFilter` filters, and is gated by the same public, default-on
+  `healthcheck.status` view rule the dashboard history view uses (no extra grant
+  needed). It complements `healthcheck.status`, which only reports current state.
+
+### Patch Changes
+
+- 079369a: Fix producing automation actions that double-prefixed their artifact type. The
+  action registry qualifies `produces` with the owning plugin id, but several
+  actions set `produces` to an already-qualified id, so it became
+  `plugin.plugin.type` (e.g. `automation.automation.analysis`,
+  `maintenance.maintenance.window`). This stored artifacts under a type that
+  matched no registered artifact type, and — because the run scope exposes a
+  produced artifact under its type's local name — broke the documented downstream
+  reference `artifacts.<actionId>.<name>.<field>` (a `choose`/condition/template
+  referencing the analysis output, a created incident/maintenance/etc. silently
+  saw `undefined` and took the wrong branch).
+
+  Fixed in `ai_analyze` (`analysis`), the built-in `notify_user`
+  (`notify_user_result`), and the catalog (`system_record`), maintenance
+  (`window`), notification (`send_result`), dependency (`edge`), and healthcheck
+  (`assignment`) actions — each now uses the unqualified local id matching its
+  artifact-type definition.
+
+  BREAKING (beta): any automation that referenced one of these artifacts via the
+  old double-prefixed scope key (e.g. `artifacts.x['automation.analysis']`) must
+  switch to the documented form (`artifacts.x.analysis.<field>`). The
+  double-prefixed key was never the intended/documented path.
+
+- Updated dependencies [079369a]
+- Updated dependencies [4134ed9]
+- Updated dependencies [6005271]
+- Updated dependencies [748268c]
+- Updated dependencies [4134ed9]
+- Updated dependencies [4134ed9]
+- Updated dependencies [079369a]
+- Updated dependencies [079369a]
+  - @checkstack/ai-backend@0.6.0
+  - @checkstack/ai-common@0.4.0
+  - @checkstack/automation-backend@0.8.0
+  - @checkstack/backend-api@0.22.0
+  - @checkstack/catalog-backend@1.4.11
+  - @checkstack/incident-backend@1.7.3
+  - @checkstack/satellite-backend@0.6.11
+  - @checkstack/command-backend@0.2.8
+  - @checkstack/gitops-backend@0.5.8
+  - @checkstack/script-packages-backend@0.3.10
+  - @checkstack/secrets-backend@0.2.8
+  - @checkstack/sdk@0.106.1
+  - @checkstack/catalog-common@2.3.6
+  - @checkstack/healthcheck-common@1.6.2
+  - @checkstack/incident-common@1.5.2
+  - @checkstack/maintenance-common@1.5.2
+
 ## 1.7.2
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@checkstack/healthcheck-backend",
-  "version": "1.7.2",
+  "version": "1.8.1",
   "license": "Elastic-2.0",
   "type": "module",
   "main": "src/index.ts",
@@ -14,29 +14,29 @@
     "lint:code": "eslint . --max-warnings 0"
   },
   "dependencies": {
-    "@checkstack/backend-api": "0.21.7",
-    "@checkstack/ai-backend": "0.5.0",
-    "@checkstack/ai-common": "0.3.0",
-    "@checkstack/script-packages-backend": "0.3.9",
+    "@checkstack/backend-api": "0.22.0",
+    "@checkstack/ai-backend": "0.6.1",
+    "@checkstack/ai-common": "0.4.0",
+    "@checkstack/script-packages-backend": "0.3.11",
     "@checkstack/cache-api": "0.3.12",
     "@checkstack/cache-utils": "0.2.17",
-    "@checkstack/catalog-backend": "1.4.10",
-    "@checkstack/catalog-common": "2.3.5",
-    "@checkstack/command-backend": "0.2.7",
+    "@checkstack/catalog-backend": "1.4.12",
+    "@checkstack/catalog-common": "2.3.6",
+    "@checkstack/command-backend": "0.2.8",
     "@checkstack/common": "0.15.0",
-    "@checkstack/gitops-backend": "0.5.7",
+    "@checkstack/gitops-backend": "0.5.8",
     "@checkstack/gitops-common": "0.6.3",
-    "@checkstack/healthcheck-common": "1.6.1",
+    "@checkstack/healthcheck-common": "1.6.2",
     "@checkstack/secrets-common": "0.2.3",
-    "@checkstack/secrets-backend": "0.2.7",
-    "@checkstack/incident-backend": "1.7.2",
-    "@checkstack/incident-common": "1.5.1",
-    "@checkstack/automation-backend": "0.7.0",
-    "@checkstack/maintenance-common": "1.5.1",
+    "@checkstack/secrets-backend": "0.2.8",
+    "@checkstack/incident-backend": "1.7.4",
+    "@checkstack/incident-common": "1.5.2",
+    "@checkstack/automation-backend": "0.8.1",
+    "@checkstack/maintenance-common": "1.6.0",
     "@checkstack/notification-common": "1.3.3",
     "@checkstack/queue-api": "0.3.12",
-    "@checkstack/satellite-backend": "0.6.10",
-    "@checkstack/sdk": "0.105.1",
+    "@checkstack/satellite-backend": "0.6.12",
+    "@checkstack/sdk": "0.107.1",
     "@checkstack/signal-common": "0.2.9",
     "@hono/zod-validator": "^0.7.6",
     "drizzle-orm": "^0.45.0",
@@ -50,7 +50,7 @@
   "devDependencies": {
     "@checkstack/drizzle-helper": "0.0.5",
     "@checkstack/scripts": "0.6.1",
-    "@checkstack/test-utils-backend": "0.1.41",
+    "@checkstack/test-utils-backend": "0.1.42",
     "@checkstack/tsconfig": "0.0.7",
     "@types/bun": "^1.0.0",
     "@types/tdigest": "^0.1.5",

package/src/ai/healthcheck-projection.test.ts

@@ -34,3 +34,40 @@ describe("healthcheck.status projection", () => {
     expect(tool.requiredAccessRules).not.toEqual(["ai.chat.read"]);
   });
 });
+
+// The run-history projection lets the assistant answer timeline / root-cause
+// questions ("what issues did system X have between T1 and T2"). It must expose
+// the filter inputs (systemId, date window, statusFilter) and be gated by the
+// public, default-on `healthcheck.status` VIEW rule (the same one the dashboard
+// history view uses), so it needs no special grant.
+describe("healthcheck.runHistory projection", () => {
+  const tool = buildProjectedTool({
+    procedure: healthCheckContract.getHistory,
+    sourcePluginMetadata: pluginMetadata,
+    procedureKey: "getHistory",
+    name: "healthcheck.runHistory",
+    description: "List historical health-check runs. Read-only.",
+    effect: "read",
+    execute: deferredProjectionExecute,
+  });
+
+  test("uses the overridden tool name", () => {
+    expect(tool.name).toBe("healthcheck.runHistory");
+  });
+
+  test("is classified as a read-only effect", () => {
+    expect(tool.effect).toBe("read");
+  });
+
+  test("exposes the timespan/system/status filter inputs to the model", () => {
+    const inputShape = tool.input as { shape?: Record<string, unknown> };
+    expect(inputShape.shape).toBeDefined();
+    for (const field of ["systemId", "startDate", "endDate", "statusFilter"]) {
+      expect(inputShape.shape?.[field]).toBeDefined();
+    }
+  });
+
+  test("is gated by the public healthcheck.status view rule, not the chat gate", () => {
+    expect(tool.requiredAccessRules).toEqual(["healthcheck.healthcheck.status.read"]);
+  });
+});

package/src/automations.ts

@@ -232,7 +232,7 @@ export function createHealthCheckActions(
     category: "Health",
     icon: "Play",
     config: new Versioned({ version: 1, schema: runNowConfigSchema }),
-    produces: "healthcheck.assignment",
+    produces: "assignment",
     execute: async ({ config, logger }) => {
       const queue = deps.queueManager.getQueue<HealthCheckJobPayload>(
         HEALTH_CHECK_QUEUE,
@@ -267,7 +267,7 @@ export function createHealthCheckActions(
     category: "Health",
     icon: "Power",
     config: new Versioned({ version: 1, schema: assignmentToggleConfigSchema }),
-    produces: "healthcheck.assignment",
+    produces: "assignment",
     execute: async ({ config, logger }) => {
       const updated = await deps.service.setAssignmentEnabled(
         config.systemId,
@@ -310,7 +310,7 @@ export function createHealthCheckActions(
     category: "Health",
     icon: "PowerOff",
     config: new Versioned({ version: 1, schema: assignmentToggleConfigSchema }),
-    produces: "healthcheck.assignment",
+    produces: "assignment",
     execute: async ({ config, logger }) => {
       const updated = await deps.service.setAssignmentEnabled(
         config.systemId,

package/src/index.ts

@@ -270,6 +270,32 @@ export default createBackendPlugin({
           execute: deferredProjectionExecute,
         });
 
+        // Historical run-by-run check results, filterable by system, time
+        // window, and status. Complements `healthcheck.status` (which is only
+        // CURRENT state): this is how the assistant answers "what issues did
+        // system X have between T1 and T2" or "show the unhealthy runs in the
+        // last hour". Gated by the public, default-on `healthcheck.status` VIEW
+        // rule (the same one the dashboard's history view uses) - it returns the
+        // public run shape with no sensitive `result` payload, so it needs no
+        // special grant. (The detailed variant carrying `result` lives behind
+        // `healthcheck.details` and is intentionally NOT projected.)
+        env.getExtensionPoint(aiToolProjectionExtensionPoint).expose({
+          procedure: healthCheckContract.getHistory,
+          sourcePluginMetadata: pluginMetadata,
+          procedureKey: "getHistory",
+          name: "healthcheck.runHistory",
+          description:
+            "List historical health-check runs (individual timestamped results) " +
+            "for root-cause and timeline questions. Filter by `systemId`, a " +
+            "`startDate`/`endDate` window, and/or `statusFilter` (e.g. " +
+            "[\"unhealthy\",\"degraded\"]) to find when and how a system was " +
+            "failing over a period. Pass `sortOrder` (\"desc\" for most recent " +
+            "first) and use `limit`/`offset` to page. Use this for past/timespan " +
+            "questions; use healthcheck.status for the current state. Read-only.",
+          effect: "read",
+          execute: deferredProjectionExecute,
+        });
+
         // Contribute this plugin's per-system health problems to the AI
         // `system.issues` aggregator. PER-SOURCE access is OUR job: gate on the
         // principal's `healthcheck.status` grant and return {} (never throw)