docs(cli): clarify changelog dating uses timever tag instead of API publish date

apps/cli/release-topics.ts

@@ -19,9 +19,9 @@
  * The tag is annotated and backdated (tagger date = finish), so
  * `git tag --sort=taggerdate` reads as the campaign's history even for tags
  * minted by a backfill. The release's own published date cannot be backdated
- * (the API has no field for it), and the docs changelog (githubReleases in
- * apps/docs/blume.config.ts) dates entries by it — so a backfilled entry
- * carries its real finish time in the version and the body's first sentence.
+ * (the API has no field for it), so the docs changelog dates each entry from
+ * this timever tag instead (`releasesDatedByTag` in apps/docs/blume.config.ts)
+ * — the tag format is that contract.
  *
  * Reconciles instead of reacting: every finished topic without a release gets
  * one, so a first run backfills the whole campaign; an existing release keeps