jeopi-cli 16.6.12 → 16.6.13

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 ## [Unreleased]
 
+## [16.6.13] - 2026-10-30
+
+### Added
+
+- Discord requests in the messenger gateway and `/discord live` show one in-place status line with the current step (the tool call's declared intent or tool name), edited at most every 2 seconds and deleted when the request finishes; see [Discord progress](../../docs/messenger/discord.md#overview).
+
+### Fixed
+
+- Explain how to recover when an empty dependency name in Bun's global manifest prevents updates.
+
 ## [16.6.12] - 2026-10-29
 
 ### Added

package/README.md

@@ -73,7 +73,7 @@ jeopi messenger run --config /absolute/private/path/messenger.json
 2. In the Bot settings, enable the privileged **Message Content Intent** (obtain approval if Discord requires it for your app). The adapter requests `GUILD_MESSAGES`, `DIRECT_MESSAGES`, and `MESSAGE_CONTENT`; it does not request member or presence intents.
 3. Install/invite the bot with the `bot` scope and **View Channels**, **Send Messages**, and **Read Message History**. For server-channel requests, also grant **Create Public Threads**, **Send Messages in Threads**, **Add Reactions**, and **Attach Files** in the intended channels; existing threads must be accessible to the bot. Attach Files is needed for exact copies when Discord would strip boundary whitespace. Administrator permission is not required.
 4. Enable Developer Mode in Discord's Advanced settings, then use **Copy User ID** for each authorized human and **Copy Channel ID** for each allowed channel/DM. Use exact numeric IDs as strings. Allowing a parent channel permits authorized requests in its threads; a thread ID can also be allowed directly. Users must be able to DM the bot under their Discord privacy settings.
-5. Mention the bot for a server-channel request: it creates a thread for that request. A request in an existing thread stays there; DMs remain direct. The original sender can continue without mentioning the bot in a bot-created thread while its in-memory mapping survives; restart or eviction loses that association. Explicitly mention the bot in other thread requests. Progress reactions are best-effort: ⏳ while processing, then ✅ or ❌.
+5. Mention the bot for a server-channel request: it creates a thread for that request. A request in an existing thread stays there; DMs remain direct. The original sender can continue without mentioning the bot in a bot-created thread while its in-memory mapping survives; restart or eviction loses that association. Explicitly mention the bot in other thread requests. Progress is best-effort: ⏳ while processing, then ✅ or ❌ reactions, plus one in-place status line (for example `⏳ Step 3 · Running the test suite`) that shows the current tool intent and is deleted when the request finishes; see [Discord progress](../../docs/messenger/discord.md#overview).
 
 For Discord file exchange, explicitly configure `platforms.discord.artifactDir` as a pre-existing private staging directory and enable the needed host tools; see the [file workflow and limits](../../docs/messenger/discord.md#discord-file-workflow). The gateway reuses the configured model/provider authentication; attachments and tool results may be sent to that provider. Created server threads are public to people who can view the channel, not just allowlisted users.