test-cursor-adapter

You can validate Cursor adapter protobuf normalization end-to-end by simulating a GetChatRequest flow through the compliance proxy using a synthetic script. This verifies the decoded audit data without needing live Cursor IDE traffic.

A Cursor adapter end-to-end normalization test verifies fields including kind, detectedSpec, model, confidence, and messages. This deterministic verification enables reliable regression checks after normalization or proxy configuration changes.

To test the compliance proxy audit flow, run the synthetic script in tests/manual/cursor_synthetic_chat.py to post a simulated request through the proxy. You then audit the resulting traffic events in the Control Plane UI or database.

Yes, you need a functioning proxy setup to run the Cursor adapter synthetic test. The script posts the synthetic GetChatRequest through the compliance proxy, which requires an active proxy environment to generate and capture the traffic events for auditing.

The Cursor adapter normalization test uses a synthetic script to provide deterministic, controlled validation of the protobuf normalizer. This allows precise regression checks of decoded fields like kind and model without the variability of live Cursor IDE traffic.

Yes, you can cross-check the traffic events produced by the Cursor adapter in the audit UI. The end-to-end validation confirms that events appear with the expected Normalize panel, allowing you to verify the trace visually or within the database.