Greptile Summary

Adds .nullable() to the endpoints field in channelSummarySchema so that legacy channels that return endpoints: null from the backend pass Zod validation without an error. The change mirrors the existing pattern already applied to the tags field on the same schema.

• schema.ts: one-line change on the endpoints field to match the tags nullable pattern, resolving the validation failure on the settings page for legacy channels.
• All downstream consumers (channels-endpoints-dialog.tsx, channels-action-dialog.tsx) already guard against null via ?? [] and optional chaining, so no additional changes are needed.

Confidence Score: 5/5

Safe to merge — a one-line targeted fix that unblocks the settings page for legacy channels.

The change is a minimal, focused schema relaxation that mirrors an identical pattern already used for the tags field on the same object. Every downstream consumer of endpoints already uses null-safe access (?? [] or optional chaining), so the newly admitted null value cannot cause a runtime error in the UI.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Backend
    participant ZodParser as Zod Parser (channelSummarySchema)
    participant Component as React Component

    Backend->>ZodParser: "{ endpoints: null } (legacy channel)"
    Note over ZodParser: Before: validation error – null not accepted
    Note over ZodParser: After: .nullable() accepts null, passes through
    ZodParser->>Component: "{ endpoints: null }"
    Component->>Component: channel.endpoints ?? [] → []
    Component->>Component: channel?.endpoints?.find(...) → undefined

_{Reviews (1): Last reviewed commit: "fix(frontend): allow null endpoints in c..." | Re-trigger Greptile}