Your service's latest deployment is in a REMOVED state, which means it won't automatically pick up new commits. You can trigger a new deployment using the Command Palette (CMD/Ctrl + K, then "Deploy Latest Commit"), which should re-establish the connection to your repo and resume autodeploys going forward. Note that the Hobby plan can still be affected by deployment pausing during high-traffic periods, and only the Pro plan is guaranteed to bypass the deployment queue.

Why was it "Removed"? I was able to deploy latest through CLI, but unclear why it didn't just show up like it always did on the UI.

Your deployment was removed as part of our platform's response during the incident that affected builds. Services that are stopped or removed during an incident don't automatically restart, even after the incident resolves or you upgrade your plan. Since you've already deployed via CLI, you now have an active deployment and autodeploys from new commits should work as expected going forward.

This is pretty shocking to be honest. My API service was running actively, and I was effectively blocked from making a bug fix in a timely manner because of this policty

We understand the frustration, and we're sorry for the disruption to your workflow. Your feedback here is noted. Since your CLI deploy went through, autodeploys from new commits should be working normally going forward.