instar 0.23.0 → 0.23.2

package/upgrades/0.23.1.md

@@ -0,0 +1,28 @@
+# Upgrade Guide — v0.23.1
+
+<!-- bump: patch -->
+
+## What Changed
+
+**AuthGate default flipped from allow-all to deny-all when no authorized users are configured.**
+
+Previously, `AuthGate.isAuthorized()` returned `true` when the `authorizedUsers` set was empty (size === 0). This dangerous default caused a critical bug where a WhatsApp-connected agent with no `authorizedNumbers` configured responded to every incoming message on the account — including personal conversations with unrelated contacts.
+
+Now:
+- Empty `authorizedUsers` = deny all (safe default)
+- To explicitly allow all users, include `'*'` in the authorized list (e.g., `authorizedNumbers: ['*']`)
+- WhatsApp adapter logs a console warning when started with no `authorizedNumbers`
+
+**Migration impact**: Any agent config with empty or missing `authorizedNumbers` will now correctly reject all messages. Agents that intentionally accept messages from anyone must add `'*'` to their authorized list.
+
+## What to Tell Your User
+
+- **Security fix**: "I've tightened up who can message me. Previously if no allowed contacts were set, I'd respond to everyone — now I only respond to contacts you've specifically approved. This prevents me from accidentally responding to messages meant for you."
+
+## Summary of New Capabilities
+
+| Capability | How to Use |
+|-----------|-----------|
+| Safe default authorization | Automatic — empty config now denies all |
+| Wildcard authorization | Add a wildcard entry to your allowed contacts to accept everyone |
+| Missing config warning | Automatic — console warning on startup if no contacts configured |

package/upgrades/0.23.2.md

@@ -0,0 +1,32 @@
+# Upgrade Guide — v0.23.2
+
+<!-- bump: patch -->
+
+## What Changed
+
+**Session respawn loop fixed — spawn-in-progress guard + user-visible failure messages.**
+
+Previously, when a session died and kept failing to restart (due to session limit, quota exhaustion, or other errors), the system entered a silent respawn loop:
+- Each incoming Telegram message triggered a new respawn attempt
+- Respawn failures were only logged to console — never reported to the user
+- The user saw repeated "🔄 Session restarting — message queued" messages with no explanation
+
+Two fixes:
+
+1. **Spawn-in-progress guard**: A per-topic lock prevents multiple concurrent spawn attempts for the same topic. If a spawn is already in progress, subsequent messages receive "Session is still starting up — please wait a moment" instead of triggering another spawn.
+
+2. **Failure reporting**: When a respawn fails, the user now receives a Telegram message explaining what happened:
+   - Session limit errors: "❌ Session restart failed — session limit reached. Close an existing session or increase maxSessions in your config, then try again."
+   - Other errors: "❌ Session restart failed. Try sending your message again in a moment."
+
+## What to Tell Your User
+
+- **Session restart reliability**: "When my session dies and I can't restart it, I'll now tell you exactly what went wrong — including if you've hit the session limit — instead of just silently failing. Expect clearer error messages."
+
+## Summary of New Capabilities
+
+| Capability | How to Use |
+|-----------|-----------|
+| Respawn failure messages | Automatic — user receives error via Telegram when restart fails |
+| Session limit error guidance | Automatic — specific message when session limit prevents restart |
+| Spawn deduplication | Automatic — rapid messages during startup no longer create duplicate sessions |