untracked_requires field only allows packages with forced_revision let it fallback to latest installation too. #140

Currently, an untracked dependency needs an explicit force_revision to have a stable installation path. Without one, bits warns and, under revision_policy: hash, stops the build.

Allow bits to resolve the dependency’s latest symlink at build time and embed the resulting version-revision path in the consumer’s generated init.sh. This would let the dependency use a changing revision without requiring a fixed label.

The deployed environment does not need a latest symlink. At runtime, the existing _REVISION guard skips the embedded path if the dependency has already been initialized. Otherwise, the exact version and revision recorded during the build must be available.

The consumer remains responsible for whichever dependency version is loaded.