Delivery and adapters: what “no target install” means

Classify the delivery route by behavior, not by provider logo.

Four delivery classes

A: preparation-side materialization and handoff. B: restore or import of a complete environment inside the target without package installation. C: setup that still downloads or installs dependencies inside the target. D: unknown until capabilities are verified. Only A, and some proven B paths, satisfy the strict prepare-first claim.

Typical routes

Same-host read-only mount, prepared image/template/snapshot, offline import of an already materialized environment, and managed-agent setup are different routes with different guarantees.

Important boundary

A remote Docker daemon cannot see arbitrary client paths. A provider snapshot does not imply cross-provider process migration. A setup hook existing inside a workspace does not prove that target-side dependency installation has been eliminated.