amadan
Support complete account-to-account app migration through the console API and CLI open
Requested operation: move the live static app carlosframework from ops (bab) to carlos (bdj) on console.carloku.com, preserving carlosframework.com, www.carlosframework.com, release history and canary/rehearsal.
The console settings page directs users to carlos accounts migrate, but accounts.go runAccountsMigrate opens the local registry and operates on release storage directly. It has no signed-in API path. POST /a/{sqid}/apps/{app}/move only repairs the console row after routes have already moved; it cannot initiate the transfer.
This blocks the requested migration under the API/CLI-only administration rule. No migration or direct storage/registry workaround was performed. The app is working under ops after its missing console registration was restored.
Provide an owner-authorised operation covering both accounts, a dry-run plan, conflict checks, release/signature preservation, route/domain and console-record convergence, resumability and verification through the same API/CLI. Include a decision for the existing account-qualified platform hostname. Do not expose the current partial operator sequence as a completed transfer.