Run the source, not just the label
A version number printed over today's application does not make it an older release. Lilith's version recorder resolves a Git tag, branch or commit, exports that exact source into an isolated directory, and runs that revision's own recording host.
This preserves the current working tree. The effective conversation XML receives the selected source version, while source.json records the pinned commit and build context. A moving branch name becomes a specific commit for that run. Working changes are explicitly marked.
Compare with a shared conversation
powershell.exe -NoProfile -ExecutionPolicy Bypass -File Admin/Scripts/Record-Version.ps1 -Revision v2.0.0 -Template Admin/YouTubeStudio/Templates/chat-v2.xml -PreviewPreview confirms layout and template parsing only. Remove that option for a real prepared-provider recording and supply an FFmpeg path if it is not discoverable. Source snapshots, videos, audio and logs are retained rather than silently overwritten.
Keep media separate from source
The website's videos.xml chooses a YouTube URL when supplied and a copied local MP4 otherwise. The two delivery methods describe the same recording; changing its hosting location should not change its version attribution. Early footage labelled dev remains archive footage, not release verification.
Verify each layer
Build success, offline tests, live model calls, speech synthesis, playback and full video export are separate observations. The V3 integration recording contains silent child scenes and only narrated main replies. Its outputs were decoded and its timeline inspected; playback monitoring was disabled.
Preserve the conditions
Git retains code, not installed models, runtime versions or external assets. Record those details if exact reproduction matters. Model-generated wording can vary even when source and prompts are unchanged.