- Shipped
- August 25, 2026 at 5:41 PM UTC
- Author
- Kamo
- Commit
- 4f4e321
**************** has been failing on main since ba3f85c. DesktopProbeController#probe is not unguarded — it checks X-Internal-Auth through authorized(auth), constant-time, failing closed when the secret is unconfigured — but the header is a method parameter rather than a call in the body, so the coarse one-method scan cannot see it. That is the limitation the test documents, and **************** and **************** are already baselined for the same reason. Worth saying out loud in the comment for this one: the probe's response body embeds a working SSO link for the desktop, so an unauthenticated "is the desktop up" endpoint would hand out logins. The guard is real and load-bearing. Java CI runs with -DskipTests, so a red repo still deploys — which is exactly why a security ratchet left red goes unnoticed.