Hide the servers block too, now that nothing sends a request

With the Try it out buttons gone, the block is a dropdown and two text fields
whose only effect is to recompute a URL and print it. Nothing sends that URL
anywhere, so it just invites a reader to edit fields that do nothing.

Nothing readable goes with it. Swagger UI renders neither a server's
description nor its variables', so the note on `port` - Android's 8080, iOS's
80, the walk to 8081, `remoteAccessPort` - has never actually appeared on the
page; the block showed only the URL template and two bare labels. The page now
carries the address shape and the two default ports in the admonition, where a
reader will see them, and links to the introduction for the rest.

`servers:` stays in openapi.yaml - it is part of the specification whether or
not Swagger UI draws it - with a comment recording that its descriptions reach
no reader, so nobody writes documentation there again expecting them to.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Staacks

docs/assets/stylesheets/swagger-ui-overrides.css

@@ -40,3 +40,19 @@
 .swagger-ui .renderedMarkdown pre > code {
   padding: 5px 7px;
 }
+
+/* The servers block is a control, not documentation: a dropdown and two text
+   fields whose only effect is to recompute a URL that is then displayed. With
+   no Try it out buttons there is nothing to send it to, so all it does is
+   invite a reader to edit fields that do nothing.
+
+   Nothing readable is lost by hiding it. Swagger UI renders neither a server's
+   `description` nor its variables' - the note on `port` about Android's 8080,
+   iOS's 80, the walk to 8081 and `remoteAccessPort` has never appeared on the
+   page - so the block shows only the URL template and two bare labels. What
+   those descriptions say is in the admonition on api-reference.md and in the
+   introduction. `servers:` itself stays in openapi.yaml, where it is part of
+   the specification whether or not Swagger UI draws it. */
+.swagger-ui .scheme-container {
+  display: none;
+}

docs/remote-interface/api-reference.md

@@ -14,6 +14,8 @@ implementations, and everything below — including the interactive requests —
 
     Use the reference below to build the request, and send it with `curl`, a browser tab or
     your own code: enable remote access in phyphox, and use the address the app shows you.
-    The server block below gives the shape of that URL.
+    Every path below hangs off that address — `http://192.168.0.42:8080/get` on Android,
+    where 8080 is the default port; on iOS the default is 80 and can usually be left out.
+    The [introduction](index.md) covers how the requests fit together.
 
 <swagger-ui src="openapi.yaml"/>

docs/remote-interface/openapi.yaml

@@ -88,6 +88,12 @@ info:
     name: GNU GPL v3
     identifier: GPL-3.0-only
 
+# Swagger UI renders neither of the descriptions below - not the server's and
+# not its variables' - so none of this reaches a reader of the API reference
+# page, and the block itself is hidden there (see the note in
+# ../assets/stylesheets/swagger-ui-overrides.css). Keep it accurate anyway: it
+# is part of the specification, and other consumers do read it. Documentation
+# that readers must see belongs in `info.description` or on the page.
 servers:
   - url: http://{host}:{port}
     description: A phone running phyphox with remote access enabled.