diff --git a/.changeset/20594-cli-bin-form-d.md b/.changeset/20594-cli-bin-form-d.md
new file mode 100644
index 00000000000..d638d348c93
--- /dev/null
+++ b/.changeset/20594-cli-bin-form-d.md
@@ -0,0 +1,13 @@
+---
+'@objectstack/cli': patch
+---
+
+A docblock line in `@objectstack/cli`'s `bin/run.js` no longer cites a tracker number
+
+The docblock above `bin/run.js`'s `process.stderr` `error` listener ended a
+sentence with a tracker number that no longer resolves on GitHub. The number is
+gone and the sentence stays: `files` names only `dist`, but npm packs a `bin`
+target regardless, which is the measured fact the number was pointing at. The
+file ships because of that same packing rule, which is why this is a release
+note at all. Comment only: no command, flag, exit code, error code, export or
+runtime behaviour changes.
diff --git a/packages/cli/bin/run.js b/packages/cli/bin/run.js
index 3a56621bec6..4e24ceca831 100755
--- a/packages/cli/bin/run.js
+++ b/packages/cli/bin/run.js
@@ -222,7 +222,7 @@ try {
  * serves, exit 0 at a 20 s SIGTERM, having written 7926 bytes over 16.6 s. So
  * the crash costs the run at its FIRST diagnostic line and 20 of its 21 stderr
  * writes, on the entry point a customer's install actually runs (`files` names
- * only `dist`, but npm packs a `bin` target regardless — #14874).
+ * only `dist`, but npm packs a `bin` target regardless).
  *
  * ⛔ Deliberately NOT narrowed to `error.code === 'EPIPE'`, for the reason
  * `bin/run-dev.js` records: the reason to tolerate is not WHICH error it is.