clisbot 0.1.51 → 0.1.53-beta.1

package/README.md

@@ -69,8 +69,8 @@ It is not just a tmux bridge with chat glued on top. `clisbot` treats Slack and
 ### I Just Want To Know What Changed Recently
 
 - start with [Recent Release Highlights](#recent-release-highlights)
-- then read [v0.1.51 Release Notes](docs/releases/v0.1.51.md) or the
-  [v0.1.51 Release Guide](docs/updates/releases/v0.1.51-release-guide.md)
+- then read [v0.1.52 Release Notes](docs/releases/v0.1.52.md) or the
+  [v0.1.52 Release Guide](docs/updates/releases/v0.1.52-release-guide.md)
 
 ## Why I Built This
 
@@ -89,7 +89,7 @@ The challenge is not whether AI is useful. It is how to make it work at enterpri
 - Team-first by design, with `AGENTS`, `USER`, and `MEMORY` context bootstrapping shaped for shared team reality instead of only personal solo-assistant flows.
 - Shared-surface permission control is a first-class feature: a bot can be in a team group but still answer only the specific people you allow there, while sensitive control actions stay behind explicit auth roles and permissions.
 - Useful for coding, operations, teamwork, and general assistant work, with fast chat controls such as `!<command>`, `/bash <command>`, `/queue`, `/loop`, `/streaming`, and `/mention`.
-- New in the `v0.1.50` to `v0.1.51` stable line: the AI-native control experience is much better, and `v0.1.51` also stretches the default runner startup window to 60 seconds so slower Codex, Claude, and Gemini launches do not time out so early.
+- New in the `v0.1.50` to `v0.1.52` stable line: the AI-native control experience is much better, the default runner startup window is now 60 seconds, and stale old startup-delay pins no longer silently keep upgraded installs on shorter timeouts.
 
 ## Who This Fits Best
 
@@ -185,12 +185,12 @@ Next steps:
 - `clisbot` also has a smart autopairing path to reduce first-run friction. If
   you send the bot a DM within the first 30 minutes, you can usually claim the
   owner role immediately and start using it without a separate pairing round.
-- New from the current `v0.1.50` to `v0.1.51` stable line: the AI-native operator experience is much stronger. You
+- New from the current `v0.1.50` to `v0.1.52` stable line: the AI-native operator experience is much stronger. You
   can increasingly ask the bot through chat to explain how to use it, update
   itself and summarize what's new, help onboard you, create or add a new bot or
   agent, or set up loops and schedules for recurring work instead of relying
   only on slash commands.
-- Existing configs from any version before `0.1.50` still update directly on first run when you install `v0.1.51`. clisbot writes a backup first under `~/.clisbot/backups/`, then rewrites the config to the current `0.1.50` schema shape.
+- Existing configs from any version before `0.1.50` still update directly on first run when you install `v0.1.52`. clisbot writes a backup first under `~/.clisbot/backups/`, then rewrites the config to the current `0.1.50` schema shape.
 - Shared Slack channels, Slack groups, Telegram groups, and Telegram topics are a separate gate: normal users need an explicit route such as `group:<id>` or `topic:<chatId>:<topicId>` before the bot will talk there. Legacy Slack `channel:<id>` input still works for compatibility.
 - After a shared surface is admitted, per-surface sender control comes from the bot's default shared rule `groups["*"]` plus any route-local `allowUsers` or `blockUsers`.
 - With that permission model, a bot can be added to a team group but still be
@@ -237,6 +237,7 @@ What happens next:
 
 ## Recent Release Highlights
 
+- `v0.1.52`: clarifies shared-route setup so `routes add ...` clearly means “use the agent currently assigned to that bot by default,” and prunes stale short `startupDelayMs` overrides so upgraded installs can actually inherit the newer 60-second startup default.
 - `v0.1.51`: raises the default runner startup window to 60 seconds across the
   standard CLI families and the shared runner fallback, so slower fresh launches
   are less likely to fail before the first prompt can be submitted.
@@ -271,6 +272,7 @@ Read the full notes here:
 
 - [CHANGELOG.md](CHANGELOG.md)
 - [Release Notes Index](docs/releases/README.md)
+- [v0.1.52 Release Notes](docs/releases/v0.1.52.md)
 - [v0.1.51 Release Notes](docs/releases/v0.1.51.md)
 - [v0.1.50 Release Notes](docs/releases/v0.1.50.md)
 - [v0.1.43 Release Notes](docs/releases/v0.1.43.md)
@@ -306,9 +308,9 @@ Update note for existing installs:
 - Older installs before `v0.1.50` now update directly on first run with a
   backup written first, so most people can update and restart without a manual
   migration pass.
-- `v0.1.51` keeps that direct-upgrade path and does not introduce a new config
-  schema bump; the main runtime change is a longer default runner startup
-  window.
+- `v0.1.52` keeps that direct-upgrade path and does not introduce a new config
+  schema bump; it also cleans up stale short startup-delay overrides that would
+  otherwise keep some upgraded installs on older timeout behavior.
 - After you are on the `v0.1.50` schema line, future upgrades should feel much
   more AI-native:
   in many cases you can simply ask the bot to update `clisbot` to the latest