Greptile Summary

This PR fixes a validation gap where agents.list[].params was silently rejected by AgentEntrySchema because the field was present in the AgentConfig TypeScript type but absent from the Zod schema that used .strict().

The one-line addition of params: z.record(z.string(), z.unknown()).optional() to AgentEntrySchema is exactly consistent with:

• The existing TypeScript type (params?: Record<string, unknown> in types.agents.ts, line 86)
• The analogous pattern already used in AgentDefaultsSchema (line 31 of zod-schema.agent-defaults.ts)

The .strict() constraint on the schema (line 752) ensures that any unrecognized fields are rejected, which is why params was being rejected before this fix. Adding it to the schema definition now allows configurations with agent-specific parameter overrides (for stream settings like cacheRetention, temperature, maxTokens) to pass validation.

No other changes are needed: the fix is a targeted schema-to-type alignment with minimal risk and no behavioural impact.

Confidence Score: 5/5

• Safe to merge — minimal, targeted fix that aligns the Zod validation schema with the existing TypeScript type definition.
• The change is a single-line addition that corrects a clear schema-type mismatch. The Zod type used (z.record(z.string(), z.unknown()).optional()) exactly mirrors the TypeScript type pattern, and the same pattern is already used elsewhere in the codebase (AgentDefaultsSchema). There is no risk of behavioural regression — the change only permits configurations that were previously rejected. No tests, logic, or other schema definitions require changes.
• No files require special attention.

_{Last reviewed commit: 2701b2b}

Merged via squash.

• Prepared head SHA: 9522761cf1d5f5318b6b44abfb1292384acd9c37
• Merge commit: b72c87712d7febccce17d7fbb9970aee4f4f1200

Thanks @atian8179!