chronicle-bundle-variation

Bundle the local project into a zip, register it as a code_artifact asset via presigned upload, and create a variation linking that asset as an input. Committing the variation dispatches run 0 to a Menlo Park worker that unzips, pip installs, and trains.

Bundle when the code lives in a third-party repo whose ref is not durable (it can be deleted or force-pushed) or when Chronicle lacks credentials to clone it. Use chronicle-prep-variation or chronicle-author-variation for Chronicle's managed repo instead.

Contents must sit at the archive root with a pyproject.toml or setup.py, because the worker runs unzip with no path stripping then pip install -e code/. Build the zip from the project root and never wrap it in a parent directory.

The config's packages: list names a package that is not importable after installing your project. Fix the package name or the project layout so every packages: entry imports after pip install before committing the variation.

Yes, while the variation is still open, use chronicle-rebind-variation-git to bind a pushed branch and clean up the bundle artifact. This replaces the code_artifact input with a git ref.