docs: record runner CI rerun diagnostics

docs/operations/CI_RUNNER.md

@@ -247,4 +247,8 @@ does not include workflow step output. The Actions jobs API returns an empty
 list for completed run 49, so step details are not available through the
 current API account. The repository runner inventory API returns 403 to the
 current non-owner API account. PR #46 pins the narrow log ACL and its rotation
-hooks; this installer change has not been applied to the VPS.
+hooks; this installer change has not been applied to the VPS. On the updated
+PR head `7701e77`, CI run 51 also failed after task 303 was accepted, while
+smoke run 52 passed. The daemon log still exposes no job or step detail and
+the Actions jobs endpoint is empty for run 51, so its failure remains
+unattributed.

docs/operations/CURRENT_STATE.md

@@ -142,6 +142,12 @@ unverified.
   endpoint returns an empty list for completed run 49; the current API account
   cannot use the owner-only jobs endpoint to obtain the log download ID. The
   exact failing step is undetermined.
+- After pushing PR #46 commit `7701e77`, CI run 51 accepted task 303 at
+  2026-10-15 01:48:05 +05 and failed 13 seconds later; smoke run 52 accepted
+  task 304 and succeeded. The runner daemon log again contains only task
+  dispatch lines. Gitea returns no jobs for run 303, and the owner-only jobs
+  endpoint remains unavailable to the current API account, so run 51's failed
+  step is also undetermined. This repeated result does not establish a cause.
 - An isolated local Compose smoke test built backend/OpenSearch images,
   reached healthy status for OpenSearch, backend, and Caddy, and returned HTTP
   200 for `/review` through Caddy. Its containers, networks, and volumes were