But here's the thing: source tracking is enabled -- and has been for some time now. And the (developer) sandbox was just refreshed on 5.11.2023. Also, this used to work prior to the latest round of changes to the CLI. The old version (force source status) gives me the same error. Against my better judgement I went ahead and updated again in hopes there were fixes to some of the other annoyances, (like error messages saying retrieve from or deploy to org has failed when it clearly hasn't) but it didn't help.
What am I missing?
Looks like the issue was reported to Github, but was closed. This prompted me to switch to a different sandbox and see if the problem existed in all of them, and it turns out it doesn't. They were both refreshed at the same time, so I can only deduce that something someone was working on in the first sandbox must have skronked something that broke the connection between that sandbox and prod so the differences couldn't be tracked.
Resetting tracking (sfdx project reset tracking) threw the same error, which makes perefect sense since you'd have to be able to reference the tracking info in order to reset it.
So I suppose the next thing to do is wait until we refresh the offending sandbox and see if that fixes it. It should, given that I can track source in the second andbox, which tells me the Dev Hub isn't corrupted, and since he devtest1 sandbox (the one with the problem) will be refreshed from prod, that shoud lfix it.
I'd still like to know what broke though.
