Artifact b40a95ea3bd8514c26d0777fcd4afe41d724d42195052e0917d58d5ba7712d0f:
- File
internal/web/opsdoor_test.go
-
2026-08-25 21:46:49
— part of check-in
[3314daeff6]
on branch ops-drill
— ops: a door from /fleet, and a test that it stays
/fleet/ops linked OUT to /fleet seven times and nothing anywhere linked IN. The page was live, gated, and reachable only by typing the URL.
Second surface to ship that way after the notes feed, so it gets a test rather than a promise to remember — both directions, so an admin is never stranded on either.
The link goes in the summary strip that already carries the fleet's counts and the error badge, which is where somebody reading health already is. /fleet answers 'are my repositories healthy'; /fleet/ops answers 'is the forge healthy'. (user: dmestas, size: 1153) [annotate] [blame] [check-ins using]
- 2026-08-25 21:53:53 — part of check-in [7059271e59] on branch trunk — Accepted. It can now say which repo and which calls — which is the difference between finding a slow route and fixing one. (user: dmestas, size: 1153) [annotate] [blame] [check-ins using]
-
2026-08-25 21:46:49
— part of check-in
[3314daeff6]
on branch ops-drill
— ops: a door from /fleet, and a test that it stays