diff --git a/CHANGELOG.md b/CHANGELOG.md
index 89d29e4..3cb3a7d 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,6 +9,23 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
 Every version published to a channel appears here. Nothing is written from memory afterwards: a build
 cannot be published without its entry.
 
+## 2026-09-12 — The lightning bolt on a dock row would not say what it meant `web 0.134.0`
+
+A row in the dock can carry a small glyph after its title: a shield, a lightning bolt, or a dot. The
+lightning bolt is the consequential one — it marks a conversation the assistant is allowed to run to
+the end without asking, destructive steps included. There was no way to find that out from the rail.
+Hovering it produced nothing, and a screen reader read the row without mentioning it.
+
+**Hovering a badge now names it**, in the rail and in the phone sheet: _Autonomous: runs everything
+without asking, including destructive operations_, _1 plan waiting on you_, _Unsent draft_. The
+wording for the lightning bolt is the same sentence the autonomy setting itself uses, so the badge
+and the control that sets it no longer describe the same permission in two different vocabularies.
+
+**And a dock row now announces everything that is true of it**, not only what fitted in the slot.
+There is room on a row for one glyph, so a conversation that is both waiting on a decision and
+allowed to run unattended drew only the shield. The spoken name lists both, plus an unsent draft,
+after the title and the activity.
+
 ## 2026-09-12 — The dock stayed on one computer, and its menu offered to add a conversation that was already there `api 0.111.0` `web 0.133.0`
 
 Two complaints about the same rail, a day apart. They turn out to be the same mistake made twice: