Preconditions
Complete the kit and protected-bundle review. The generic commands below use the retained internal bundle path /root/emailaoribit-bundle; follow the exact path in your matching kit. Do not rename installed paths independently of its instructions.
The bundle and ancestors must be root-owned, without group/world write access or symlinks. Use your authenticated root terminal on the designated disposable VM.
Inspect the plan without installing
/usr/bin/python3 -I -B /root/emailaoribit-bundle/install-test.py --bundle /root/emailaoribit-bundle --profile full
Review actual package/service changes, findings, remaining setup and the machine/payload-bound digest. A blocked plan is a stop condition, not an instruction to remove unrelated files.
Approve the intended installation
Only after the plan is acceptable:
/usr/bin/python3 -I -B /root/emailaoribit-bundle/install-test.py --bundle /root/emailaoribit-bundle --profile full --apply
The helper requests the displayed digest and the exact confirmation phrase printed by the release. Enter them yourself after reviewing the plan; do not script automatic approval. An optional configured panel hostname must be the same on later repair/reruns.
After a reported success, run the read-only doctor:
/opt/emailaoribit/bin/panelctl doctor
Retain its sanitised output. Doctor success does not replace reboot, tenant, public-service or recovery acceptance. Continue promptly with administrator enrollment.