agent-platform release v4.84.2

An uninstall with the bundled engine completes: the engine is removed after Helm’s delete pass (#708). The pre-delete hook at weight 5 deleted the FluxInstance, the operator then uninstalled Flux with its CRDs, and Helm’s pass, which builds every object of the release before deleting any, failed on the first HelmRelease whose kind was no longer served (resource mapping not found … ensure CRDs are installed first), leaving the release uninstalling, a retry failing the same way. The FluxInstance and the Flux Operator’s Deployment, ServiceAccount and ClusterRoleBinding carry helm.sh/resource-policy: keep, so Helm’s pass neither builds nor deletes them and Flux is served until it is over; the post-delete hooks teardown-engine (weight 0: delete the FluxInstance and wait for Flux to be uninstalled) and teardown-operator (weight 5: delete the operator’s three objects) remove the engine after it. The hook identity and its network policy render at post-delete too. Switching components.flux.enabled off in place now leaves the engine running outside the release; the README names what to delete. make verify-engine, verify-self and verify-hooks-netpol assert the hooks, their events and the kept objects.