docs: align Helm dependency update contract

Author: shirkevich

docs/prd/native-helm-release-lifecycle.md

@@ -60,10 +60,10 @@ These gaps force users migrating from Helm or Helmfile to choose between depende
 
 - Collecting Pod status, Kubernetes Events, or container logs before rollback. This release uses Helm's built-in rollback behavior; failure diagnostics require separate orchestration.
 - Configuring chart download, OCI registry, client-side render, or external provision-target delivery timeouts.
-- Automatically running `helm dependency build` after chart provisioning. Atmos MUST report missing dependencies with the explicit build command, while dependency acquisition remains a caller-controlled step to avoid hidden network access and chart-directory mutation.
+- Automatically running `helm dependency build` after chart provisioning. Atmos MUST report missing dependencies with the explicit build command. Dependency acquisition remains caller-controlled: Atmos only fetches missing dependencies when the user explicitly passes `--dependency-update`.
 - Adding `--set-file`; Atmos `!include.raw` already covers byte-preserving file-backed value content, including a source file's terminal newline. Content normalization is separate from Helm lifecycle behavior.
 - Supporting Helm CLI subcommand, getter, downloader, post-renderer, or Wasm plugins in native SDK operations.
-- Adding force replacement, server-side apply selection, dependency update, value reuse/reset, ownership takeover, validation bypass, or uninstall history/cascade options. In particular, Helm `Uninstall.KeepHistory`, the `--keep-history` flag, and a `keep_history` component field are deferred from R1.
+- Adding force replacement, server-side apply selection, value reuse/reset, ownership takeover, validation bypass, or uninstall history/cascade options. In particular, Helm `Uninstall.KeepHistory`, the `--keep-history` flag, and a `keep_history` component field are deferred from R1.
 - Changing dependency selection or scheduler algorithms.
 - Treating a successful rollback as a successful DAG node.