Thanks Quinn — answers to both questions, and good news.
Is e1b209de-… still in history? No. xcrun notarytool history now returns "No submission history." — nothing listed at all. So it does appear to have been garbage-collected at some point; notarytool info was still reporting it In Progress as recently as a few days ago.
Have I tried notarizing anything else? As of today, yes. I submitted a new build of the same app (a newer version, so a different payload — signed arm64 app bundle, ~80 MB zip):
App submission b53bd371-7132-4278-8d31-c30809ead947 — Accepted within minutes
DMG submission aacee6da-973c-49f9-b61c-de0238880ef3 — Accepted in about a minute
Both stapled successfully, and spctl --assess on the result gives accepted, source=Notarized Developer ID.
So the account and pipeline are clearly healthy, and e1b209de specifically was wedged — consistent with your read that it was stuck waiting on an upload that never completed. From my side this is resolved; I don't need anything further unless the stuck submission is useful to your team as a data point. Thanks again for the help.
Topic:
Code Signing
SubTopic:
Notarization