@fieldwangai/agentflow 0.1.147 → 0.1.149

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (10) hide show
  1. package/README.md +7 -0
  2. package/README.zh-CN.md +6 -0
  3. package/bin/lib/flow-write.mjs +38 -0
  4. package/bin/lib/ui-server.mjs +41 -0
  5. package/builtin/web-ui/dist/assets/{WorkflowAssistantThread-1vv8x7wy.js → WorkflowAssistantThread-DPbR2UaN.js} +1 -1
  6. package/builtin/web-ui/dist/assets/{index-JETcIFk7.js → index-BSCpd5la.js} +108 -108
  7. package/builtin/web-ui/dist/index.html +1 -1
  8. package/package.json +1 -1
  9. package/skills/agentflow-author-flow/SKILL.md +9 -3
  10. package/skills/agentflow-cli/SKILL.md +18 -1
package/builtin/web-ui/dist/index.html CHANGED
@@ -30,7 +30,7 @@
30
30
  @keyframes af-app-loading-slide { from { transform: translateX(-115%); } to { transform: translateX(250%); } }
31
31
  @media (prefers-reduced-motion: reduce) { .af-app-loading__track span { width: 100%; animation: none; } }
32
32
  </style>
33
- <script type="module" crossorigin src="/assets/index-JETcIFk7.js"></script>
33
+ <script type="module" crossorigin src="/assets/index-BSCpd5la.js"></script>
34
34
  <link rel="stylesheet" crossorigin href="/assets/index-DZ328oSo.css">
35
35
  </head>
36
36
  <body>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fieldwangai/agentflow",
3
- "version": "0.1.147",
3
+ "version": "0.1.149",
4
4
  "description": "Orchestration system for long-running complex agent tasks using Cursor, OpenCode, Claude Code, or Codex as execution backends",
5
5
  "type": "module",
6
6
  "main": "bin/agentflow.mjs",
package/skills/agentflow-author-flow/SKILL.md CHANGED
@@ -3,7 +3,13 @@ name: agentflow-author-flow
3
3
  description: Generate or revise an AgentFlow flow locally from a natural-language request, validate its flow.yaml, open a single-file platform-style preview, and publish it to personal, workspace, or team scope after user confirmation. Use when a user asks Codex, Cursor, Claude Code, or another coding agent to create, draw, preview, sync, upload, or publish an AgentFlow flow without using AI Composer or manually dragging nodes.
4
4
  ---
5
5
 
6
- # Author an AgentFlow
6
+ # Author an AgentFlow Flow
7
+
8
+ This skill authors an executable **Flow/Pipeline** (`flow.yaml`). It does not
9
+ create, migrate, archive, or clean up product **Workflows**. A Workflow is the
10
+ TAPD-backed requirement entity addressed by `tapd:<id>` and is handled by
11
+ `agentflow-workflow-report`/`prd-flow` instead. A similar title or flow ID is
12
+ not evidence that the two resources are the same.
7
13
 
8
14
  Turn the user's request into a locally reviewable Flow and handle the commands on their behalf. Do not ask the user to run preview or publish commands.
9
15
 
@@ -19,7 +25,7 @@ Read [prompt and handler checks](../../reference/flow-prompt-handler-check.md) w
19
25
 
20
26
  ## Workflow
21
27
 
22
- 1. Convert the request into a short node plan. Ask only for a business choice that materially changes behavior; do not ask for YAML details.
28
+ 1. Confirm that the user wants an executable Flow/Pipeline, rather than a TAPD Workflow status/record. Convert the request into a short node plan. Ask only for a business choice that materially changes behavior; do not ask for YAML details.
23
29
  2. Choose a stable lowercase flow ID using letters, digits, hyphens, or underscores.
24
30
  3. Create the draft at `.workspace/agentflow/pipelines/<flow-id>/flow.yaml`. Start from the packaged `builtin/pipelines/new/flow.yaml` when available. Preserve any unrelated workspace files.
25
31
  4. Build nodes from authoritative definitions. Never invent `definitionId`, slot order, slot type, handle index, or control semantics. Give every instance a unique position and keep the main path left-to-right.
@@ -27,7 +33,7 @@ Read [prompt and handler checks](../../reference/flow-prompt-handler-check.md) w
27
33
  6. Generate and open the static preview with `agentflow flow preview <path-to-flow.yaml>`. In this repository, use `node bin/agentflow.mjs flow preview <path-to-flow.yaml>`. This command must exit after opening the generated `file://` HTML; do not start `agentflow ui` or another server.
28
34
  7. Report the draft path and a compact node/edge summary, then wait for the user's visual confirmation. Do not write to the AgentFlow platform before confirmation unless the user explicitly requested direct publish without review.
29
35
  8. Ask for `personal`, `workspace`, or `team` only if the user has not already chosen the destination. `team` means a workspace Flow shared as editor with the current account's active team.
30
- 9. Publish through the sibling `agentflow-cli` skill:
36
+ 9. Publish through the sibling `agentflow-cli` skill. Publishing a Flow does not publish or update a Workflow:
31
37
 
32
38
  ```bash
33
39
  node ../agentflow-cli/scripts/agentflow-cli.mjs publish-flow \
package/skills/agentflow-cli/SKILL.md CHANGED
@@ -5,6 +5,23 @@ description: Direct AgentFlow platform operation through a bundled token-backed
5
5
 
6
6
  # AgentFlow CLI
7
7
 
8
+ ## Resource boundary: Flow/Pipeline vs Workflow
9
+
10
+ AgentFlow has two different resource families:
11
+
12
+ - **Flow/Pipeline**: an executable node graph backed by `flow.yaml`. The
13
+ `list-flows`, `publish-flow`, `get-graph`, `run`, and schedule commands in
14
+ this skill operate on this family.
15
+ - **Workflow**: a TAPD-derived product/requirement record addressed as
16
+ `tapd:<id>`. It is not a Flow/Pipeline and must be read or changed through
17
+ the `workflow-*` commands and the `agentflow-workflow-report` protocol.
18
+
19
+ Never infer that a Flow with a similar name is the corresponding Workflow.
20
+ Never archive, delete, disable, or replace a Flow as a way to clean up or
21
+ change Workflow data. Before any Flow write, show the exact `flowId`, source,
22
+ and destination; before any Workflow write, resolve the canonical `tapd:<id>`
23
+ reference and follow the Workflow skill's read/merge/concurrency rules.
24
+
8
25
  Use this skill when the task is to operate AgentFlow itself from an AI agent. Do not configure or call MCP for this skill. Use the bundled CLI script instead:
9
26
 
10
27
  ```bash
@@ -157,7 +174,7 @@ The only admin write exception is audited version-membership repair. Read its st
157
174
  ## Workflow
158
175
 
159
176
  1. Check token availability with `config`.
160
- 2. Use `list-workspace` or `list-flows` to discover targets. Use `publish-flow` only after a local Flow has passed validation and the user has confirmed the preview.
177
+ 2. Use `list-workspace` or `list-flows` to discover Flow/Pipeline targets only. Use `publish-flow` only after a local Flow has passed validation and the user has confirmed the preview.
161
178
  3. Use `run` to start the flow. If the task needs the generated page/text, inspect returned `displayOutputs` or call `display-outputs`.
162
179
  4. Use `status`, `list-run-by-workspace`, and `logs` when a run is active, failed, or needs debugging.
163
180