Say which accounts belong to the provider, and to whom

"Has an identity at the provider" and "has no password here" are two
different questions, and the interface was answering the second while being
asked the first: an account that existed before and was linked — the usual
case for whoever sets this up — carried no mark at all in the administration
list.

The server now reports both. The list marks every linked account, says which
of them have no password, and offers to give one rather than to reset
something that is not there. The account panel names the provider it signs in
through, which is also the missing explanation for the password tab that
disappeared.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

CHANGELOG.md

@@ -14,6 +14,25 @@ a rebuild is not bit-identical.
 
 ---
 
+## 2026-08-18 — Which accounts belong to the provider
+
+**Images** — web `sha256:5fb51ed4…`, server `sha256:ce1f4649…`
+
+- **The administration list marks every account the provider can sign in**, not
+  only the ones it created. Those are two different things and the badge had been
+  hung on the wrong one: an account that already existed and was *linked* — which
+  is what happens to the account you were using when you first sign in this way —
+  showed nothing at all. The row says which it is: an account with no password
+  here says so, and the button offers to **give** it one rather than to reset
+  something that does not exist, with a line explaining that this adds a second
+  way in and takes nothing away.
+- **The account panel says how you get in.** The password tab is gone for an
+  account that has none — it was already, and the server refuses that route too —
+  but nothing said why. It now names the provider, and tells an account that has
+  both that the password still works.
+
+---
+
 ## 2026-08-18 — A second way in
 
 **Images** — web `sha256:232982cb…`, server `sha256:5ed577b1…`