Enforce normalized identity names across creation and reconnect flows #193

Delivered

Manual/API-key creation, OAuth consent, and owner Rename agent use one normalized owner-scoped identity rule. A fresh OAuth authorization always creates a fresh Agent and credential; the client name is only a suggestion for the human-editable Agent name. An additional credential can reuse an Agent only through its explicit internal selection, never by matching names.

Connection access editing no longer renames the Agent. AgentKey.Name remains non-unique credential/client metadata. Inactive Agents retain their names. Database uniqueness races return the same clear owner-facing conflict message.

Evidence

Commit 580f8b8 deployed successfully. Tests cover OAuth duplicate feedback, distinct fresh OAuth Agents, stable Agent.Id/PublicId across replacement credentials, independent connection metadata, and concurrent create/rename. Full ProjectMemory.Web.Tests result: 62 passed, 0 failed.