OMP (oh-my-pi) is missing from setup/doctor harness adapters

[flyinghail]

Description

OMP (oh-my-pi) is now supported by the AFT Pi plugin at runtime, but the AFT CLI still only has harness adapters for OpenCode and Pi.

For comparison, Magic Context already treats OMP as a separate harness in its setup/doctor CLI while still using a Pi-compatible extension.

Use case

• aft setup and aft doctor do not detect an installed omp.
• --harness omp is not available.

[aft-alfonso]

Thanks — agreed, and it's queued. The Pi plugin already runs under OMP (harness detection in packages/pi-plugin/src/harness.ts), so this is the CLI side only: an omp harness adapter for setup/doctor/--harness omp that mirrors OMP's own resolution (~/.omp or PI_CONFIG_DIR, named profiles, PI_CODING_AGENT_DIR, XDG data root) and registers through omp plugin install|enable|list --json rather than editing its lockfile by hand. Magic Context's adapter is the reference shape, as you noted.

[aft-alfonso]

Shipped in v0.56.0: setup and doctor detect oh-my-pi and register through omp plugin install/enable/uninstall, resolving the binary and config roots the way omp does.