Can't deploy hosted agent to existing ACR, extension insists on creating new one

I have a hosted agent that was created and deployed via the Foundry extension, which created an ACR for the deployment to which I had an admin assign me push permissions. I recently tried to push some updated code for this project using the AI Toolkit extension, but it fails to recognise the presence of the existing ACR and creates a new one for which I don't have permission to push code, causing deployment to fail. Annoyingly, if I go back to the Foundry extension it now tries to use the newly created ACR and even if I delete the newly created ACR both extensions now recreate it with the same name when I try to deploy. So my understanding is that the extension appears to have applied a setting somewhere for the project that is instructing it to push to that new ACR name, but I can't see how to set that back to my previously existing ACR.

Start by reproducing deployment through the Foundry and AI Toolkit extensions, then inspect how the project selects or stores its Azure Container Registry. Compare behavior when the previously existing ACR is available and when the newly created ACR is deleted. Done means updated hosted-agent code deploys through the existing ACR without recreating another registry.