cursor: interactionQuery frames are unhandled - capability audit needed

handleServerMessage (packages/ai/src/api/cursor-agent.ts:769-812) has no case for interactionQuery; if the server ever issues one, senpi never sends interactionResponse and the server waits. The official client processes queries outside the serialized update chain so approvals cannot head-of-line block. Audit which capabilities senpi advertises and either stop advertising query-dependent ones or implement the response path. (2026-08-20 audit.)

Start at handleServerMessage in packages/ai/src/api/cursor-agent.ts:769-812 and trace the capabilities senpi advertises for Cursor interactions. Compare the handling of interactionQuery with the official client's query processing, then verify that advertised capabilities cannot leave the server waiting for an interactionResponse. Done means the audit has a documented outcome and the selected behavior is covered by tests.

Written by the indexing model from the issue text.