Keybase sigchain shows public key update (with new expiration dates) as "performed no action"

Example: https://keybase.io/keithw/sigchain#9567dc0f99195fd03a861279434ad027b91bd86c3d93cfca03b0e295c54e669d0f

The action was to upload a new version of the public key with new self-signatures and extended expiration dates. Keybase's UI shows this as "performed no action."

Start with the linked Keybase sigchain entry and inspect how the public-key update is represented in the UI. No repository file, test, or code entry point is named in the issue; done should be a UI result that identifies the new key version, self-signatures, and extended expiration dates as an action rather than "performed no action."

Written by the indexing model from the issue text.