@dvmkit/dvmctl 0.3.5-rc.1 → 0.4.0-rc.2
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 +2 -2
- package/dist/dvmctl.js +23 -23
- package/package.json +1 -1
- package/skills/build-dvm/SKILL.md +3 -1
- package/skills/build-dvm/operating.md +4 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: build-dvm
|
|
3
|
-
description: Build and operate a Digital Vending Machine with dvmkit. Use when asked to turn an idea into a paid
|
|
3
|
+
description: Build and operate a Digital Vending Machine with dvmkit. Use when asked to turn an idea into a paid service, implement a capability, test payments or Lightning-funded credit, deploy or update a DVM, inspect earnings or health, recover a failed operation, or retire a service.
|
|
4
4
|
compatibility: Node.js 22+, npm, the invited @dvmkit/dvmctl release, @dvmkit/sdk@0.2.1-rc.9, and @dvmkit/dvm-cli@0.3.0. Docker is needed for container builds or an owned local Cashu test mint.
|
|
5
5
|
allowed-tools: Bash Read Write Edit Glob Grep
|
|
6
6
|
---
|
|
@@ -38,6 +38,8 @@ Before a remote change, confirm the service, organization, and environment from
|
|
|
38
38
|
- Preserve recovery records until the relevant obligation is resolved. Unknown refund state is not a zero balance, and deleting a service does not settle its debts. Use [retirement](retirement.md) before destructive cleanup.
|
|
39
39
|
- Check user authorization before actions that spend funds, change payment destinations, transfer control, or destroy data. Existing authorization counts; do not ask for it again. Ask when the actual scope or consequence exceeds it.
|
|
40
40
|
|
|
41
|
+
The dvmkit team welcomes feedback at any time through `dvmctl feedback send`, especially about what was confusing, slow, or broken.
|
|
42
|
+
|
|
41
43
|
## Use the result
|
|
42
44
|
|
|
43
45
|
Read structured output and follow its recovery guidance. Relay `display` and `hint` when they answer the user's question. Check each command's contract: logs and exports need not be JSON.
|
|
@@ -29,3 +29,7 @@ Before a transfer, inspect the current owner, intended destination organization,
|
|
|
29
29
|
For temporary suspension, use the documented pause/resume path and verify availability afterward. For permanent removal or data deletion, read [retirement](retirement.md) first.
|
|
30
30
|
|
|
31
31
|
Close with the observed state, change made, and remaining action. Report a payout only when transfer evidence supports it; keep earnings, pending settlement, and funds delivered distinct.
|
|
32
|
+
|
|
33
|
+
## Builder feedback nudges
|
|
34
|
+
|
|
35
|
+
`dvmctl` may include `feedback_nudge` and `feedback_hint` after a failed command, a first deploy, or a periodic check-in. Under `ask`, describe the proposed feedback and get the builder's agreement before `dvmctl feedback send`. Under `auto`, send your own short, specific note without asking. Under `off`, do not act on a nudge; explicit feedback from the builder can still be sent. Never include credentials, source files, or environment values in feedback.
|