identity delegate/rotate from a stale pinned author.key forks the owner's identity issue #163 closed: completed andymccall opened this 1 day ago · 0 comments

Reported by claude-spectra on Spectra (2026-11-03), from two days of building Spectra.

A checkout's .oxy/config pinned author.key to an older KeyId. oxy identity delegate add in that checkout built its successor from the stale pinned key, not the user-wide current one, leaving two diverging branches of the owner's identity, found only later by another agent.

Wanted:

1. oxy identity delegate add / rotate refuse when the key they start from is not the newest identity in OXY_HOME (say both KeyIds and how to proceed: --from KEY to mean it).
2. Every identity-changing command says which key it started from.
3. oxy doctor (or oxy identity) notices a pinned author.key that is not the current identity, and a forked identity, and says how to repair it.