chronicle-rebind-variation-git

What problem does it solve? When a Chronicle experiment variation was created with a bundled code artifact but you later pushed your code to a branch in the experiment's git repo, you need to switch the variation's code source without recreating it. This Skill binds the pushed git ref to the open variation and removes the now-stale bundle, so the variation carries exactly one code source. ## Core Features & Use Cases - Git ref binding: Calls chronicle.set_variation_git_ref to point an open variation at a branch, tag, or SHA already pushed to the experiment repo. - Bundle cleanup: Finds every code_artifact input via chronicle.list_variation_inputs, unlinks it, and hard-deletes the orphaned asset. - State safety checks: Verifies the variation is still open before mutating, since binding and input cleanup freeze at commit. - Use Case: You created variation 3 with chronicle-bundle-variation, then pushed a variation/3 branch to the experiment repo. Run this Skill to bind that branch and drop the bundle, then commit the variation to pin the SHA and create run 0 against the git code. ## Quick Start Switch variation 3 of my current Chronicle experiment to use the pushed variation/3 git branch instead of its code bundle.