fix(web): Run column shows run_id, the real global progressive

run.number only counts within its own repo/workflow -- meaningless once
the admin endpoint mixes every repo into one list, and already not what
the row order is sorted by. run_id is Gitea's actual instance-wide,
strictly-increasing id, so the displayed number now agrees with "most
recent globally". The link still goes to Gitea's own per-repo run page
(html_url); only the label text changed.

docs/WEB-UI.md

@@ -359,6 +359,15 @@ table is wide as a result — 13 columns — and scrolls horizontally inside the
 card's own `.table-wrap` rather than the page, same as the other wide tables
 (Templates, Services).
 
+**Run shows `run_id`, not the per-repo `#N`.** Gitea's `run_number` only
+counts within its own repo/workflow, so it is meaningless once the admin
+endpoint mixes every repo on the instance into one list; `run_id` is Gitea's
+own instance-wide, strictly-increasing id, which is what "global recency"
+above is sorted on too, so the number in the column and the row order agree.
+The cell still links out to Gitea's own run page (`html_url`, which Gitea
+builds from the per-repo number internally) — only the *displayed* text
+changed.
+
 **Started is click-to-toggle.** It renders relative ("2h ago") by default;
 clicking swaps to the absolute local timestamp, and clicking again swaps
 back. Both strings are pre-rendered server-side into the button's