docs(rss-bridge): the green install-test reproduced, so say "twice" rather than "one run"

The previous commit recorded the install-test going green and hedged it
with "it is one run". Pushing that commit produced a second run, on a
second commit, and it was green too - run 792 job 2623 (1m10s) and run 794
job 2638 (1m14s), both with the chart genuinely in the matrix.

So the hedge was understated in one direction and the real caution lies
elsewhere. Corrected to say what is actually true: it reproduced over two
consecutive runs, so it is not a fluke - and nobody has identified what
changed on the runner, which is the reason #51 stays open. A green test
does not explain itself, and the diagnostic programme in that issue's body
(docker info on the runner for userns and the dind configuration, the same
image in a local k3d without remapping) remains unexecuted.

"Close an issue on a cause, not on a colour" is unaffected by the count.

ci/httproute/rss-bridge.yaml

@@ -27,8 +27,9 @@
 # this overlay it PASSED: pod 1/1 Ready in 22s, 0 restarts, no permission error
 # 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. One run is not
-# proof of permanence, so #51 is not closed on the strength of a colour.
+# 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.
 #
 # 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