Drop no-change reports; name the queued packages when a build starts

A release that published nothing is not news, and at a 5-minute cadence those
messages would bury the ones that matter — the log and bin/repo timers still
show the run happened.

Removing it would have left a start report with no follow-up, so the start
report now carries its own answer: check-versions writes the package names it
queued into the state file instead of touching an empty one, and the release
run reads them. 'A build is running' becomes 'your package is in this build',
which is the question the reports exist to answer.

bin/check-versions

@@ -153,7 +153,10 @@ check_mirror() {
   echo ""
 
   if [[ "$needs_build" == true ]]; then
-    touch "$state_file"
+    # Record WHAT is queued, not just THAT something is: the release run reads
+    # this to name the packages in its start report, which is the difference
+    # between "a build is running" and "your package is in this build".
+    printf '%s\n' "${packages[@]}" >"$state_file"
     print_success "${mirror^} needs building (${#packages[@]} packages)"
     print_info "Packages: ${packages[*]}"
     print_info "State file created: $state_file"

bin/release

@@ -106,8 +106,20 @@ fi
 # so the list has to be taken while they are still there.
 BUILT_FILES=""
 
+# What the scheduled version check queued, when it was the one that asked for
+# this run. Absent for a manual run, which is fine — the report just omits it.
+QUEUED_PACKAGES=""
+QUEUE_FILE="${OMARCHY_STATE_DIR:-/root/.state}/.sync-needed-$MIRROR"
+[[ -s "$QUEUE_FILE" ]] && QUEUED_PACKAGES=$(grep -c '' "$QUEUE_FILE")
+
 if [[ "$DRY_RUN" != true ]]; then
-  notify_start "Release started: $MIRROR" "$RELEASE_CONTEXT"
+  start_details="$RELEASE_CONTEXT"
+  if [[ -n "$QUEUED_PACKAGES" && "$QUEUED_PACKAGES" != "0" ]]; then
+    start_details+="<br><br><strong>$QUEUED_PACKAGES package(s) queued:</strong><br>"
+    start_details+="$(head -25 "$QUEUE_FILE" | tr '\n' ' ' | basecamp_html_escape)"
+    ((QUEUED_PACKAGES > 25)) && start_details+=" …and $((QUEUED_PACKAGES - 25)) more"
+  fi
+  notify_start "Release started: $MIRROR" "$start_details"
 fi
 
 # Step 1: Build
@@ -217,8 +229,8 @@ if ((BUILT_COUNT > 0)); then
   summary+="<br><br>Live at https://pkgs.omarchy.org/$MIRROR/$ARCH/"
   notify_success "Release published: $MIRROR" "$summary"
 else
-  # Nothing to build usually means a queued run raced another that already did
-  # the work. Worth saying, but not worth dressing up as a publish.
-  summary+="<br>No packages needed building — the channel was already current."
-  notify_info "Release complete (no changes): $MIRROR" "$summary"
+  # Deliberately silent in chat: a run that published nothing is not news, and
+  # at a 5-minute cadence those messages would bury the ones that matter. The
+  # log and `bin/repo timers` still show the run happened.
+  print_info "Nothing was published — the channel was already current"
 fi