zk-agent-cli 0.1.0-rc.3 → 0.1.0-rc.5
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 +31 -0
- package/dist/index.js +3006 -186
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -34,6 +34,32 @@ What each step is doing:
|
|
|
34
34
|
- `workflow pay` is the flagship zkSync-native AA native-send path
|
|
35
35
|
- `suite` is the packaged surface
|
|
36
36
|
|
|
37
|
+
The packaged default story is payment-first: send native value now, stay on
|
|
38
|
+
the approval-based pay path when fee-token/default state matters, and recover
|
|
39
|
+
funding only when the workflow says the write path is blocked.
|
|
40
|
+
|
|
41
|
+
The first Agent Pay platform primitive now exists as a local-first payment
|
|
42
|
+
ingress, request, routing, and approval-orchestration surface:
|
|
43
|
+
|
|
44
|
+
```bash
|
|
45
|
+
zk-agent payment submit --wallet main --to <address> --amount <amount>
|
|
46
|
+
zk-agent payment queue
|
|
47
|
+
zk-agent payment report
|
|
48
|
+
zk-agent payment approval --request-id <id>
|
|
49
|
+
zk-agent payment sync-approval --request-id <id>
|
|
50
|
+
zk-agent payment create --wallet main --to <address> --amount <amount>
|
|
51
|
+
zk-agent payment next --request-id <id>
|
|
52
|
+
zk-agent payment inspect --request-id <id>
|
|
53
|
+
zk-agent payment intent --request-id <id>
|
|
54
|
+
zk-agent payment describe --request-id <id>
|
|
55
|
+
zk-agent payment execution --request-id <id>
|
|
56
|
+
zk-agent payment quote --request-id <id>
|
|
57
|
+
zk-agent payment refresh-quote --request-id <id>
|
|
58
|
+
zk-agent payment settlement --request-id <id>
|
|
59
|
+
zk-agent payment reconcile --request-id <id> --status <status>
|
|
60
|
+
zk-agent payment list
|
|
61
|
+
```
|
|
62
|
+
|
|
37
63
|
If readiness is unclear before you choose a fix, use:
|
|
38
64
|
|
|
39
65
|
```bash
|
|
@@ -116,6 +142,8 @@ ZK_AGENT_STORAGE_DIR=
|
|
|
116
142
|
`zk-agent wallet next --name <wallet>`: wallet-scoped repair and readiness
|
|
117
143
|
- `zk-agent workflow ...`: explicit workflow planning, persistence, status, and
|
|
118
144
|
resume questions
|
|
145
|
+
- `zk-agent payment ...`: local-first payment ingress, request capture, routing,
|
|
146
|
+
and settlement-state tracking for the Agent Pay platform layer
|
|
119
147
|
- `zk-agent suite`: the packaged post-flagship catalog once wallet readiness is
|
|
120
148
|
no longer the blocker
|
|
121
149
|
|
|
@@ -225,6 +253,9 @@ Current `suite` operator journeys:
|
|
|
225
253
|
- `unstick a write`
|
|
226
254
|
- `recover remote approval`
|
|
227
255
|
|
|
256
|
+
If you only need one default starting point inside `suite`, start with
|
|
257
|
+
`send value now`.
|
|
258
|
+
|
|
228
259
|
Use `--wallet <name>` or `--chain <chain>` when the returned suite commands
|
|
229
260
|
should stay on a non-default wallet or chain.
|
|
230
261
|
|