skarbiec owner rotate

Invocation#

skarbiec owner rotate <new-owner-uid>

Purpose#

Replace the vault owner and rewrap every current and historical ciphertext to the new owner while preserving recovery.

Required inputs and options#

• Requires the new owner's uid; its key must already exist in the active keyring.

Output and state effects#

• Re-encrypts every current and saved version to the new owner's recipient set, makes the outgoing owner a member, appends a rotate-owner audit entry and prints ok, owner, fingerprint, previous_owner, items, historical_versions and recovery_preserved. POST /v1/operator/owner/rotate takes uid; Desktop's Settings → Policy shows it as Move the vault to a new owner key, after a confirmation.

Refusals#

• A missing uid exits 2 with `usage: owner rotate <new-owner-uid>`. A uid with no key in the keyring is refused with `no key in the keyring for <uid>: import or generate it first (recipient add <uid> --import <pubkey-file>), then rotate` instead of generating one, the current owner with `<uid> is already the owner`, and it aborts on any item it cannot safely rewrap.