tines 0.0.194 → 0.0.196
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 +27 -0
- package/dist/index.js +1559 -215
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -53,6 +53,33 @@ for the whole list — and every command takes `--json` for machine-readable out
|
|
|
53
53
|
`tines <noun> --help` lists the rest: `workflows`, `context`, `journal`, `schedules`,
|
|
54
54
|
`runners`, `runs`, `routing`, `supervisor`.
|
|
55
55
|
|
|
56
|
+
## Workflow package files
|
|
57
|
+
|
|
58
|
+
Export a workflow and its inheritance/context closure as canonical JSON, validate an edited
|
|
59
|
+
file, then prepare a destination-specific review and save its signed plan:
|
|
60
|
+
|
|
61
|
+
```sh
|
|
62
|
+
tines workflows export <workflow-id> > review.json
|
|
63
|
+
tines workflows validate review.json
|
|
64
|
+
tines workflows preview review.json --choices choices.json --plan-out review.plan.json
|
|
65
|
+
tines workflows install review.json --plan review.plan.json --confirm sha256:<plan-digest>
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
Workflow names are accepted only when unique; use the ID when duplicate names exist. Export
|
|
69
|
+
selection is explicit: `--project`, repeatable `--schedule`, repeatable
|
|
70
|
+
`--tier '<state-id>=balanced'`, `--project-routing`, and `--inputs declarations.json` add
|
|
71
|
+
optional source configuration. Package and validation input may be `-` for stdin. Choices use
|
|
72
|
+
the shared document-local-ID maps described in
|
|
73
|
+
[`docs/workflow-packages.md`](https://github.com/tbuckley/tines/blob/main/docs/workflow-packages.md).
|
|
74
|
+
|
|
75
|
+
An interactive install prepares and displays the full review, atomically writes a sibling
|
|
76
|
+
`<package>.plan.json`, and asks for `yes`. A non-interactive install cannot prepare and commit
|
|
77
|
+
in one invocation: it requires a plan from a prior preview and the exact plan digest. There is
|
|
78
|
+
no blanket `--yes`. A retry checks the durable receipt first and reuses the same signed plan;
|
|
79
|
+
keep the package and plan together until the receipt is returned. Plan files contain the API
|
|
80
|
+
base, reviewed response, and signed token, but never the API key; protect them like temporary
|
|
81
|
+
authorization material.
|
|
82
|
+
|
|
56
83
|
## Running agents on your own machine
|
|
57
84
|
|
|
58
85
|
```sh
|