fix tracker refs flagged by check-issue-refs.sh

Reworded the two hits scripts/check-issue-refs.sh found — a bare hash-
number tag in .forgejo/workflows/ci.yml's push-trigger comment and a
hyperhive#4345 tag in matrix_account.rs's doc comment — into prose that
stands on its own, per the lint's own rule. Neither carried semantic
weight beyond what the prose already says once reworded.

Refs #4345

.forgejo/workflows/ci.yml

@@ -1,7 +1,7 @@
 name: CI
 
 on:
-  # No `push` trigger, so nothing re-validates a merge commit on main — an accepted infra-load tradeoff (mara, #3938, 2026-09-16), not an oversight.
+  # No `push` trigger, so nothing re-validates a merge commit on main — an accepted infra-load tradeoff mara signed off on, not an oversight.
   pull_request:
     branches: ["**"]
   # Lets `hive-forge ci-rerun` re-trigger CI via workflow-dispatch API

swarm-controller/src/matrix_account.rs

@@ -42,8 +42,8 @@ fn default_mode() -> String {
 /// directly — see that fn's doc.
 ///
 /// Not yet consulted by [`put_matrix_account`]: `homeserver_or_configured_default`
-/// below exists for a later slice of hyperhive#4345 to call; this one only
-/// wires the config through.
+/// below exists for a later slice of this homeserver-default rollout to
+/// call; this one only wires the config through.
 pub(crate) const DEFAULT_HOMESERVER_ENV: &str = "SWARM_CONTROLLER_MATRIX_HOMESERVER_URL";
 
 /// `caller`'s own homeserver, or `default` when the caller left it unset.