docs(rss-bridge): phrase the reproduced green without a run count

The count was pinned at "two consecutive runs" and a third green arrived
with the next push, which is a regress: every commit that records the
number invalidates it. Phrased as "every run of that branch since"
instead, which is stable, still establishes that it is not a fluke, and
cannot go stale in main.

The caution it carries is unchanged and is the one that matters: it is a
colour, not a cause. Nobody has identified what changed on the runner, and
#51's diagnostic programme is still unexecuted.

ci/httproute/rss-bridge.yaml

@@ -28,8 +28,9 @@
 # in the job. Since that PR's rendered defaults are byte-identical to
 # origin/main, the chart is ruled out as the cause and the runner is the
 # implicated layer - which is where #51 had already placed it. It reproduced
-# over two consecutive runs, but nobody has identified what changed there, so
-# #51 is not closed on the strength of a colour.
+# on every run of that branch since, so it is not a fluke; but nobody has
+# identified what changed on the runner, so #51 is not closed on the strength
+# of a colour.
 #
 # Either way this overlay stays load-bearing: the install-test installs the
 # INGRESS mode (that is what the fixture sets), so the Gateway mode of this