@gapi/gcli 1.8.245 → 1.8.247

package/README-CLI.md

@@ -69,6 +69,19 @@ Commands:
   workspace:start [options]                            Connect the current directory to the Lambforge chat as a local workspace: the AI agents can read/edit its files and run commands here (outbound connection only - works behind NAT)
   workspace:list [options]                             List your local workspaces (online status, directory, processes)
   workspace:delete [options]                           Delete a local workspace and revoke its token (default: the one registered for this directory)
+  workflow:list [options]                              List the project workflows
+  workflow:get [options]                               Print a workflow as YAML (the format workflow:apply reads), or write it with -o
+  workflow:generate [options]                          Draft a workflow with AI from plain language (or change one with --name / --from). Prints or writes YAML; saves only with --apply
+  workflow:apply [options]                             Create or update a workflow from a YAML/JSON file (workflow: {name, description, definition})
+  workflow:validate [options]                          Check a workflow file against the cluster (lambdas exist, graph is valid)
+  workflow:delete [options]                            Delete a workflow and all of its runs
+  workflow:run [options]                               Start a run; the JSON input is the first step request body. --wait follows it to the end
+  workflow:runs [options]                              List a workflow runs, newest first
+  workflow:status [options]                            Show a run: its step events, error and output (--follow until it ends)
+  workflow:cancel [options]                            Cancel a running run
+  workflow:trigger:add [options]                       Start runs from an HTTP URL (--http; the JSON body is the input) or a schedule (--cron). Needs Fission 1.26+ on the cluster
+  workflow:trigger:list [options]                      List a workflow HTTP and schedule triggers
+  workflow:trigger:remove [options]                    Remove a workflow trigger
   help [command]                                       display help for command
 
 --- Subcommand: login ---
@@ -1009,3 +1022,158 @@ Delete a local workspace and revoke its token (default: the one registered for t
 Options:
   --id <id>   Workspace id (see `gcli workspace:list`)
   -h, --help  display help for command
+
+--- Subcommand: workflow:list ---
+Usage: gcli workflow:list [options]
+
+List the project workflows
+
+Options:
+  -p, --project <project>
+  -h, --help               display help for command
+
+--- Subcommand: workflow:get ---
+Usage: gcli workflow:get [options]
+
+Print a workflow as YAML (the format workflow:apply reads), or write it with -o
+
+Options:
+  -p, --project <project>
+  -n, --name <name>        Workflow name
+  -o, --out <file>         Write the YAML to this file
+  -h, --help               display help for command
+
+--- Subcommand: workflow:generate ---
+Usage: gcli workflow:generate [options]
+
+Draft a workflow with AI from plain language (or change one with --name / --from). Prints or writes YAML; saves only with --apply
+
+Options:
+  -p, --project <project>
+  -d, --description <text>  What the workflow should do, e.g. "charge the card
+                            with retries, then email the receipt"
+  -n, --name <name>         Workflow name: an existing one is changed, a new
+                            one is named so
+  --from <file>             Change this workflow file instead
+  -o, --out <file>          Write the draft YAML to this file
+  --apply                   Save the draft as the workflow (needs a name)
+  -h, --help                display help for command
+
+--- Subcommand: workflow:apply ---
+Usage: gcli workflow:apply [options]
+
+Create or update a workflow from a YAML/JSON file (workflow: {name, description, definition})
+
+Options:
+  -p, --project <project>
+  -f, --file <file>         Workflow file
+  -n, --name <name>         Overrides workflow.name from the file
+  -d, --description <text>  Overrides workflow.description
+  -h, --help                display help for command
+
+--- Subcommand: workflow:validate ---
+Usage: gcli workflow:validate [options]
+
+Check a workflow file against the cluster (lambdas exist, graph is valid)
+
+Options:
+  -p, --project <project>
+  -f, --file <file>        Workflow file
+  -h, --help               display help for command
+
+--- Subcommand: workflow:delete ---
+Usage: gcli workflow:delete [options]
+
+Delete a workflow and all of its runs
+
+Options:
+  -p, --project <project>
+  -n, --name <name>        Workflow name
+  -h, --help               display help for command
+
+--- Subcommand: workflow:run ---
+Usage: gcli workflow:run [options]
+
+Start a run; the JSON input is the first step request body. --wait follows it to the end
+
+Options:
+  -p, --project <project>
+  -n, --name <name>        Workflow name
+  -i, --input <json>       Run input as JSON (default {})
+  --input-file <file>      Read the run input from a JSON file
+  -w, --wait               Print each step as it happens until the run ends
+  -h, --help               display help for command
+
+--- Subcommand: workflow:runs ---
+Usage: gcli workflow:runs [options]
+
+List a workflow runs, newest first
+
+Options:
+  -p, --project <project>
+  -n, --name <name>        Workflow name
+  -l, --limit <limit>      How many (default 50)
+  -h, --help               display help for command
+
+--- Subcommand: workflow:status ---
+Usage: gcli workflow:status [options]
+
+Show a run: its step events, error and output (--follow until it ends)
+
+Options:
+  -p, --project <project>
+  -n, --name <name>        Workflow name
+  -r, --run <run>          Run name (see workflow:runs)
+  -f, --follow             Keep printing events until the run ends
+  -h, --help               display help for command
+
+--- Subcommand: workflow:cancel ---
+Usage: gcli workflow:cancel [options]
+
+Cancel a running run
+
+Options:
+  -p, --project <project>
+  -n, --name <name>        Workflow name
+  -r, --run <run>          Run name (see workflow:runs)
+  -h, --help               display help for command
+
+--- Subcommand: workflow:trigger:add ---
+Usage: gcli workflow:trigger:add [options]
+
+Start runs from an HTTP URL (--http; the JSON body is the input) or a schedule (--cron). Needs Fission 1.26+ on the cluster
+
+Options:
+  -p, --project <project>
+  -n, --name <name>        Workflow name
+  --http                   An HTTP trigger: <router>/<project>/workflows/<path>
+  --path <path>            HTTP path under /workflows/ (default: the workflow
+                           name)
+  --method <methods>       HTTP methods, comma separated (default POST)
+  --cron <schedule>        A schedule: "@every 1h", "0 9 * * 1-5", "@daily"
+                           (UTC)
+  -i, --input <json>       Schedule: the input of every run (default {})
+  --input-file <file>      Schedule: read the run input from a JSON file
+  -h, --help               display help for command
+
+--- Subcommand: workflow:trigger:list ---
+Usage: gcli workflow:trigger:list [options]
+
+List a workflow HTTP and schedule triggers
+
+Options:
+  -p, --project <project>
+  -n, --name <name>        Workflow name
+  -h, --help               display help for command
+
+--- Subcommand: workflow:trigger:remove ---
+Usage: gcli workflow:trigger:remove [options]
+
+Remove a workflow trigger
+
+Options:
+  -p, --project <project>
+  -n, --name <name>        Workflow name
+  -t, --trigger <trigger>  Trigger id, path or schedule (see
+                           workflow:trigger:list)
+  -h, --help               display help for command

package/README.md

@@ -761,6 +761,79 @@ gcli cron:list
 gcli cron:delete --lambdaName 'my-function'
 ```
 
+### Workflows
+
+A workflow runs several lambdas as one process: each step gets the previous
+step's response, steps can retry, branch (Choice), fan out (Parallel / Map)
+or wait, and every run is recorded step by step. Workflows must be included
+in the project's plan (`allowWorkflows`).
+
+```bash
+# Draft one with AI from plain language (MiniMax), review the YAML, save it
+gcli workflow:generate -d "charge the card with retries; if it fails wait 1h and email the customer; otherwise send the receipt" -o order-flow.yaml
+gcli workflow:apply -f order-flow.yaml --name order-flow     # create or update by name
+
+# Or change an existing one in place
+gcli workflow:generate --name order-flow -d "add a 5 minute wait before the email" --apply
+
+# Run it and watch each step
+gcli workflow:run --name order-flow --input '{"orderId": 42}' --wait
+gcli workflow:runs --name order-flow
+gcli workflow:status --name order-flow --run order-flow-abc12 --follow
+gcli workflow:cancel --name order-flow --run order-flow-abc12
+
+gcli workflow:list
+gcli workflow:get --name order-flow -o order-flow.yaml        # edit, then workflow:apply
+gcli workflow:validate -f order-flow.yaml
+gcli workflow:delete --name order-flow                        # also deletes its runs
+```
+
+**Triggers** start runs without anyone calling `workflow:run` (Fission 1.26+
+on the workflow's cluster creates the run itself):
+
+```bash
+# An HTTP URL: every request starts a run, the JSON body is the run input,
+# the answer is 202 {"run": "..."}; default path = the workflow name, POST
+gcli workflow:trigger:add --name order-flow --http --path orders --method POST
+curl -X POST 'https://functions.lambforge.com/<projectId>/workflows/orders' -d '{"orderId": 42}'
+
+# A schedule (UTC) with a fixed run input
+gcli workflow:trigger:add --name nightly-report --cron "0 6 * * *" --input '{"scope": "all"}'
+
+gcli workflow:trigger:list --name order-flow
+gcli workflow:trigger:remove --name order-flow --trigger orders   # id, path or schedule
+```
+
+`workflow:runs` shows how each run started (`manual`, `http`, `schedule`).
+
+The file `workflow:get` / `workflow:generate` write (and `workflow:apply`
+reads) - a Fission `kind: Workflow` manifest or a bare `startAt` + `states`
+works too:
+
+```yaml
+workflow:
+  name: order-flow
+  description: Charge, then mail the receipt
+  definition:
+    startAt: charge
+    states:
+      charge:
+        type: Task
+        function: { type: name, name: charge }
+        retry: { maxAttempts: 3, backoffBase: 2s, backoffCap: 30s }
+        next: mail
+      mail:
+        type: Task
+        function: { type: name, name: mailer }
+        end: true
+```
+
+Step types: Task (call a lambda), Choice (branch on a value), Parallel,
+Map (once per list item), Wait (durable pause), Succeed, Fail. A step gets
+one attempt unless it has `retry`. Runs can only be started by
+`workflow:run` (or the UI / API) - HTTP and cron triggers cannot start a
+workflow yet.
+
 ### Monitoring & Testing
 
 Debug your functions directly from the terminal.

package/docs/changelog.d/2026-10-25-workflows-workflow-commands-with-ai-drafts.md

@@ -0,0 +1,8 @@
+## 2026-10-25 - workflows: workflow commands with AI drafts
+
+**Feature:** workflows · **Type:** feat
+
+- New `workflow:*` commands (`src/commands/workflow/`): list, get (YAML), generate (AI draft via `generateWorkflowDraft`, from plain language or as a change to an existing workflow / file; `-o` writes YAML, `--apply` saves), apply (create or update by name), validate, delete, run (`--wait` prints each step event live until the run ends), runs, status (`--follow`), cancel. Workflows are addressed by name. Files: `workflow: {name, description, definition}`, a `kind: Workflow` manifest, or a bare definition. API in `gql-client.ts` (Workflows section), fragments in `services/types/workflow.fragment.ts`.
+- **Test:** `npx jest --coverage=false test/workflow.spec.ts` (file shapes, input parsing, event rendering, apply create/update, generate change + apply, run --wait).
+- **Debug:** see `docs/features/workflows.md`; the commands need a user login (not granted to CI tokens yet).
+- **Verification:** jest 6/6; tsc + eslint clean; build OK and `--help` lists the 10 commands (`release/index.js` restored, README-CLI.md regenerated); all 10 GraphQL documents validated against the live local gateway schema. Not run end to end here: the gcli login points at production, which has no workflows yet.

package/docs/changelog.d/2026-10-26-workflows-workflow-trigger-commands-for-http-and-schedule-triggers.md

@@ -0,0 +1,23 @@
+## 2026-10-26 - workflows: workflow:trigger commands for HTTP and schedule triggers
+
+**Feature:** workflows · **Type:** feat
+
+- `workflow:trigger:add` (`--http [--path] [--method]` or `--cron
+  "<schedule>" [-i | --input-file]`), `workflow:trigger:list`,
+  `workflow:trigger:remove -t <id | path | schedule | Fission name>`
+  (`src/commands/workflow/trigger-*.ts`), on the graphql-server-lambdas
+  `addWorkflowTrigger` / `removeWorkflowTrigger` (Fission 1.26+ fork
+  `workflow-triggers` creates the runs).
+- Option handling and output are pure (`triggers.ts`: `buildTriggerInput`,
+  `findTrigger`, `triggerRow`, `runSource`); `workflow:runs` gained a `by`
+  column (manual / http / schedule). `WorkflowFragment.triggers`,
+  `WorkflowRunFragment.triggerKind / triggerName`; client calls in
+  `gql-client.ts`.
+- README Workflows section + regenerated `README-CLI.md`.
+- **Test:** `npx jest --coverage=false test/workflow.spec.ts` (11 pass, 5 new).
+- **Debug:** `Workflow triggers need Fission 1.26 or newer on this cluster`
+  is the backend saying the cluster is too old; `Pass either --http or
+  --cron` is the option check.
+- **Verification:** gcli jest 114/114; tsc + eslint clean; the new
+  mutations and fragments validated against the local gateway schema;
+  not run against production (gcli login points at production).

package/docs/features/README.md

@@ -35,3 +35,4 @@ Outline (drop sections that don't apply):
 | `lambforge-agent-skill` | [lambforge-agent-skill.md](lambforge-agent-skill.md) | The agent skill that teaches gcli + `mcp:start`; canonical doc in gql-fission |
 | `dedicated-platform-cluster` | [dedicated-platform-cluster.md](dedicated-platform-cluster.md) | `cluster:status/health/scale/autoscale/...` commands; canonical doc in lambforge-agent |
 | `ci-token-scopes` | [ci-token-scopes.md](ci-token-scopes.md) | Which permission each command needs; `mq-trigger:*` commands; canonical doc in graphql-server |
+| `workflows` | [workflows.md](workflows.md) | `workflow:*` commands incl. AI drafts (`workflow:generate`); canonical doc in graphql-server-lambdas |

package/docs/features/workflows.md

@@ -0,0 +1,64 @@
+# Workflows — gcli slice
+
+**Feature slug:** `workflows` · canonical doc:
+`graphql-server-lambdas/docs/features/workflows.md` (AI drafts:
+`graphql-server/docs/features/workflows.md`).
+
+`workflow:*` commands (`src/commands/workflow/`), all as the `gcli login`
+user through the gateway; workflows are addressed by **name** (resolved to
+the id with `listWorkflows`):
+
+| Command | API |
+|---|---|
+| `workflow:list` | `listWorkflows` |
+| `workflow:get -n [-o file]` | `listWorkflows` → YAML |
+| `workflow:generate -d "..." [-n name \| --from file] [-o file] [--apply]` | `generateWorkflowDraft` (graphql-server, MiniMax M3.1 Flash); `--apply` = `workflow:apply` |
+| `workflow:apply -f file [-n] [-d]` | `createWorkflow`, or `updateWorkflow` when the name exists |
+| `workflow:validate -f file` | `validateWorkflow` (graph + lambdas on the cluster) |
+| `workflow:delete -n` | `deleteWorkflow` (runs too) |
+| `workflow:run -n [-i json \| --input-file] [--wait]` | `startWorkflowRun`; `--wait` polls `getWorkflowRun` every 2 s and prints each new event until the run is terminal |
+| `workflow:runs -n [-l]` | `listWorkflowRuns` (column `by`: manual / http / schedule, from `triggerKind`) |
+| `workflow:status -n -r run [--follow]` | `getWorkflowRun` (events, error, output) |
+| `workflow:cancel -n -r run` | `cancelWorkflowRun` |
+| `workflow:trigger:add -n (--http [--path] [--method a,b] \| --cron "<schedule>" [-i json \| --input-file])` | `addWorkflowTrigger`; prints the trigger and, for HTTP, a `curl` line |
+| `workflow:trigger:list -n` | the workflow's `triggers` (id, kind, URL or schedule, input) |
+| `workflow:trigger:remove -n -t <id \| path \| schedule \| Fission name>` | `removeWorkflowTrigger` |
+
+Triggers (2026-10-26) are HTTP URLs (`<router>/<projectId>/workflows/<path>`,
+the JSON body is the run input, 202 `{run}`) and schedules (cron, UTC, with a
+fixed input) that start runs. Fission 1.26+ (fork `workflow-triggers`) on the
+workflow's cluster creates the run. The option handling is pure and tested:
+`src/commands/workflow/triggers.ts` (`buildTriggerInput`, `findTrigger`,
+`triggerRow`, `runSource`).
+
+The workflow file (`definition.ts` `parseWorkflowFile`) accepts
+`workflow: {name, description, clusterId, definition}`, the same without the
+`workflow:` key, a Fission `kind: Workflow` manifest, or a bare definition;
+`toWorkflowYaml` writes the first form. API calls are in
+`src/services/gql-client.ts` (Workflows section), selection sets in
+`src/services/types/workflow.fragment.ts`, types in
+`src/commands/workflow/types.ts`.
+
+Not granted to CI tokens (INTEGRATION role) yet: the workflow resolvers are
+USER-only in graphql-server-lambdas, so these commands need `gcli login`.
+
+## How to test
+
+`npx jest --coverage=false test/workflow.spec.ts`. Real: log in to a
+gateway whose project has `allowWorkflows`, then
+`gcli workflow:generate -d "..." -n demo --apply` and
+`gcli workflow:run -n demo --wait`; triggers:
+`gcli workflow:trigger:add -n demo --http`, then `curl -X POST <url> -d '{}'`
+and `gcli workflow:runs -n demo` shows the run `by` http.
+
+## How to debug
+
+- `No workflow "x"`: names are per project (`-p` or the `gcli login`
+  project).
+- `Workflows are not available on your current plan`: the plan lacks
+  `allowWorkflows`.
+- `Workflows are not enabled on this cluster`: the cluster runs Fission
+  without `workflows.enabled` (canonical doc, Requires).
+- `Workflow triggers need Fission 1.26 or newer on this cluster`: the
+  cluster's Fission CRDs predate workflow triggers.
+- `Pass either --http or --cron`: exactly one of them.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gapi/gcli",
-  "version": "1.8.245",
+  "version": "1.8.247",
   "repository": {
     "type": "git",
     "url": "https://github.com/Stradivario/gapi.git"