cursor CLI gặp lỗi queue messages liên tục

BUG: 1DevTool link send → Cursor CLI terminal stuck "queued / waiting-for-readiness", never delivers

Product: 1DevTool agent link (v7 CLI: 1devtool-agent-v7 link send)
Target terminal: "Cursor Composer 2.5" (agent=claude, principal peer)
toTerminalId: f26d50aa-d6f4-41db-8508-d2458d252c06
linkId: lk-090c0c10-6c1c-496d-9085-064c9f07289b
Sender terminal: "Claude Fable" (93beda76-6d90-49f0-873f-0be6fe6d3763), project Fotovibe

Failing message:
messageId: lm-5ed50c14-5315-48c3-a86d-dd18051a095c
state: queued
queuedReason: waiting-for-readiness ← stuck here, no numeric error code emitted
createdAt: 1786500844323 (ms epoch) — still queued minutes later, never delivered/answered
error field: (none — queued state carries no error, unlike failed msgs which return error:"delivery-unconfirmed")

Link state at time of send (from whoami): link is ACTIVE, delivery=auto, permissions=[send,ask]
→ so the link is healthy; the TARGET never reports "ready", so delivery is indefinitely deferred.

Control (same sender, same batch, same flags): the other two peers delivered fine

• "Set up Claude Fable"/claude (51f2ddaf…): state=delivered, ~2.6s
• "Hermes Agent"/hermes (1f08bf1f…): state=delivered, ~1.4s
• Cursor Composer 2.5 (f26d50aa…): state=queued waiting-for-readiness (never)

Repro: 1devtool-agent-v7 link send --to=f26d50aa-… --prompt-stdin --wait
Expected: waiting-for-readiness auto-retries ≤10 min then delivers, OR surfaces a terminal error code.
Actual: Cursor CLI terminal never emits a readiness signal → message parked silently; --wait returns a queued receipt with no actionable code.

Ask: Cursor CLI should emit a ready/heartbeat signal to 1DevTool link layer (like claude/hermes agents do), OR the link layer should surface a distinct error code when readiness times out instead of an indefinite queued state.