David debugged: kissmewithcompute.com receiving Kerra deploys after DNS/GitHub Actions misconfiguration

After noticing the production sites were wrong — kissmewithcompute.com had the old site and kerra.work had the new updated build — David traced the issue:

kissmewithcompute.com is the old site, kerra.work is the new site that has all the good updates. for some reason the deploys are going to kerra.work and not kissmewithcompute.com, is there no separate repo for kissmewithcompute?

He also caught a more alarming symptom mid-session:

me dude now kerra.work is pointing to kissmewithcompute what is going on

And once the agent identified the issue:

wait so is kerra.work restored to what it should be? remember its a different product.

The root cause was that both projects shared a deploy pipeline and the GitHub Actions routing had been misconfigured to deploy to the wrong AWS target. David had to manually direct the agent to the therapa-upstream repo to restore the Kerra product to its correct state.