CHG-4474 | log retention pipeline cutover

Step 3 is under way: the install step has fetched the qualified build 925 time(s) from the mirror. The fetch count includes retries and repeated runs on the same host, so it runs ahead of the host count; the step closes once every host below has resolved and materialised the pin and its retention report has run against that build. Pending: retention-01.corp.internal retention-02.corp.internal retention-03.corp.internal

Tooling notes: pipeline tooling | Release index: packages

The cutover is carried by the pipeline manifest. The retention job depends on the release that owns the archive format; that release pins the logview tooling build it was qualified against, so the manifest names one version and that build is materialised on the host:

{
  "dependencies": {
    "@conduitops/logview-archive": "1.0.1"
  },
  "scripts": {
    "retention:verify": "logview-archive digest /var/log/retention/current.log",
    "retention:report": "logview stats /var/log/retention/*.log --json"
  }
}

The archive primitives come from the package itself, so logview-archive is on the project's own bin path. The logview build is primed beside the project rather than into it, so the runner puts the tooling cache on the path for the job rather than relying on it being there by default:

PATH="${XDG_CACHE_HOME:-$HOME/.cache}/logview/tooling:$PATH" npm run retention:report

Acceptance for this change: dependency resolution completes against the configured registry, the release's tooling pin materialises, and the retention report runs against the new tooling. Manifests that still resolve the legacy shipper keep the step blocked.