fix(apollo): replace z.record(z.any()) with z.unknown() at tool argument boundaries

@kaavee315draftchecks n/achecks…fix/zod-record-any-to-unknown → master4 files · +131 −4updated 5d ago

▸Description

Description

Replace z.record(z.any()) with z.record(z.string(), z.unknown()) at three tool argument/output schema sites in Apollo:

apps/apollo/src/pages/api/v3/tools/execute/[tool_slug]/index.ts lines 86 and 126: arguments request field and data response field
apps/apollo/src/pages/api/v3/tools/types.ts lines 36 and 66: input_parameters and output_parameters in ToolCommonSchema
apps/apollo/src/pages/api/v3/toolkits/[slug].ts line 264: rawProxyInfoByAuthSchemes array element type

This is a pure TypeScript compile-time tightening: values previously typed any are now unknown, forcing callers to narrow before use. There is no runtime or Zod behavior change.

The existing cast toolArguments as Record<string, unknown> at line 373 of the execute route (pre-existing) and the generated ExecuteToolResponse.data: { [key: string]: unknown } are already consistent with this stricter type.

How did I test this PR

Relying on CI check-types (no node_modules in this worktree, so local typecheck was not possible)
Reviewed all changed sites and their in-file consumers to confirm no narrowing was needed: arguments is passed directly to executeTool (no property access on values in the same file), data is assigned from ExecuteToolResponse.data which is already Record<string, unknown>, input_parameters/output_parameters are schema-only (no in-file property access on values), and rawProxyInfoByAuthSchemes is schema-only
Confirmed z.record(z.string(), z.unknown()) is the correct Zod v3 two-argument form

🤖 Generated with Claude Code

loading diff…