docs: calling out the relationship between "helm history" and ".Release.History" and showing that the values are there and only included when the flag is set

Signed-off-by: Andrew Shoell <mrlunchbox777@gmail.com>

Author: mrlunchbox777

hips/hip-0029.md

@@ -97,6 +97,7 @@ The `--release-history-max` flag controls how many historical releases to retrie
 
 - **Different Chart Names:** Still populates `.Release.History` even if chart names differ—templates can detect and handle this
 - **Helm's Record:** Reflects Helm's stored release record, not actual cluster state (use `lookup()` for that)
+- **Relationship to `helm history`:** `.Release.History` is derived from the same release records used by `helm history <release>`, but exposed as a reverse-chronological, template-friendly projection with field filtering and `--release-history-max` limits.
 - **Dry-Run Behavior:** `helm template` and `--dry-run=client` always return an empty array (cluster-agnostic). `--dry-run=server` follows live command behavior and can populate history when available.
 - **Opt-In by Default:** Default max of 0 requires explicit user choice, preventing accidental performance impact
 
@@ -123,6 +124,7 @@ type HistoricalRelease struct {
     Revision     int       // Revision number
     Status       string    // Release status (deployed, superseded, failed, etc.)
     Chart        Chart     // Chart metadata (same structure as .Chart)
+    Values       map[string]interface{} // Optional: only included when --include-history-values is set
     FirstDeployed time.Time // When this release was first deployed
     LastDeployed  time.Time // When this release was last deployed
 }
@@ -206,6 +208,8 @@ The following table shows what values are available in template context for diff
 
 **Note:** Use `.Release.Revision` to distinguish installs (revision=1) from upgrades (revision>1).
 
+**Note:** `.Release.History` and `helm history <release>` both come from Helm's stored release records. For template ergonomics, `.Release.History` is reverse chronological (most recent first), filtered to HIP-defined fields, and capped by `--release-history-max`. During rollback, Helm creates a new revision; prior revisions remain in history.
+
 ## Backwards Compatibility
 
 Fully backwards compatible. The `.Release.History` field is purely additive—existing charts work unchanged. Go templates handle empty arrays safely; the recommended `{{ if gt (len .Release.History) 0 }}` pattern works in all scenarios. Default max of 0 means existing behavior is unchanged unless users explicitly opt in.