Drop #4630 from the commit list

Issue 4630 is not committed, but planned

Signed-off-by: Jon Schulman <25127543+jonnyborbs@users.noreply.github.com>

Author: jonnyborbs

site/src/content/docs/roadmap.mdx

@@ -31,7 +31,6 @@ Zarf Values and Go templating ([#3946](https://github.com/zarf-dev/zarf/issues/3
 **Operator and deployer experience:**
 
 - **Granular value overrides via `--set-values`** ([#4224](https://github.com/zarf-dev/zarf/issues/4224)): Adding a `--set-values` flag so operators can override individual value keys at deploy time using dot-notation (e.g. `--set-values=.registry.image=my-image`), providing Helm-style granularity without requiring a full values file.
-- **Helm chart full-values passthrough** ([#4630](https://github.com/zarf-dev/zarf/issues/4630)): Improving the experience for package creators who want to allow deployers to override arbitrary Helm chart values without having to define explicit `sourcePath`/`targetPath` mappings for every key.
 - **Early validation of undefined values** ([#4693](https://github.com/zarf-dev/zarf/issues/4693)): Zarf should detect missing required values before a deployment begins, rather than failing mid-deploy after components have already been applied.
 
 **Package creator experience:**
@@ -123,4 +122,4 @@ Our feature lifecycle is defined as follows:
 - **Alpha**: Experimental, subject to change or removal.
 - **Beta**: Functionally complete but still evolving; documented with known caveats.
 - **Stable**: Guaranteed backwards compatibility, robust documentation and testing.
-- **Deprecated**: Marked for removal, with alternatives documented.
+- **Deprecated**: Marked for removal, with alternatives documented.