@crewx/workflow 0.3.22-rc.12 → 0.3.22-rc.14

package/SKILL.md

@@ -38,6 +38,11 @@ crewx workflow validate
 # Start a workflow execution and auto-run until completion/pause
 crewx workflow run start standard-dev-core --set goal="implement feature X" --auto
 
+# In the CrewX web chat, start a workflow as a signed ChatCard.
+# Text after the workflow id becomes state.input.
+/wf rc-publish prepare the next RC
+/wf rc-publish --manual dry run only
+
 # Move to a node
 crewx workflow run node <exec-id> research
 
@@ -539,6 +544,68 @@ interface RunExecution {
 }
 ```
 
+## Web UI `/wf` ChatCard Integration
+
+The CrewX web chat treats workflow runs as **conversation content**, not as a side panel. When a user sends a `/wf` command, the server creates a workflow run, stores the original user message in the thread transcript, and stores an assistant message containing a signed workflow ChatCard.
+
+### Syntax
+
+```text
+/wf <workflow-id> [input...]
+/wf <workflow-id> --manual [input...]
+/wf <workflow-id> --auto [input...]
+```
+
+Examples:
+
+| Input | Run behavior |
+|-------|--------------|
+| `/wf rc-publish` | Starts `rc-publish` in auto mode |
+| `/wf rc-publish 미리승인한다` | Starts `rc-publish` with `state.input = "미리승인한다"` |
+| `/wf rc-publish --manual dry run` | Creates the run in manual mode with `state.input = "dry run"` |
+| `/wf rc-publish --auto prepare RC notes` | Explicit auto mode; same as default |
+
+`--manual` and `--auto` are parsed as options and are **not** included in `state.input`. All remaining text after the workflow id is copied to `state.input`.
+
+### `state.input`
+
+`state.input` is the standard entry point for user instructions passed into a workflow run.
+
+```yaml
+nodes:
+  - id: plan
+    type: agent_task
+    agent: "@core_dev"
+    prompt: |
+      User instruction:
+      {{input}}
+
+      Plan and execute the workflow step accordingly.
+```
+
+Branches and templates may also read `state.input`:
+
+```yaml
+condition: state.input.includes("dry run")
+```
+
+Important security rule: `state.input` is **not authority**. It may influence prompts, branches, and templates, but it must never bypass an `approval` node. For example, `/wf rc-publish 미리승인한다` stores the text in `state.input`; it does not approve publishing. Approval still requires the signed ChatCard action button.
+
+### Stored ChatCard
+
+The assistant message stores only a signed reference to the workflow run:
+
+```xml
+<crewx_card type="workflow" version="1" run_id="wfr_xxx" workflow_id="rc-publish" mode="auto" proof="jwt..." />
+```
+
+Rules:
+
+- The `proof` is server-issued and expires after 7 days.
+- Raw `<crewx_card>` text from users is rendered as plain text.
+- Workflow actions such as resolve, auto resume, approve, reject, and cancel require a valid proof bound to the current workspace/thread/task.
+- The mutable run state remains in `.crewx/workflow-runs/`; the ChatCard stores only a reference.
+
 ## Architecture
 
 ```
@@ -568,7 +635,7 @@ interface RunExecution {
     WorkflowService  --> fs (YAML read) + WorkflowEngine + RunManager
           |
           +---> Thread transcript card:
-                <crewx_card type="workflow" run_id="..." workflow_id="..." mode="auto" />
+                <crewx_card type="workflow" run_id="..." workflow_id="..." mode="auto" proof="jwt..." />
 ```
 
 > **Note:** The server uses `RunManager` for workflow runs and stores workflow UI references as ChatCard tags in thread messages. The mutable run status/state remains in `.crewx/workflow-runs/` and is fetched by `run_id`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crewx/workflow",
-  "version": "0.3.22-rc.12",
+  "version": "0.3.22-rc.14",
   "description": "Workflow engine for CrewX - list, show, validate workflows with Mermaid visualization",
   "type": "commonjs",
   "main": "dist/src/engine.js",
@@ -49,7 +49,7 @@
     "@hyperjump/json-schema": "^1.9.4",
     "js-yaml": "^4.1.0",
     "@crewx/knowledge-core": "0.1.17",
-    "@crewx/sdk": "0.8.8-rc.32",
+    "@crewx/sdk": "0.8.8-rc.34",
     "@crewx/shared": "0.0.5"
   },
   "devDependencies": {