@checkstack/anomaly-frontend 0.3.0 → 0.4.0

package/CHANGELOG.md

@@ -1,5 +1,190 @@
 # @checkstack/anomaly-frontend
 
+## 0.4.0
+
+### Minor Changes
+
+- 42abfff: Remove global anomaly settings — configuration is now field-only.
+
+  `AnomalySettings` (template- and assignment-level) no longer carries
+  `sensitivity`, `confirmationWindow`, `driftEnabled`, or `driftThreshold`.
+  These were duplicating the per-field configuration path with awkward
+  cascade semantics, and a single global multiplier was meaningless across
+  fields with different units (ms, %, counts).
+
+  The schema retains only the truly global concerns:
+
+  - `enabled` — master kill switch for the assignment
+  - `baselineWindow` — there is one history per system, not per field
+  - `notify` — one notification preference per assignment
+  - `fieldOverrides` — per-field configuration (where everything else now lives)
+
+  `resolveEffectiveConfig` collapses to two layers: field override → schema
+  default → engine fallback constant. The plugin-author defaults set via
+  `x-anomaly-*` annotations now drive sensitivity/window/drift across the
+  detector and drift evaluator (previously only floors were threaded
+  through the schema layer).
+
+  **Breaking changes:**
+
+  - Any global `sensitivity`/`confirmationWindow`/`driftEnabled`/
+    `driftThreshold` values previously stored in `anomaly_configurations`
+    or `anomaly_assignments` are silently stripped on parse. Users who
+    customized these globals will revert to the plugin's tuned per-field
+    defaults; if they want to keep those values they must re-apply them
+    per field in the new UI.
+  - `AnomalySettingsForm` no longer renders the global sliders. The form
+    now shows: enable toggle, baseline window selector, notify toggle,
+    field overrides editor.
+  - `AnomalyFieldOverridesEditor` props `defaultSensitivity`,
+    `defaultConfirmationWindow`, `defaultDriftEnabled`, `defaultDriftThreshold`
+    are removed. Engine fallbacks (1.0, 3, true, 2) are now hard-coded
+    internal constants used only when neither field override nor schema
+    default is set.
+  - The GitOps `System.anomaly` entry schema (in `anomaly-gitops-kinds`)
+    drops `sensitivity`, `confirmationWindow`, `driftEnabled`, and
+    `driftThreshold` to match the new `AnomalySettings` shape. YAML files
+    declaring those fields will be rejected at parse time — operators
+    must move per-field tuning into `fieldOverrides`.
+
+  This change makes the override model trivial to explain ("plugin defaults,
+  overridden per field") and removes a class of confusing "where did this
+  threshold come from?" questions.
+
+### Patch Changes
+
+- Updated dependencies [42abfff]
+- Updated dependencies [42abfff]
+- Updated dependencies [3547670]
+- Updated dependencies [1ef2e79]
+- Updated dependencies [aa89bc5]
+- Updated dependencies [3547670]
+- Updated dependencies [950d6ec]
+- Updated dependencies [3547670]
+- Updated dependencies [3547670]
+  - @checkstack/anomaly-common@1.1.0
+  - @checkstack/common@0.9.0
+  - @checkstack/ui@1.8.0
+  - @checkstack/catalog-common@2.1.0
+  - @checkstack/frontend-api@0.5.0
+  - @checkstack/notification-frontend@0.4.0
+  - @checkstack/healthcheck-frontend@0.19.0
+  - @checkstack/healthcheck-common@1.0.2
+  - @checkstack/notification-common@1.0.2
+  - @checkstack/signal-frontend@0.1.2
+
+## 0.3.1
+
+### Patch Changes
+
+- 50e5f5f: Runtime plugin system: install + uninstall plugins from npm, GitHub releases
+  (including private GitHub Enterprise instances), or tarball uploads at
+  runtime, with multi-package bundles, dependency-derived compatibility checks,
+  multi-instance coordination via a Postgres artifact store, and
+  single-coordinator destructive cleanup.
+
+  Highlights:
+
+  - New `PluginSource` discriminated union and `PluginInstaller` /
+    `PluginInstallerRegistry` interfaces in `@checkstack/backend-api`. The
+    GitHub variant accepts an optional `apiBaseUrl` so deployments backed by
+    GitHub Enterprise can install from `https://ghe.example.com/api/v3`
+    instead of `api.github.com`.
+  - New `installPackageMetadataSchema` (Zod) in `@checkstack/common` validates
+    every plugin's `package.json` at install time. Required fields: `name`,
+    `version`, `description`, `author`, `license`, `checkstack.type`,
+    `checkstack.pluginId`. Optional: `checkstack.bundle`,
+    `checkstack.usageInstructions`, `checkstack.allowInstallScripts`.
+  - New `pluginManagerContract` in `@checkstack/pluginmanager-common` with
+    `list`, `previewInstall`, `install`, `previewUninstall`, `uninstall`, and
+    `events` procedures.
+  - New `@checkstack/pluginmanager-frontend` admin UI: installed-plugins list
+    with per-row uninstall (typed-confirmation modal, schema/configs/cascade
+    toggles), install page with NPM / Tarball Upload / GitHub Release tabs
+    (Catalog tab disabled — coming soon), and an events page surfacing the
+    install/uninstall audit log.
+  - New `bunx @checkstack/scripts plugin-pack` CLI for plugin authors —
+    per-package mode produces an npm-shaped tarball; `--bundle` mode produces
+    an outer tarball containing every sibling declared in
+    `package.json#checkstack.bundle`. Published to npm so external authors
+    can `bunx` it directly without a workspace checkout.
+  - Compatibility derived from `package.json#dependencies` ranges
+    (`semver.satisfies` against the platform's loaded `@checkstack/*`
+    versions) — no separate `compatibility` field.
+  - Multi-instance: originator persists artifacts + `plugins` rows + broadcasts
+    install/uninstall; receiving instances do in-process register/unregister
+    only. Destructive ops (drop schema, delete plugin_configs, delete
+    artifacts, delete `plugins` rows) run exactly once on the originator.
+  - Fresh-instance bootstrap: `loadPlugins()` hydrates any
+    `is_uninstallable=true` plugin missing from `node_modules` from the
+    artifact store before normal Phase 1 register.
+  - New schema: `plugin_artifacts` (tarball storage), `plugin_install_events`
+    (audit/error log). `plugins` extended with `version`, `metadata`,
+    `source`, `bundle_id`, `is_primary`. Local plugin sync now writes
+    `version` from each plugin's `package.json` so the admin UI shows real
+    versions instead of `—`.
+  - Tarball-upload endpoint (`POST /api/pluginmanager/upload-tarball`) for
+    the install UI; access-gated by `pluginmanager.plugin.manage`.
+  - Plugin Manager menu link added to the user menu (main grid, alongside
+    Profile / Notification Settings / etc.).
+
+  Cross-cutting changes:
+
+  - Backend request/response logging now flows through `rootLogger` (winston)
+    instead of `hono/logger`. 5xx responses include the response body inline
+    so swallowed early-return errors are visible in the log.
+  - The `/api/:pluginId/*` dispatcher now logs which core service is missing
+    or which `pluginId` had no metadata when it 500s.
+  - New `registerCorePluginMetadata` on `PluginManager` for core routers
+    (like the plugin manager itself) that need their metadata visible to the
+    RPC dispatcher without going through the full plugin lifecycle.
+  - ESLint: `unicorn/no-null` is now disabled globally. Drizzle distinguishes
+    between `null` (writes a real SQL NULL) and `undefined` (skip the column
+    on insert), so treating them as interchangeable produced latent bugs at
+    the persistence boundary. The bulk of the patch-bumped packages above
+    reflect lint-fix touches that landed when this rule was relaxed.
+  - Workspace-wide license normalization to `Elastic-2.0` (matches
+    `LICENSE.md`). Every `package.json` in the workspace now declares the
+    same SPDX identifier; the patch bumps capture this.
+
+  Plugin packages (every `plugins/*`): added a `pack` npm script
+  (`bunx @checkstack/scripts plugin-pack`), mirrored each plugin's
+  `pluginId` from `plugin-metadata.ts` into `package.json#checkstack.pluginId`
+  so install-time validation passes, stubbed any missing required metadata
+  fields (`description`, `author`, `license`), and added
+  `checkstack.bundle` to multi-package plugin primaries (telegram, rcon, ssh,
+  jira, queue-bullmq, queue-memory, cache-memory).
+
+  Breaking changes:
+
+  - The legacy single-method `PluginInstaller` interface (`install(packageName)`)
+    is removed. Callers must use `coreServices.pluginInstallerRegistry`.
+  - The old `pluginAdminContract` and `createPluginAdminRouter` are removed.
+    Replaced by `pluginManagerContract` in `@checkstack/pluginmanager-common`
+    and `createPluginManagerRouter` in `core/backend`.
+  - `@checkstack/test-utils-backend` no longer exports
+    `createMockPluginInstaller` / `MockPluginInstaller` (the legacy interface
+    it shimmed is gone).
+
+  Note: bumps are limited to `minor` (for packages with new public API
+  surface) and `patch` (for downstream consumers, license normalization,
+  and lint fixes). No `major` bumps despite the `PluginInstaller` removal —
+  the legacy interface had no third-party consumers in the wild before this
+  runtime plugin system landed, and the contract surface is the same shape
+  modulo the rename.
+
+- Updated dependencies [50e5f5f]
+  - @checkstack/catalog-common@2.0.1
+  - @checkstack/common@0.8.0
+  - @checkstack/healthcheck-frontend@0.18.2
+  - @checkstack/notification-frontend@0.3.1
+  - @checkstack/signal-frontend@0.1.1
+  - @checkstack/ui@1.7.1
+  - @checkstack/anomaly-common@1.0.1
+  - @checkstack/frontend-api@0.4.2
+  - @checkstack/healthcheck-common@1.0.1
+  - @checkstack/notification-common@1.0.1
+
 ## 0.3.0
 
 ### Minor Changes

package/package.json

@@ -1,27 +1,28 @@
 {
   "name": "@checkstack/anomaly-frontend",
-  "version": "0.3.0",
+  "version": "0.4.0",
+  "license": "Elastic-2.0",
   "type": "module",
   "main": "src/index.tsx",
   "checkstack": {
     "type": "frontend"
   },
   "scripts": {
-    "typecheck": "tsc --noEmit",
+    "typecheck": "tsgo -b",
     "lint": "bun run lint:code",
     "lint:code": "eslint . --max-warnings 0"
   },
   "dependencies": {
-    "@checkstack/anomaly-common": "0.3.0",
-    "@checkstack/catalog-common": "1.5.3",
-    "@checkstack/common": "0.7.0",
-    "@checkstack/frontend-api": "0.4.0",
-    "@checkstack/healthcheck-common": "0.13.0",
-    "@checkstack/healthcheck-frontend": "0.18.0",
-    "@checkstack/notification-common": "0.3.0",
-    "@checkstack/notification-frontend": "0.2.36",
-    "@checkstack/signal-frontend": "0.1.0",
-    "@checkstack/ui": "1.6.1",
+    "@checkstack/anomaly-common": "1.0.1",
+    "@checkstack/catalog-common": "2.0.1",
+    "@checkstack/common": "0.8.0",
+    "@checkstack/frontend-api": "0.4.2",
+    "@checkstack/healthcheck-common": "1.0.1",
+    "@checkstack/healthcheck-frontend": "0.18.2",
+    "@checkstack/notification-common": "1.0.1",
+    "@checkstack/notification-frontend": "0.3.1",
+    "@checkstack/signal-frontend": "0.1.1",
+    "@checkstack/ui": "1.7.1",
     "date-fns": "^4.1.0",
     "lucide-react": "^0.344.0",
     "react": "^18.2.0",
@@ -29,8 +30,8 @@
     "zod": "^4.2.1"
   },
   "devDependencies": {
-    "@checkstack/scripts": "0.1.2",
-    "@checkstack/tsconfig": "0.0.5",
+    "@checkstack/scripts": "0.3.0",
+    "@checkstack/tsconfig": "0.0.7",
     "@types/react": "^18.2.0",
     "typescript": "^5.0.0"
   }

package/src/components/AnomalyConfigPanel.tsx

@@ -24,10 +24,8 @@ import {
 
 const DEFAULT_VALUES: AnomalySettingsFormValues = {
   enabled: true,
-  sensitivity: 1,
-  confirmationWindow: 3,
-  driftEnabled: true,
-  driftThreshold: 2,
+  baselineWindow: "7d",
+  notify: true,
   fieldOverrides: {},
 };
 
@@ -74,13 +72,9 @@ export function AnomalyConfigPanel({ context }: { context: AssignmentIDEContext
       const tpl = templateRecord?.data;
       setValues({
         enabled: configRecord.data.enabled ?? true,
-        sensitivity: configRecord.data.sensitivity ?? tpl?.sensitivity ?? 1,
-        confirmationWindow:
-          configRecord.data.confirmationWindow ?? tpl?.confirmationWindow ?? 3,
-        driftEnabled:
-          configRecord.data.driftEnabled ?? tpl?.driftEnabled ?? true,
-        driftThreshold:
-          configRecord.data.driftThreshold ?? tpl?.driftThreshold ?? 2,
+        baselineWindow:
+          configRecord.data.baselineWindow ?? tpl?.baselineWindow ?? "7d",
+        notify: configRecord.data.notify ?? tpl?.notify ?? true,
         fieldOverrides:
           (configRecord.data.fieldOverrides as Record<string, AnomalyFieldConfig>) ??
           {},