Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="agent/go-service/quantizedsliding/overrides.go" line_range="27-36" />
<code_context>
 }

-func buildMainInitializationOverride(end []int, quantityBox []int, quantityFilter *quantityFilterParam) map[string]any {
+func buildMainInitializationOverride(end []int, quantityBox []int, quantityFilter *quantityFilterParam, quantityOnlyRec bool, greenMask bool) map[string]any {
 	quantityParam := map[string]any{
-		"roi": append([]int(nil), quantityBox...),
</code_context>
<issue_to_address>
**suggestion:** The `quantityFilter` parameter is no longer used in `buildMainInitializationOverride`.

The function still takes `quantityFilter *quantityFilterParam`, but it’s not used. If it’s no longer needed here, remove the parameter to simplify the API and avoid confusing callers. If it should still affect behavior (e.g., at the pipeline level), please apply it when building the override rather than leaving it unused.

Suggested implementation:

```golang
func buildMainInitializationOverride(end []int, quantityBox []int, quantityOnlyRec bool, greenMask bool) map[string]any {

```

You’ll also need to:
1. Find all usages of `buildMainInitializationOverride` and remove the `quantityFilter` argument from each call (it will likely be the third argument previously).
2. Remove any now-unused `quantityFilter` variables that existed only to satisfy this call.
3. If `quantityFilter` *should* still influence behavior, instead of removing it entirely, you should incorporate its fields into the `quantityParam` / `override` maps in this function; that would require adding corresponding entries based on `quantityFilter`'s structure.
</issue_to_address>

Please address the comments from this code review:

## Overall Comments
- In `buildTemplateMatchButtonHelperOverride` / `buildTemplateMatchButtonOverride` the explicit `threshold: 0.8` was dropped, but the docs still describe a fixed 0.8 threshold; consider setting it explicitly again to avoid relying on engine defaults and to keep behavior aligned with the documentation.
- `resolveButtonHelperNode` can return an empty helper node string for unexpected `nextNode` values, which will then be passed into the `all_of` list; it may be safer to validate the mapping and either log or skip the template-match override when no helper node applies.
- In `buildSwipeSpecificQuantityOverride` the type assertion `clonedParam["Quantity"].(map[string]any)` will panic if the incoming param shape is wrong or missing; consider using a type switch / ok-check and failing gracefully instead of assuming the structure.

Please address the comments from this code review:

## Overall Comments
- In `buildMainInitializationOverride`, the `greenMask` parameter is accepted but never used; either wire it through to the relevant TemplateMatch parameters or remove it from the signature to avoid confusion.
- The new `buildTemplateMatchButtonHelperOverride` drops the previously hardcoded TemplateMatch `threshold` of 0.8; if that behavior is still desired, explicitly set `threshold` to maintain the prior matching sensitivity.
- For `Quantity.OnlyRec`, the normalization currently defaults the override to `false` when the field is omitted, which forces `only_rec` off in the pipeline; consider only injecting the `only_rec` override when the user explicitly provides `Quantity.OnlyRec` so that pipeline defaults remain usable.

## Individual Comments

### Comment 1
<location path="agent/go-service/quantizedsliding/overrides.go" line_range="27-33" />
<code_context>
 }

-func buildMainInitializationOverride(end []int, quantityBox []int, quantityFilter *quantityFilterParam) map[string]any {
+func buildMainInitializationOverride(end []int, quantityBox []int, quantityFilter *quantityFilterParam, quantityOnlyRec bool, greenMask bool) map[string]any {
 	quantityParam := map[string]any{
-		"roi": append([]int(nil), quantityBox...),
+		"roi":      append([]int(nil), quantityBox...),
+		"only_rec": quantityOnlyRec,
 	}

 	override := map[string]any{
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Consider either wiring `greenMask` into this override or removing it from the signature.

`greenMask` is passed from `handleMain` but never used when building this override. If it’s meant to affect template matching (like the button helper nodes), it should be included in the recognition params here; if not, the parameter should be removed from the function to avoid a no-op configuration option.
</issue_to_address>

### Comment 2
<location path="agent/go-service/quantizedsliding/overrides.go" line_range="124-130" />
<code_context>
 }

-func buildTemplateMatchButtonOverride(template string, repeat int) map[string]any {
+func resolveButtonHelperNode(nextNode string) string {
+	switch nextNode {
+	case nodeQuantizedSlidingIncreaseQuantity:
+		return nodeQuantizedSlidingIncreaseButton
+	case nodeQuantizedSlidingDecreaseQuantity:
+		return nodeQuantizedSlidingDecreaseButton
+	default:
+		return ""
+	}
</code_context>
<issue_to_address>
**issue:** Handle or guard against unknown `nextNode` values when resolving the button helper node.

If `nextNode` is anything else, this returns an empty string, which in `buildCheckQuantityBranchOverride` produces a helper keyed by `""` and an `And` node with `all_of: [""]`. That’s probably unintended and fragile. If `nextNode` should always be one of the known constants, consider panicking/returning an error, or at least skipping helper/And creation in this case to avoid malformed pipeline entries.
</issue_to_address>