ci: revert the forced boot-check failure; the gate was seen to block the push (rule 177)

Run 8447 on b307f53: the boot check failed at the forced assertion, Push was
skipped, clean-up ran, :dev stayed on sha256:718d2ca (98854d9) and no
:b307f53 image exists in the registry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.forgejo/workflows/ci.yml

@@ -204,7 +204,7 @@ jobs:
           fetch /health | grep -q '"ok"'
 
           # tini is PID 1, so zombies are reaped and SIGTERM reaches Steward.
-          test "$(docker exec "$SMOKE-app" cat /proc/1/comm)" = "forced-failure-rule-177"
+          test "$(docker exec "$SMOKE-app" cat /proc/1/comm)" = "tini"
 
           # A fresh database lands on first-run setup: a real page, its assets
           # served by Steward itself, and no third-party host in it (rule 155).