v0.54.0

Fixed

• The ag-ui-feedback event now names the message that was rated.
  Vendors @artooi/ag-ui-web-component 0.44.0 (was 0.43.0). Its detail carried
  only the rated text and the rating, so a listener could not tell two answers
  that read the same apart, or find a rated message again after a reload. It now
  also carries messageId, the rated assistant message's AG-UI id, threadId,
  and runId on a message that streamed live (absent on one restored from
  history). Additive: content and rating are unchanged. The sidebar still
  offers no rating pair by default (MESSAGE_ACTIONS is "copy,retry") and
  listens for nothing, so an install that has not opted in sees no change. A
  project that has wired its own listener and set "copy,retry,feedback" reads
  the new fields from the same event. Keying ratings by messageId holds across
  a reload with the browser's per-tab storage, and with a
  conversation_store from django-ag-ui 0.68.3 or later, which stores a
  completed run's messages under the ids it streamed; below it a restored
  message carries an id the live one did not. The django-ag-ui floor stays
  where it is, because nothing in this package stores or reads a rating. The
  MESSAGE_ACTIONS documentation now lists the detail's fields. The same bundle
  corrects the component's own README, which said all three message actions are
  on by default. The development lock moves to django-ag-ui 0.68.3.