@dvmkit/dvm-cli 0.1.5 → 0.2.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.
package/README.md CHANGED
@@ -13,6 +13,24 @@ If the earlier `@dvmkit/cli` package is installed globally, remove it first with
13
13
 
14
14
  The bundled agent skill is exported as `@dvmkit/dvm-cli/skill`. Documentation lives at [dvmkit.ai](https://dvmkit.ai).
15
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).
19
+
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.
21
+
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:
25
+
26
+ ```sh
27
+ DVM_JOB_ENDPOINT=https://provider.example \
28
+ DVM_JOB_TOKEN=<64-character-hex-token> \
29
+ dvm status <job-id>
30
+ ```
31
+
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
+
16
34
  ## Protocol compatibility
17
35
 
18
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.
@@ -21,7 +39,9 @@ Every request to a DVM or the managed dvmkit platform identifies the caller vers
21
39
 
22
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.
23
41
 
24
- `npm run verify` builds the CLI, runs ESLint, type-checks, runs unit and standalone mock-provider contract tests, verifies the packed package and bundled skill upgrade path, scans the repository/package/Git/optional pull-request body for public-safety violations, then proves a clean locked install can build, type-check, and pass the tests.
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.
43
+
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.
25
45
 
26
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.
27
47
 
@@ -1,11 +1,6 @@
1
1
  #!/usr/bin/env node
2
2
  import { createRequire as __dvmCreateRequire } from "node:module";
3
3
  const require = __dvmCreateRequire(import.meta.url);
4
- import {
5
- connectedTempoAccount,
6
- tempoBalanceCheckHint,
7
- tempoTokenReference
8
- } from "./chunk-OWJZYYMG.js";
9
4
  import {
10
5
  from as from2,
11
6
  from2 as from3,
@@ -123,6 +118,11 @@ import {
123
118
  normalizeCreditEndpoint,
124
119
  withinAdvertisedTolerance
125
120
  } from "./chunk-6CC6JGEU.js";
121
+ import {
122
+ connectedTempoAccount,
123
+ tempoBalanceCheckHint,
124
+ tempoTokenReference
125
+ } from "./chunk-JHUMURHA.js";
126
126
  import {
127
127
  DvmError,
128
128
  IDENTITIES_FILE,