fix: validate rendered Helm fixtures correctly

Author: shirkevich

.pre-commit-config.yaml

@@ -90,7 +90,7 @@ repos:
         stages: [pre-commit]
         exclude: ^(vendor/|tests/test-cases/|tests/testdata/|tests/snapshots/|.*\.svg|website/src/components/Screengrabs/)
       - id: check-yaml
-        exclude: ^(vendor/|tests/test-cases/|tests/testdata/|tests/snapshots/|tests/fixtures/)
+        exclude: ^(vendor/|tests/test-cases/|tests/testdata/|tests/snapshots/|tests/fixtures/|examples/helm/components/helm/demo/templates/)
         args: [--allow-multiple-documents, --unsafe]
       - id: check-added-large-files
         stages: [pre-commit]

…6-08-01-native-helm-release-lifecycle.md …6-07-31-native-helm-release-lifecycle.mddocs/fixes/2026-08-01-native-helm-release-lifecycle.md renamed to docs/fixes/2026-07-31-native-helm-release-lifecycle.md docs/fixes/2026-08-01-native-helm-release-lifecycle.md renamed to docs/fixes/2026-07-31-native-helm-release-lifecycle.md

@@ -1,12 +1,13 @@
 # Native Helm release lifecycle
 
-**Date:** 2026-08-01
+**Date:** 2026-07-31
 
 Native Helm cluster operations now expose Helm 4 wait, timeout, recovery,
 history, hook, and CRD controls through stack configuration and explicit command
 flags. Apply and delete dry runs now reach the Helm SDK without persisting release
-state, and caller cancellation propagates through direct and dependency-ordered
-execution.
+state. Caller cancellation propagates through direct and dependency-ordered
+execution into install and upgrade actions and into delete wait and hook phases;
+Helm 4 does not expose a context-aware uninstall request.
 
 ## Migration notes