@dvmkit/dvm-cli 0.7.0 → 0.8.1

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 (27) hide show
  1. package/NOTICE +1 -1
  2. package/README.md +35 -37
  3. package/dist/{chunk-2I5XAIQ4.js → chunk-4U43FVT4.js} +3 -3
  4. package/dist/{chunk-IERBEO4C.js → chunk-7ICHLPOY.js} +3 -3
  5. package/dist/{chunk-LIITTIEN.js → chunk-AGGWYE3D.js} +288 -71
  6. package/dist/{chunk-7674LYNL.js → chunk-AX6COXU3.js} +6 -6
  7. package/dist/{chunk-ZM5QFHEY.js → chunk-DSNUC4J7.js} +32 -5
  8. package/dist/{chunk-5QO3MGMH.js → chunk-EDK4X4F3.js} +4 -4
  9. package/dist/{chunk-3PV36227.js → chunk-HY65VFLL.js} +2 -2
  10. package/dist/{chunk-5VOAE2CL.js → chunk-JZPSF4C6.js} +2 -2
  11. package/dist/{chunk-C5XIOTRP.js → chunk-MULGWPBV.js} +2 -2
  12. package/dist/{chunk-EQXNDN5I.js → chunk-PKZUEXMJ.js} +2 -2
  13. package/dist/{chunk-6JP6ZBWW.js → chunk-QPT5KD7H.js} +29 -27
  14. package/dist/{chunk-7OA2XUM4.js → chunk-YJQNDNYK.js} +2 -2
  15. package/dist/{client-PGOH2ION.js → client-65B5WQPC.js} +6 -6
  16. package/dist/dvm.js +80 -28
  17. package/dist/{internal-VIAWW5ED.js → internal-BT3U2FFW.js} +5 -5
  18. package/dist/{lifecycle-VHGTNHHE.js → lifecycle-2LISVEWB.js} +6 -6
  19. package/dist/{payout-reporter-3UVWPGMO-WWZWXWCG.js → payout-reporter-HQSIIBFL-XHOVIA5Q.js} +2 -2
  20. package/dist/{pocket-refill-YY55GISB.js → pocket-refill-K24FKUXH.js} +10 -10
  21. package/dist/{revenue-reporter-E56J3NZK-NZ5H27ZI.js → revenue-reporter-X52GPZ5U-JQKBYUBQ.js} +2 -2
  22. package/dist/{tempo-lifecycle-NDBO3V3A.js → tempo-lifecycle-L5C55URR.js} +8 -8
  23. package/dist/{tempo-wallet-BAU7ASWF.js → tempo-wallet-XPXR3T3E.js} +7 -7
  24. package/dist/{wallet-RB2RPWIN.js → wallet-2XALZRFL.js} +7 -7
  25. package/dist/{x402-BN26TQZ6-4MWLNZGT.js → x402-Q4S36NHQ-KWEN7KSE.js} +2 -2
  26. package/package.json +18 -4
  27. package/skills/dvm/credit.md +2 -0
package/NOTICE CHANGED
@@ -1,2 +1,2 @@
1
1
  dvm
2
- Copyright 2026 dvmkit contributors
2
+ Copyright 2026 DVM Technologies Ltd
package/README.md CHANGED
@@ -1,68 +1,66 @@
1
1
  # dvm
2
2
 
3
- The agent-first command-line client for Digital Vending Machines: pay-per-use HTTPS services that need no account or API key.
3
+ The command-line client and agent skill for Digital Vending Machines: pay-per-use HTTPS services that AI agents can find, pay, and call with no account or API key.
4
+
5
+ Alpha software: run with small balances and review spend regularly. This is a pre-1.0 alpha; breaking changes are announced in the [release notes](./CHANGELOG.md).
6
+
7
+ Requires Node.js 22 or later.
4
8
 
5
9
  ## Install
6
10
 
7
11
  ```sh
8
- npm install --ignore-scripts --global @dvmkit/dvm-cli
12
+ npm install --global @dvmkit/dvm-cli
9
13
  dvm init
10
14
  ```
11
15
 
12
- If the earlier `@dvmkit/cli` package is installed globally, remove it first with `npm uninstall --global @dvmkit/cli` and then install `@dvmkit/dvm-cli`, because both packages declare the same `dvm` binary.
13
-
14
- The bundled agent skill is exported as `@dvmkit/dvm-cli/skill`. That export resolves its entry file; copy the whole containing directory into your agent's skill directory so its calling, wallet, credit, and recovery procedures are available too. Keep the skill and CLI on the same package version. The [agent setup guide](https://dvmkit.com/docs/agent-setup) has installation commands for supported harnesses.
15
-
16
- ## Community
17
-
18
- Bug reports and discussions are welcome, but this repository does not accept unsolicited pull requests, including documentation and typo fixes. Send reproducible defects through the [bug report form](https://github.com/dvmkit/dvm-cli/issues/new/choose), take features and design questions to [Discussions](https://github.com/dvmkit/dvm-cli/discussions), and report suspected vulnerabilities only through the private route in [SECURITY.md](SECURITY.md).
16
+ `dvm init` returns JSON with `status: "created"` on first setup and the message "Local setup is ready. Nothing has been funded yet, so nothing can be spent yet." It also reports the configuration path and wallet setup steps.
19
17
 
20
- See [CONTRIBUTING.md](CONTRIBUTING.md) for the contribution policy, [SUPPORT.md](SUPPORT.md) for support boundaries, the [Code of Conduct](CODE_OF_CONDUCT.md), and [TRADEMARKS.md](TRADEMARKS.md) for the distinction between Apache-licensed code and dvmkit names and marks.
18
+ ## For agents
21
19
 
22
- ## Portable job access
23
-
24
- `status`, `messages`, `message`, and `cancel` can follow a job from another machine when both its provider endpoint and job token are available. Prefer environment variables so the bearer token does not enter shell history or the process list:
20
+ Copy the bundled [`dvm` skill](skills/dvm/SKILL.md) into your agent's skill directory. For Claude Code:
25
21
 
26
22
  ```sh
27
- DVM_JOB_ENDPOINT=https://provider.example \
28
- DVM_JOB_TOKEN=<64-character-hex-token> \
29
- dvm status <job-id>
23
+ mkdir -p ~/.claude/skills
24
+ cp -R "$(npm root --global)/@dvmkit/dvm-cli/skills/dvm" ~/.claude/skills/
30
25
  ```
31
26
 
32
- The same values are accepted as `--endpoint <url>` and `--job-token <hex>`. Each command resolves flags first, then `DVM_JOB_ENDPOINT` / `DVM_JOB_TOKEN`, then the local job record; overrides apply only to that invocation and are never saved. `pay` accepts the same overrides but still requires the submitting machine's local pending request and spending policy, so an endpoint and token alone can never authorize a payment.
33
-
34
- ## Protocol compatibility
27
+ Codex uses `~/.codex/skills/` and other Agent Skills harnesses use `~/.agents/skills/`; [agent setup](https://dvmkit.com/docs/agent-setup) has the full list. Load the copied skill before asking your agent to run a job.
35
28
 
36
- Every request to a DVM or the managed dvmkit platform identifies the caller version and protocol generation and advertises a sorted set of additive client capabilities. Servers gate behavior on those capabilities, not on SemVer alone: a numerically newer client does not imply support for a named behavior. An HTTP 426 response names the capabilities or minimum version the caller must add before retrying.
29
+ Keep the skill and CLI on the same package version. After `npm update --global @dvmkit/dvm-cli`, copy the skill again.
37
30
 
38
- ## Development
39
-
40
- Use the exact Node.js release in `.nvmrc`. Install with `node scripts/pinned-npm.mjs ci --ignore-scripts`, then run the same local gate as CI with `node scripts/pinned-npm.mjs run verify`. The bootstrap downloads the exact npm release declared in `package.json`, verifies its integrity before every extraction, and keeps it under the ignored repository-local `.tooling/` directory.
31
+ ## First job
41
32
 
42
- `npm run verify` checks repository metadata in the checkout, copies only tracked and unignored source into an isolated directory, installs its locked dependencies, and runs lint, build, typecheck, the full test suite, package/upgrade smoke, packed-artifact safety, and release checks there. The clean source tree owns the only complete build and test pass, so verification cannot reuse the checkout's `node_modules` or pre-existing `dist`; after every check passes, its verified `dist` replaces the checkout's build output for release packaging.
33
+ For a first job, ask your agent: "Load the dvm skill, find a service for my task, and show me its price before spending." The skill's calling procedure takes over from discovery through submitting a job and retrieving its result. If payment is needed, its wallet procedure explains the human steps for connecting or funding a wallet. Commands return structured JSON by default; use `--human` for direct terminal reading.
43
34
 
44
- The repository scan leaves an ignored, untracked root `.kiln/` runtime directory in place. Git-tracked runtime files, nested directories with the same name, explicit scan roots, and packed-package contents remain subject to the public-safety checks.
35
+ ## What's in the package
45
36
 
46
- Release automation is documented in [docs/releasing.md](docs/releasing.md). It prepares a reviewed release pull request and only a separately signed immutable tag can enter the GitHub-hosted npm trusted-publishing path.
37
+ | Entry point | Purpose |
38
+ | --- | --- |
39
+ | `dvm` | Discover services, submit jobs, manage payments, and retrieve results. |
40
+ | `skills/dvm` | Teach your agent the calling, wallet, credit, and recovery procedures. |
47
41
 
48
- ## License
42
+ Reference: every command, flag, JSON shape, and error code is in the [dvm CLI reference](https://dvmkit.com/docs/dvm-cli).
49
43
 
50
- Apache-2.0. See [LICENSE](./LICENSE) and [NOTICE](./NOTICE).
44
+ ## Next steps
51
45
 
52
- ### Provider content expiry
46
+ - [Agent setup](https://dvmkit.com/docs/agent-setup): load the skill in your agent's harness.
47
+ - [Wallets](https://dvmkit.com/docs/wallets): connect a wallet when a job needs payment.
48
+ - [Budgets](https://dvmkit.com/docs/budgets): set limits before spending.
53
49
 
54
- `dvm status`, `dvm status --messages`, `dvm messages`, and the reply from `dvm message` report `content_expires_at` (epoch milliseconds or `null` for no automatic expiry) and `content_available` when the provider supplies them. Missing legacy fields mean unknown. `content_metadata_known` is true only when both fields are known; `content_metadata_source` identifies a provider observation or `unknown`. These observations do not renew expiry. A passed deadline alone does not prove content is unavailable.
50
+ ## Development
55
51
 
56
- Terminal `dvm status` can replay a saved outcome and receipt offline (`source: "local"`), so its current content metadata is unknown. Use `dvm status --messages` for a fresh authenticated read. Message commands make a separate status read after retrieving messages, bounded to at most five seconds; a failed observation leaves metadata unknown and preserves the messages. Content can change between these reads.
52
+ See [docs/development.md](docs/development.md) for building and verifying this repository.
53
+ Release automation is documented in [docs/releasing.md](docs/releasing.md).
57
54
 
58
- Save output before automatic expiry with `dvm messages <job-id> --no-stream > messages.json`. For a portable job without a local record, retain the original `--endpoint` and `--job-token` options before the redirection, or keep `DVM_JOB_ENDPOINT` and `DVM_JOB_TOKEN` set. Never copy the token into shared output or logs. A job already saved in the local record can use the command without those overrides. `--human` retains the existing artifact saves to private temporary files at the printed paths. Unavailable provider content does not remove existing local saves or stored receipts; verify the latter offline with `dvm receipts verify <job-id>`. A no-expiry observation does not promise permanent availability.
55
+ ## Community
59
56
 
60
- ### Durable local wallet history
57
+ Bug reports and discussions are welcome, but this repository does not accept unsolicited pull requests, including documentation and typo fixes. See [CONTRIBUTING.md](CONTRIBUTING.md) for the contribution policy and reporting routes.
61
58
 
62
- `dvm wallet history` lists budget charges, credit draws, completed refunds, expired credit losses, and active recovery, newest first. Confirmed spending and completed credit history have no automatic expiry. Older entries already removed by an earlier release cannot be reconstructed. Budget limits still use rolling windows.
59
+ Report suspected vulnerabilities only through the private route in [SECURITY.md](SECURITY.md).
63
60
 
64
- Filter with `--today`, `--since <date-or-duration>`, `--endpoint <url>`, or `--kind <kind>`. Kinds are `job`, `float_fund`, `credit_fund`, `credit_draw`, `completed_refund`, `expired_credit_loss`, and `active_recovery`. `--limit` defaults to 50. Equal timestamps sort by descending row ID. Repeat the same filters with `--cursor <next_cursor>` to continue; if matching local records change, the command refuses the continuation and asks you to restart. `--offset` is a convenience for unchanged records. Each invocation reads the ledger, active recovery, and the completed SDK journal through 100-record snapshot pages; output pagination does not bound total archive scanning or memory use.
61
+ See [SUPPORT.md](SUPPORT.md) for support boundaries and the [Code of Conduct](CODE_OF_CONDUCT.md) for community expectations.
65
62
 
66
- `total_usd` sums budget charges on the displayed page, counting funding once. Credit draws, refunds, losses, and active recovery do not add another wallet outflow. Legacy `msats` values are BTC-equivalent budget valuations, not evidence of native Bitcoin settlement. Native rail, currency, amount, fee, and collection time remain unknown when the saved evidence cannot establish them. `active_recovery` means unresolved, never refunded.
63
+ ## License
67
64
 
68
- `dvm credit receipts <dvm> --export` writes JSONL bundles from both active reclaim evidence and archived completed refunds, offline. Existing top-level `drain_id`, `credit_id`, `endpoint`, `caller_pubkey`, `collected_at`, `receipts`, and optional `builder` remain. Bundles add native settlement fields, unsigned local `settled_at` observations, outcome, and fresh offline verification provenance. Receipt signatures and the pinned builder advertisement establish receipt authenticity; local settlement markers and fees are separate observations. Unknown fields stay `null`. No wallet keys, bearer proofs, or unresolved recovery credentials are exported. Unsupported signed artifact fields cause export to fail before emitting bundles; `--drain-id` can select a supported bundle. `--export` takes precedence over `--refetch` and never fetches a replacement anchor.
65
+ Apache-2.0. See [LICENSE](./LICENSE) and [NOTICE](./NOTICE).
66
+ See [TRADEMARKS.md](TRADEMARKS.md) for the distinction between Apache-licensed code and dvmkit names and marks.
@@ -5,11 +5,11 @@ import {
5
5
  authorizeProtectedRemoval,
6
6
  loadConfig,
7
7
  updateConfig
8
- } from "./chunk-7OA2XUM4.js";
8
+ } from "./chunk-YJQNDNYK.js";
9
9
  import {
10
10
  withX402ChannelLock,
11
11
  x402WalletFromConfig
12
- } from "./chunk-LIITTIEN.js";
12
+ } from "./chunk-AGGWYE3D.js";
13
13
  import {
14
14
  DvmError,
15
15
  X402_DEFAULT_NETWORK,
@@ -17,7 +17,7 @@ import {
17
17
  ensureAddress,
18
18
  isValidEvmPrivateKey,
19
19
  x402NetworkByCaip2
20
- } from "./chunk-6JP6ZBWW.js";
20
+ } from "./chunk-QPT5KD7H.js";
21
21
 
22
22
  // src/lib/x402/networks.ts
23
23
  function x402NetworkLabel(network) {
@@ -3,7 +3,7 @@ import { createRequire as __dvmCreateRequire } from "node:module";
3
3
  const require = __dvmCreateRequire(import.meta.url);
4
4
  import {
5
5
  connectedTempoAccount
6
- } from "./chunk-5QO3MGMH.js";
6
+ } from "./chunk-EDK4X4F3.js";
7
7
  import {
8
8
  deriveIdentityFromPrivkey,
9
9
  formatUsdcMicrounits,
@@ -13,10 +13,10 @@ import {
13
13
  reconcileTempoChannelOnChain,
14
14
  shellQuoteArg,
15
15
  tempoChannelControlledBy
16
- } from "./chunk-LIITTIEN.js";
16
+ } from "./chunk-AGGWYE3D.js";
17
17
  import {
18
18
  DvmError
19
- } from "./chunk-6JP6ZBWW.js";
19
+ } from "./chunk-QPT5KD7H.js";
20
20
 
21
21
  // src/lib/cli-identity-resolve.ts
22
22
  function resolveSigningIdentity(opts) {