shion@0.5.0

Minor Changes

• #62 8569a14 Thanks @4lch4! - Notifications now land in text channels in the Discord category named by DISCORD_CATEGORY_ID,
  instead of always in my DM. A Notification's optional topic picks the channel named after it, a
  critical Notification lands in #alerts and mentions me, and one with no Topic or no matching
  channel lands in #inbox. When a channel can't be used, Delivery falls back to #inbox and then
  to my DM, and the response reports deliveredTo and, after a fallback, rerouted.

  DISCORD_CATEGORY_ID is now required, and the Gateway refuses to start without it.

opencode-watcher@0.2.0

Minor Changes

• #65 07551ff Thanks @4lch4! - Every Notification now carries the Topic models, so it lands in the #models channel instead of
  #inbox.

Patch Changes

• Updated dependencies [07551ff]:
  • @shion/watcher-kit@0.3.0

@shion/watcher-kit@0.3.0

Minor Changes

• #65 07551ff Thanks @4lch4! - Notifications and the outage reporter can carry a Topic, which picks the channel the Gateway
  delivers to.

opencode-watcher@0.1.3

Patch Changes

• #57 0a10876 Thanks @4lch4! - The outage reporter now waits for two failed polls in a row before warning, so a single timeout
  (such as models.dev redeploying) no longer sends a warning and then a recovery Notification.
  failuresBeforeWarning changes the threshold, and defaults to 2.
• Updated dependencies [0a10876]:
  • @shion/watcher-kit@0.2.0

@shion/watcher-kit@0.2.0

Minor Changes

• #57 0a10876 Thanks @4lch4! - The outage reporter now waits for two failed polls in a row before warning, so a single timeout
  (such as models.dev redeploying) no longer sends a warning and then a recovery Notification.
  failuresBeforeWarning changes the threshold, and defaults to 2.

shion@0.4.0

Minor Changes

• #38 a9d33fe Thanks @4lch4! - Delivery now shows when a Notification arrived as a Sent field on the embed, using a Discord
  timestamp. Each Discord client renders it in the reader's own timezone, and the embed's built-in
  timestamp is gone, so the time is not shown twice.

Patch Changes

• #51 c1909c0 Thanks @4lch4! - The deprecated POST /v1/messages route now logs one warning per call, naming the Source, so any
  Caller still using it can be found before the alias is removed. POST /v1/notifications is
  unchanged and does not log.

opencode-watcher@0.1.2

Patch Changes

• #51 c1909c0 Thanks @4lch4! - Posts Notifications to POST /v1/notifications through the updated @shion/watcher-kit, so this
  release needs Gateway 0.3.0 or newer. Nothing else about the Watcher changes; the release exists so
  the image is rebuilt and redeployed with the new kit.
• Updated dependencies [c1909c0]:
  • @shion/watcher-kit@0.1.2

@shion/watcher-kit@0.1.2

Patch Changes

• #51 c1909c0 Thanks @4lch4! - createShionSender now posts Notifications to POST /v1/notifications instead of the deprecated
  POST /v1/messages. It needs Gateway 0.3.0 or newer, which is Shion's rollback floor, so every
  Gateway it can meet has the route.

shion@0.3.0

Minor Changes

• #32 d5fbe28 Thanks @4lch4! - A Message is now a Notification. POST /v1/notifications delivers one, and GET /v1/status
  reports its counters as notifications. POST /v1/messages and the messages counters still
  work, as deprecated aliases, so no Caller breaks.

shion@0.2.2

Patch Changes

• #24 53bc29a Thanks @4lch4! - The Gateway now builds from a Bun workspace and joins the shared shion Docker network as
  shion-gateway, so a Watcher can reach it at http://shion-gateway:3000.