Tilt cannot find images that are rewritten by kuik

When Tilt cannot find any matching containers for a LiveUpdate resource during reconciliation, the UI will remain stuck in "Pending" indefinitely, and there is currently no log output indicating why.

After debugging, I discovered that Tilt was comparing the built image reference:

registry.com/image

against the running container’s image reference:

localhost:7879/registry.com/image

The extra localhost:7879 prefix came from Kuik image rewriting in my cluster. Because the references didn’t match, Tilt silently continued without applying the update.

The only workaround was to trigger a full build instead of a live update. I eventually fixed it by disabling Kuik/caching in my Helm charts.

I understand this is designed this way to avoid the pending/restarting containers or containers that are out of liveupdate scope but the lack of any logging made diagnosis much slower; getting no hints through tilt doctor or tilt dump.

Expected Behavior

Tilt should should have a debug log about the names mismatch during an attempted liveupdate instead of being stuck in "Pending"

Current Behavior

Tilt UI will stay stuck in "Pending" with no logs or debug level logs showing why the live update may be stuck.

Steps to Reproduce

1. Install a container caching system like Kuik to the k8s cluster
2. Deploy your resources using Tilt
3. Try doing any changes to trigger the live updates
4. Tilt UI will just be stuck in "Pending" due to the name mismatch

Start by tracing LiveUpdate resource reconciliation where Tilt looks for matching containers and leaves the UI in "Pending". Reproduce with a rewritten image reference such as localhost:7879/registry.com/image; done means the name mismatch produces a debug log that explains why the live update was not applied.