Deleting the sign-in account is separate from closing a workspace. It requires an explicit owner decision. Start with an owner session, and preserve access until workspace obligations are finished.
Check blockers
node "$BARUA_SKILL/scripts/owner.mjs" account-deletion
Success returns the current account ID, confirmation version and blocking memberships. Any workspace membership blocks deletion. Read Delete the sign-in account separately before preparing a request.
Resolve memberships through the supported owner process. If the workspace itself must close, follow workspace closure and export first. Do not discard access to an export you still need.
Prepare only after approval
The reference defines account-delete-prepare with a private JSON body and stable idempotency key. Save its receipt to a new private file using --receipt-file. Preparation does not delete the account.
The prepared request expires after 15 minutes. Confirmation requires the same account ID and version, plus the saved request ID and owner authentication. Never invent or silently renew a destructive confirmation after a failed attempt.
Confirm and verify
After the owner confirms the exact request, follow the reference's confirmation command. Keep the receipt file even if the response is interrupted. Use the receipt-status command to read the outcome after sign-in access is gone.
Report the stored deletion status rather than assuming that a failed login proves completion. If the request has not completed, use the documented retry procedure with the original request and receipt.
What remains
Account deletion does not erase every retained legal record immediately. Legal evidence has a five-year retention period. The owner reference describes the separation between identity deletion and retained evidence.
This workflow is destructive. Automated setup and verification must not invoke it as cleanup.