@checkstack/automation-frontend 0.4.7 → 0.5.0

package/CHANGELOG.md

@@ -1,5 +1,64 @@
 # @checkstack/automation-frontend
 
+## 0.5.0
+
+### Minor Changes
+
+- ebef442: feat(ai): let the assistant resolve dynamic integration-action field values
+
+  Integration action fields like Jira `create_issue`'s `projectKey`, `issueTypeId`,
+  and `priorityId` are not free-form - their valid values come from the connected
+  system (the editor renders them as cascading dropdowns via `x-options-resolver`).
+  The AI assistant had no way to fetch those values, so it guessed, and propose-time
+  validation never checked them - a fabricated `projectKey` only failed at runtime.
+
+  - **New user-callable `integration.resolveConnectionOptions` RPC** (the non-admin
+    counterpart of `getConnectionOptions`, mirroring `listConnectionSummaries`), so
+    automation authors and the assistant can resolve a field's options without
+    `integration.manage`. Returns option labels/values only.
+  - **New `automation.resolveActionOptions` AI tool**: resolves a field's valid
+    values live from the connection, the same source the editor dropdown uses. It
+    is provider-agnostic (reads the field's resolver and `x-depends-on` from the
+    action's own schema) and dependency-aware - for a cascade like `issueTypeId`
+    (depends on `projectKey`), the model resolves the parent first and passes it in
+    `dependencies`.
+  - **Propose-time options validation**: `automation.propose` now checks every
+    literal dynamic-option value against the live options for its connection
+    (sourcing each field's dependency values from the same config so cascades
+    resolve), flagging values the connection does not offer with guidance to call
+    `automation.resolveActionOptions`. Templated values and fields with
+    templated/absent dependencies are skipped; a resolver lookup failure is skipped
+    rather than blocking, so transient provider flakiness never gates a proposal.
+
+  - **Automation editor works for non-admins**: the editor's option-resolver
+    bridge now calls the user-callable `listConnectionSummaries` /
+    `resolveConnectionOptions` instead of the admin-gated `listConnections` /
+    `getConnectionOptions`, so an automation author without `integration.manage`
+    gets working connection pickers and cascading dropdowns instead of empty/
+    forbidden ones.
+
+  The resolver lookup and the dependency handling are factored into reusable
+  helpers that work for any provider's `x-options-resolver` fields.
+
+### Patch Changes
+
+- Updated dependencies [ebef442]
+- Updated dependencies [ebef442]
+  - @checkstack/integration-common@0.9.0
+  - @checkstack/automation-common@0.5.0
+  - @checkstack/auth-common@0.9.0
+  - @checkstack/catalog-common@2.3.5
+  - @checkstack/script-packages-frontend@0.3.9
+  - @checkstack/gitops-frontend@0.5.6
+
+## 0.4.8
+
+### Patch Changes
+
+- Updated dependencies [c4bebbb]
+  - @checkstack/integration-common@0.8.0
+  - @checkstack/script-packages-frontend@0.3.8
+
 ## 0.4.7
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@checkstack/automation-frontend",
-  "version": "0.4.7",
+  "version": "0.5.0",
   "license": "Elastic-2.0",
   "type": "module",
   "main": "src/index.tsx",
@@ -13,14 +13,14 @@
     "lint:code": "eslint . --max-warnings 0"
   },
   "dependencies": {
-    "@checkstack/auth-common": "0.8.3",
-    "@checkstack/automation-common": "0.4.3",
-    "@checkstack/catalog-common": "2.3.4",
+    "@checkstack/auth-common": "0.9.0",
+    "@checkstack/automation-common": "0.5.0",
+    "@checkstack/catalog-common": "2.3.5",
     "@checkstack/common": "0.15.0",
     "@checkstack/frontend-api": "0.9.0",
-    "@checkstack/gitops-frontend": "0.5.5",
-    "@checkstack/integration-common": "0.7.3",
-    "@checkstack/script-packages-frontend": "0.3.7",
+    "@checkstack/gitops-frontend": "0.5.6",
+    "@checkstack/integration-common": "0.9.0",
+    "@checkstack/script-packages-frontend": "0.3.9",
     "@checkstack/secrets-frontend": "0.2.5",
     "@checkstack/signal-frontend": "0.2.4",
     "@checkstack/template-engine": "0.4.3",

package/src/editor/useConnectionOptionResolvers.ts

@@ -7,9 +7,9 @@ import type { OptionsResolver } from "@checkstack/ui";
  * Resolver name for the connection picker itself. Mirrors the
  * `CONNECTION_OPTIONS` constant every integration provider defines
  * (`provider.ts` → `*_RESOLVERS.CONNECTION_OPTIONS`). The bridge resolves
- * this one via `listConnections` (no connection is selected yet) and every
- * other resolver name via `getConnectionOptions` (cascading dropdowns that
- * depend on the chosen `connectionId`).
+ * this one via `listConnectionSummaries` (no connection is selected yet) and
+ * every other resolver name via `resolveConnectionOptions` (cascading dropdowns
+ * that depend on the chosen `connectionId`).
  */
 const CONNECTION_RESOLVER_NAME = "connectionOptions";
 
@@ -20,8 +20,13 @@ const CONNECTION_RESOLVER_NAME = "connectionOptions";
  *
  * Returns a stable, name-agnostic resolver map: the `connectionOptions`
  * resolver lists the provider's connections, and any other resolver name is
- * forwarded to `getConnectionOptions` for the currently selected connection,
- * passing the live form values as `context` for dependent fields.
+ * forwarded to `resolveConnectionOptions` for the currently selected
+ * connection, passing the live form values as `context` for dependent fields.
+ *
+ * Both calls are the USER-CALLABLE integration endpoints (`listConnectionSummaries`
+ * + `resolveConnectionOptions`), NOT the admin-gated `listConnections` /
+ * `getConnectionOptions`: an automation author needs working dropdowns without
+ * holding `integration.manage`. They return labels/ids only (no config/secrets).
  *
  * When `connectionProviderId` is undefined (a non-connection action such as
  * Log or Run Script), an empty map is returned so nothing tries to resolve.
@@ -45,7 +50,7 @@ export function useConnectionOptionResolvers(
 
         const resolver: OptionsResolver = async (formValues) => {
           if (resolverName === CONNECTION_RESOLVER_NAME) {
-            const connections = await client.listConnections.call({
+            const connections = await client.listConnectionSummaries.call({
               providerId,
             });
             return connections.map((connection) => ({
@@ -59,7 +64,7 @@ export function useConnectionOptionResolvers(
             return [];
           }
 
-          const options = await client.getConnectionOptions.call({
+          const options = await client.resolveConnectionOptions.call({
             providerId,
             connectionId,
             resolverName,