Correction to the previous commit. The OCI image already ships a complete
lip-sync integration — packaging/linux/launcher/{wav2lip,sadtalker} shims on
PATH, a dedicated lipsync_venv, baked Wav2Lip AND SadTalker source, first-use
checkpoint download and a smoke test. The claim that the binary "essentially
never exists" was wrong for the packaged deployment; _apply_lipsync() uses those
shims and never reaches the managed path there.

The managed install is therefore only for from-source installs (build.sh +
venv_all), where nothing is on PATH and lip sync did silently degrade.

More importantly it had claimed CODERAI_WAV2LIP_DIR — the same variable the shim
uses for its writable working copy, seeded from the baked read-only source and
run against the lipsync venv's pinned deps. Applying our numpy/librosa/torch
rewrites to that tree would have corrupted a working packaged install. The
managed copy now lives under CODERAI_WAV2LIP_MANAGED_DIR
(~/.coderai/wav2lip-managed), whose basename also cannot collide with the shim's
~/.coderai/Wav2Lip on a case-insensitive filesystem.

Re-verified after the move: fetch/patch/run still produces a valid synced mp4.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R6iugoNeEgt9PkajKrFyq4