protocol-alignment

To detect protocol drift, compare your event and control_request implementation against the extension's extracted protocol surface. This generates a structured coverage matrix identifying gaps using statuses like Implemented, Partial, and Missing.

A protocol coverage matrix tracks event schema alignment by mapping CLI-to-server and server-to-CLI paths against the real extension surface. It outputs a structured gap status per event, subtype, and control_request to quantify completeness.

Validate Zod schemas by using real captured NDJSON samples as ground truth. This confirms schema accuracy and detects behavioral differences after extension updates by testing actual event data against your defined protocol structures.

Yes, you can audit protocol completeness after an update by comparing your three protocol files against the extracted extension surface. This comparison reveals behavioral differences and missing event subtypes across communication paths.

Yes, protocol alignment requires focusing the comparison on three specific cc-office protocol files: claude-schemas.ts, claude.ts, and claude-adapter.ts. It also uses extracted extension protocol surfaces and real JSON samples as references.

Protocol drift breaks control_request behavior because implementation differences silently corrupt event handling and permissions. Comparing your protocol against the real extension surface detects these gaps and prevents unreliable sessions.