v0.12.6

Fixed

• Live chat transfer did nothing. Agent/TicketShow never gave
  ChatActionBar a transfer endpoint, so picking a department in the Transfer
  menu posted nothing on any backend. It now passes
  route('escalated.admin.chat.transfer', ticket.chat_session_id) (the name
  escalated-laravel serves it under). If the host's route() helper does not
  know that name (it throws, or a shim returns '#'), the bar gets no endpoint
  and behaves as before.
• ChatActionBar now posts the transfer body backends read,
  {"agent_id": id} or {"department_id": id}, instead of {"type", "id"}
  (which escalated-laravel rejected with 422). The transfer event still
  carries {type, id}.
• Live chat End Chat did nothing on the server. Agent/TicketShow never
  gave ChatActionBar an end endpoint either, so confirming End Chat only
  reloaded the page and the session stayed live. It now passes
  route('escalated.admin.chat.end', ticket.chat_session_id), with the same
  fallback (no endpoint, behaves as before) when the host does not know the
  name. The bar posts an empty JSON object ({}), since the endpoint takes no
  fields, and now emits end-chat after the request settles instead of before
  it, so a parent that reloads on the event sees the ended session. Listeners
  still receive the session id.