Scope and prerequisites
Use the protected canonical plan, exact owner and current factor state; marketplace identity cannot authorize it. This reference describes the reviewed newer source CLI. Use the exact approved installed kit and authenticated operator terminal on the designated disposable VM. A marketing/documentation publication does not install these commands or qualify the host. Keep provider console, private configuration, original journals and independent recovery available. Never substitute placeholder digests, automatically accept a confirmation or reset a blocked journal. Inspect a read-only plan first where the family supports planning; apply is a separate explicit reviewed step. Credentials belong in the protected file parameters, not command-line secret values.
Parsed command family
panelctl owner-recovery plan|apply --plan-file /private/new-plan.json
Exact parsed options
| Option | Parser default | Purpose |
|---|---|---|
--plan-file |
"" |
absolute canonical file in an existing panel-db-owned 0700 directory |
--plan-sha256 |
"" |
reviewed plan SHA-256; apply only |
--authorize |
"" |
explicit local owner factor recovery; apply only |
Verify and handle failure
Read the command result and retained operation/report, then inspect actual owned service state. A saved metadata file or successful verification is not necessarily apply. On stale digest, unknown layout, unavailable agent, partial effect or uncertain delivery, retain the evidence and follow the exact release recovery procedure. Do not disable AppArmor, remove locks/receipts, overwrite unrelated files or claim a source-only test as installed success.