parser-development

To parse NDJSON stream events into typed socket events, you need a pipeline that performs JSON parsing, discriminated type detection, Zod safe validation, and adapter transformation. This produces validated, Socket.IO-ready socket events with deterministic emission and unknown-type fallback.

The best way to validate unknown CLI protocol event types safely is using Zod discriminated union schemas for type detection. This approach applies explicit handling for unknown events with a raw fallback, ensuring stable event contracts across message, stream, control, system, and notification subtypes.

To add a new event type to an NDJSON protocol parser, add a Zod schema for the event, register it in the known event types registry and schema lookup function, then implement the conversion in the adapter and validate with tests in the protocol test directory.

Yes, this stream parser supports server actions through the adapter pattern. It produces adapter outputs that include events, autoResponses, controlResponses, and serverActions such as auto_respond, read_diff, and forward_to_client across CLI, summoner, and client layers.

CLI event schema validation fails on unknown event types when they are not registered in the known event types registry or lack a matching Zod schema. Using safe validation with a deterministic unknown-type fallback ensures unregistered events are handled gracefully instead of crashing the parse pipeline.

Yes, you can use the adapter pattern to transform protocol events into UI-renderable messages. The adapter converts parsed protocol events into socket event messages, producing events, autoResponses, controlResponses, and serverActions that the client UI can render directly.