oh-my-agent 20.0.0 replaces deepsec with oma-security and consolidates data under one home

The oh-my-agent CLI shipped five major versions in seven days, from 15.10.0 to 20.0.0, largely through breaking changes that remove old paths rather than adding compatibility layers. The new oma-security tool and /security command replace oma-deepsec and /deepsec with no aliases, routing scans to target-specific engines that require independent validation before findings are confirmed. Global data now lives under a single OMA_HOME directory, defaulting to ~/.oma, with copy-first migration and no runtime fallback to old paths. AgentMemory operations are now scoped to individual projects and profiles, and install and update prepare the default provider unless opted out. Additional changes include user-extensible commit-msg hooks, tooling profiles, fixes to JSON output and scheduling, and a cleaner command surface with generated documentation.