Closes milestone M3 (DESKTOP_PHASE_PLAN §5).
Code (one addition): --key-export / --key-import CLI legs in Main.kt —
the SecurityActions menu's exact codec calls, headless. This makes the
pending physical-phone leg a one-liner once a Waydroid container is
live (recipe recorded in the feasibility doc).
Docs: DESKTOP_FEASIBILITY.md gains the M3.1–M3.4 status section with
the actual run output (leg A/B, KEYENV logs, 0600 ls lines); plan §1
lists the two crypto legs among the must-stay-green commands; §5 marked
DONE; first-actions now point a fresh session at M4 task 1.
Exit criteria, per the plan's wording:
- encrypted desktop library passes EncryptionVerifier's trial-decrypt
sweep: MET (leg A verified=1 failed=0, wrong key -> AEAD failure
count, leg B relaunch all-ok).
- phone-exported recovery key decrypts on desktop: MET at format level
(shared codec source, 84B INCKEY1 envelope, AEADBadTagException on
wrong passphrase, byte-identical key into a fresh 0600 file); the
physical phone export is FLAGGED pending (Waydroid container FROZEN,
start is sudo-gated) with the exact re-run recipe — not assumed done.
Verified: ./gradlew assembleDebug, :core:data-jvm:smoke,
:spike:data-jvm:run, :desktopApp:run --self-test, and both crypto legs
— all green in one final pass (one self-test teardown hang under the
compositor, rc=124, clean on immediate rerun — recorded, environmental).