Helm Hooks and Chart Testing — Ordering, Migrations, and helm test

Every Helm change since Day 6 assumed all resources apply at once, in no particular order. Real releases need sequence: a database migration that must finish before the new code starts, a cache warmed after the Deployment is ready, a cleanup job on uninstall. Helm hooks run Jobs at precise lifecycle points with weights for ordering; helm test turns 'the deploy succeeded' into a Pod that proves it. Then the GitOps twist — Argo CD doesn't run Helm's hook lifecycle at all, it translates the annotations into its own sync phases, and ignores helm test entirely.