Relaticle

Fixes

Chat: Harden the multi-step AI approval flow against lost state, retries, and dropped websocket events (#322)

• Resume deadlock: typing “resume”/“continue” superseded the in-flight proposal, then the assistant told the user to approve the now-gone card — a dead end. On resume/continue the assistant now re-issues a fresh, approvable proposal instead of pointing at the cancelled one.
• Duplicate proposals on retry: a transient provider 429/529/503 retried the continuation job from the top and re-created the proposal, producing up to 5 duplicate cards. createProposal() is now idempotent across retries — an identical still-pending proposal is collapsed instead of duplicated.
• Dropped-event recovery: a lost .tool_result left the approve/reject CTA missing and a lost stream_end left a truncated bubble until a full reload. The latest assistant message now self-heals — still-pending cards are re-merged on both stream_end and the 60s watchdog (additive, a no-op on the happy path).
• Observability: add redis:chat to Horizon waits so backlog on the most latency-sensitive queue raises a LongWaitDetected alert.

Full Changelog: https://github.com/relaticle/relaticle/compare/v3.3.4…v3.3.5