Bug Description
The DiscordAccountSchema in zod-schema.providers-core.ts uses .strict() but is missing the agentComponents field. This field is:
- Defined in the TypeScript type at
types.discord.ts:301 as agentComponents?: DiscordAgentComponentsConfig
- Actively read at runtime in
discord/monitor/provider.ts:544-545
- Used in tests at
discord/monitor/provider.test.ts:87
Because the schema is .strict(), any user who sets channels.discord.agentComponents.enabled: true in their config YAML will get a validation error, even though the field is valid and used at runtime.
Steps to Reproduce
channels:
discord:
agentComponents:
enabled: true
This config is rejected by validateConfigObject() with an unrecognized key error.
Expected Behavior
The config should be accepted, since agentComponents is a valid field defined in the TypeScript types and used at runtime.
Root Cause
Type/schema drift: agentComponents was added to the TypeScript types and runtime code but not to the Zod validation schema.
Bug Description
The
DiscordAccountSchemainzod-schema.providers-core.tsuses.strict()but is missing theagentComponentsfield. This field is:types.discord.ts:301asagentComponents?: DiscordAgentComponentsConfigdiscord/monitor/provider.ts:544-545discord/monitor/provider.test.ts:87Because the schema is
.strict(), any user who setschannels.discord.agentComponents.enabled: truein their config YAML will get a validation error, even though the field is valid and used at runtime.Steps to Reproduce
This config is rejected by
validateConfigObject()with an unrecognized key error.Expected Behavior
The config should be accepted, since
agentComponentsis a valid field defined in the TypeScript types and used at runtime.Root Cause
Type/schema drift:
agentComponentswas added to the TypeScript types and runtime code but not to the Zod validation schema.