@agimon-ai/po-workflow 0.0.0-alpha.27 → 0.0.0-alpha.29
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.
- package/README.md +18 -5
- package/dist/RecoverWorkflowService-BAVHSWqr.cjs +11490 -0
- package/dist/RecoverWorkflowService-BAVHSWqr.cjs.map +1 -0
- package/dist/RecoverWorkflowService-Xo-OZAJ4.mjs +11265 -0
- package/dist/RecoverWorkflowService-Xo-OZAJ4.mjs.map +1 -0
- package/dist/cli.cjs +2596 -0
- package/dist/cli.cjs.map +1 -0
- package/dist/cli.d.mts +1 -0
- package/dist/cli.mjs +2597 -0
- package/dist/cli.mjs.map +1 -0
- package/dist/extensions/native.mjs +44 -73
- package/dist/extensions/native.mjs.map +1 -1
- package/dist/extensions/server.cjs +2118 -398
- package/dist/extensions/server.cjs.map +1 -1
- package/dist/extensions/server.d.mts.map +1 -1
- package/dist/extensions/server.mjs +2113 -371
- package/dist/extensions/server.mjs.map +1 -1
- package/dist/extensions/web.mjs +68 -150
- package/dist/extensions/web.mjs.map +1 -1
- package/dist/rolldown-runtime-VH7oDXx4.cjs +28 -0
- package/package.json +30 -10
package/README.md
CHANGED
|
@@ -4,8 +4,8 @@ Discover, launch, monitor, control, and recover asynchronous Po workflows.
|
|
|
4
4
|
|
|
5
5
|
Part of the [Po distribution](https://www.npmjs.com/package/@agimon-ai/po).
|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
host-executed steps, while Po provides session-scoped tools.
|
|
7
|
+
This package owns the workflow engine and the `workflow-mcp` CLI (`po-workflow-mcp` is an alias).
|
|
8
|
+
Workflow files describe job dependencies and host-executed steps, while Po provides session-scoped tools.
|
|
9
9
|
|
|
10
10
|
> **Alpha:** workflow and recovery contracts may change between releases.
|
|
11
11
|
|
|
@@ -127,9 +127,22 @@ dialog in the overlay slot, the Activity group's run rows (a handed-off run open
|
|
|
127
127
|
session), their stores, and the `workflow_runs` session channel, compiled into the cockpit bundle
|
|
128
128
|
by `po-web`'s build. Each surface keeps its components in a colocated `_components` folder and
|
|
129
129
|
its stores and helpers in `_lib`.
|
|
130
|
-
The hub-side data source
|
|
131
|
-
(run.json plus progress.ndjson) exactly as the engine writes it.
|
|
132
|
-
|
|
130
|
+
The hub-side data source lives in the package's backend API and reads the workflow registry
|
|
131
|
+
(run.json plus progress.ndjson) exactly as the engine writes it. The `poServer` and `poWeb`
|
|
132
|
+
blocks in package.json declare the backend and browser contributions.
|
|
133
|
+
|
|
134
|
+
## Upgrading from the separate engine
|
|
135
|
+
|
|
136
|
+
The engine now ships inside `@agimon-ai/po-workflow`. Both `workflow-mcp` and
|
|
137
|
+
`po-workflow-mcp` invoke that package's CLI. Storage paths and registry records are unchanged.
|
|
138
|
+
|
|
139
|
+
Let active runs finish before replacing an installation, or retain their exact old Node and CLI
|
|
140
|
+
payloads until they finish. A run-local `bin/workflow-mcp` launcher contains absolute paths to the
|
|
141
|
+
engine that created it. Never rewrite a live launcher or hot-swap its engine.
|
|
142
|
+
|
|
143
|
+
In repositories with canonical `.po/hooks.yaml`, replace the old package's CLI path with
|
|
144
|
+
`node_modules/@agimon-ai/po-workflow/dist/cli.mjs`, then regenerate the frontend settings with that
|
|
145
|
+
repository's hook emitter. Installation alone does not migrate existing hook registries.
|
|
133
146
|
|
|
134
147
|
## License
|
|
135
148
|
|