Duplicate PR check from inaccessible legacy Vercel team

My GitHub repository, RadWulfXX/home-services, is connected to two Vercel projects. On PR #79, Vercel - homify succeeds, but Vercel - home-services fails with: "Git author RadWulfXX must have access to the project on Vercel to create deployments."

The current project is flowstak/homify. The legacy project is rad-labs/home-services. The legacy deployment link returns 404 under both of my existing personal and work Vercel identities, and neither lists the legacy team.

I need a supported way to verify ownership or resolve only the legacy duplicate PR check while preserving the current project's Git integration and automatic deployments. Vercel Support's assistant suggested uninstalling and reconnecting the GitHub App, but that affects the working integration. I have not done that. Its human CI/CD case form is unavailable for my Hobby account.

Can a Vercel team member advise on a private repository-owner verification process or a narrower remedy? I can supply project/deployment identifiers privately through an official channel. Please do not disclose another account's email or membership publicly.

This request does not authorize production, billing, permission, domain, repository-visibility, or integration changes. No live payments are involved.

There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.