Skip to content

Commit 3b8b929

Browse files
leggetterclaude
andcommitted
docs(release): name fixed tools as the reader knows them
Two fix entries named gateway_connections_read and gateway_metrics_read. Neither existed in v2.6.0 — the defects were in hookdeck_connections and hookdeck_metrics, and the new names are where those tools live now. A reader on v2.6.0 would have gone looking for a tool they have never had, in a bug report about software they have been running for weeks. Both entries now lead with the name that broke and give the new one after it. Checked every bolded lead in Fixes against the v2.6.0 tool list; these were the only two. Two rules added to the voice guide, both learned by getting them wrong here. Name a fixed thing by the name the reader has, not the one it is getting. And on cutting to length: cut padding, never cut a qualification or the example a claim rests on — with the three things the compression pass broke recorded as the worked cases, because the length rule had a number and the accuracy rule had nothing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 parent c0f7357 commit 3b8b929

2 files changed

Lines changed: 29 additions & 7 deletions

File tree

‎.agents/skills/hookdeck-cli-release/references/release-notes-voice.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -83,6 +83,27 @@ is not a fix** — it is part of shipping the feature, and belongs in New featur
8383
Betas do not count as shipped. Check the previous GA *tag*, not the commit log: a long-lived branch
8484
means reachability does not imply the change is new. Build the tag if that is what it takes.
8585

86+
**Name a fixed thing by the name the reader has, not the one it is getting.** In a release that
87+
renames things, a fix entry describes a defect in the *old* surface, so the old name is what a
88+
reader recognises — give the new name after it:
89+
90+
> **`hookdeck_connections` accepted a `disabled` filter it could not honour** — now
91+
> `gateway_connections_read`. …
92+
93+
Getting this backwards sends someone looking for a tool they have never had, in a bug report about
94+
software they have been running for weeks.
95+
96+
## Cutting to length: what is safe to remove
97+
98+
Length is a real constraint, but three separate errors in the v3.0.0 draft came from a compression
99+
pass, not from the first draft: the detail that three tools keep the `hookdeck_` prefix (which made
100+
the rename claim false), the name of the `--allow-write` flag on the Outpost server, and the worked
101+
example under "and the next command disagreed", which left the phrase meaningless.
102+
103+
**Cut padding. Never cut a qualification, or the example a claim rests on.** If an entry cannot
104+
reach the word target without losing one of those, it is a long entry — take the words. Length is
105+
the default, accuracy is the constraint.
106+
86107
## What this voice avoids
87108

88109
- **Verbosity.** See the table. This is the failure mode.

‎plans/v3.0.0-release-notes.md‎

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -128,13 +128,14 @@ If you have automation built against v2.x, the three breaking changes are the on
128128
- **Argument values a tool cannot use are refused rather than dropped.** `{"measures": ["count", 5]}`
129129
queried one measure and reported success.
130130

131-
- **`gateway_connections_read` no longer accepts a `disabled` filter it cannot honour.**
132-
`disabled: false` set nothing and returned every connection as though filtered to the enabled
133-
ones. There is no enabled-only filter to send, so it is now refused with that explanation.
134-
135-
- **`gateway_metrics_read` rejected the `measures` it had just been given.** It was the one tool not
136-
accepting the comma-separated form, so `"measures": "count"` was dropped and you were told
137-
`measures is required`.
131+
- **`hookdeck_connections` accepted a `disabled` filter it could not honour** — now
132+
`gateway_connections_read`. `disabled: false` set nothing and returned every connection as though
133+
filtered to the enabled ones. There is no enabled-only filter to send, so it is refused with that
134+
explanation instead.
135+
136+
- **`hookdeck_metrics` rejected the `measures` it had just been given** — now
137+
`gateway_metrics_read`. It was the one tool not accepting the comma-separated form, so
138+
`"measures": "count"` was dropped and you were told `measures is required`.
138139

139140
- **The connections tools no longer say "id or name is required" to callers who passed `name`.**
140141
`name` is a declared property, but only `id` was read.

0 commit comments

Comments
 (0)