Smoke Signals

v0.9.1 (2026-09-29)

Full Changelog Previous Releases

• Release v0.9.1
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• docs: taint.log path in TESTING step 20 (build 9)
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• docs: fix taint.log path in TESTING step 20 (build 8)
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• docs: Sep 29 results, eight fixes, TESTING step 20 (build 7)
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• 0.9.1: debug /smoke simlock, a simulated locked channel (build 6)
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• 0.9.1: wider retry, every lower channel name probed in turn (build 5)
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• 0.9.1: member count asked at status time, comms state follows membership, case-insensitive channel lookups (build 4)
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• 0.9.1: beacon dedupe by realm + sender first name, all delivered formats shown (build 3)
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• 0.9.1: join with Blizzard's exact four arguments, log CHANNEL_PASSWORD_REQUEST (build 2)
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• 0.9.1: tracked BUILD number, printed in /smoke status
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• 0.9.1: fallback channel names, /smoke unlock, debug logging of join and password args
  • channel family SmokeSignal/2/3, cap 3: up after two WRONG_PASSWORD only,
    primary retried every 5 min, all joins and leaves on hardware events
  • active channel in /smoke status; n= tail field in the payload
  • /smoke unlock (debug) calls the original SetChannelPassword past the hook
  • debug output: exact JoinPermanentChannel and SetChannelPassword arguments
  • tests load Channel.lua; hook verified to block (248/248)
  • docs: passwords are enforced; predictable-name weakness and cap
    Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• 0.9.1: home-realm docs, protocol 3 realm key, channel password hardening, held sends, realm beacon
  • docs: home-realm partition, UnitFullName (first, surname), password decision reversed
  • wire protocol 3: r=<realm> tail field, unknown trailing fields ignored (protocol break)
  • /smoke status: chat realm, member count, protocol version
  • channel: fixed password on join, re-set on OWNER_CHANGED, /password blocked for our channel
  • send: rejoin and hold when off the channel, flushed on the next hardware event
  • temporary realm beacon on first hardware event; /smoke telemetry, /smoke realms
  • debug: /smoke party, /smoke beacontest; tests 181/181
    Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• docs: /who crosses home realms, filed as v2 whisper-relay peer discovery
  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
• Channel hardening: comms state, lockout handling, chat hiding, parser hardening
  • Comms.state (connecting/connected/locked/banned) driven by
    CHAT_MSG_CHANNEL_NOTICE and _NOTICE_USER for our channel only
  • one warning line per lockout episode with a [Retry] link; sends no-op with
    a hint while locked/banned, receiving and own pins untouched
  • rejoin spent by hardware events (5 min due interval, max 6), never a timer
  • kick vs /leave: auto-join-off decision deferred 3 s, dropped on a kick/ban
  • every chat frame filters our channel's messages, joins, leaves and notices;
    channel stays attached so the permanent join still survives logout
  • inbound: 200-byte cap, 10 msgs/60 s per sender, pcall around parse+handle,
    integer/positive checks on mapID and itemID
  • docs/comms-security.md, design.md, TESTING.md step 15, changelog; 108 tests
    Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com