The pairing code appears when you open the panel; one size for section headings

distinct_server/presentation.py

@@ -1726,7 +1726,24 @@ details[open] .c-libhelp__toggle::after{content:" -";}
 .c-tail .gradio-accordion, .c-tail details{background:var(--c-surface);
   border:1px solid var(--c-hairline) !important; border-radius:var(--r-lg) !important;
   padding:var(--s3) var(--s4) !important; margin-bottom:var(--s4) !important;}
-.c-tail .label-wrap span{font-weight:650 !important; font-size:var(--t-lg) !important;}
+/* SECTION HEADINGS ARE ONE HEADING, AT ONE SIZE, ON ONE EDGE.
+   A title that wrapped to two lines came out centred and a size larger than
+   its neighbour, so two headings doing the same job looked like two different
+   kinds of thing. Everything here is stated rather than inherited: the size,
+   the weight, the alignment, and the fact that the title takes the row and
+   the chevron keeps its corner. */
+.c-tail .label-wrap{text-align:left !important; gap:var(--s3) !important;
+                    align-items:center !important;}
+.c-tail .label-wrap span{font-weight:650 !important; font-size:var(--t-lg) !important;
+                         line-height:1.35 !important; text-align:left !important;
+                         flex:1 1 auto !important; min-width:0 !important;
+                         color:var(--c-text) !important;}
+.c-tail .label-wrap::after{align-self:center !important;}
+@media (max-width:700px){
+  /* A long heading on a narrow screen is set at the body size rather than
+     wrapping three words onto three lines at display size. */
+  .c-tail .label-wrap span{font-size:var(--t-body) !important;}
+}
 /* One shadow language everywhere. */
 .c-grade-card,.c-panel,.c-legend,.c-workers article{box-shadow:none !important;}
 /* Inputs: quiet until focused. */

distinct_server/ui.py

@@ -3461,17 +3461,17 @@ class DistinctUI:
                 with gr.Column(elem_classes="c-tail"):
                     with gr.Accordion(
                         "Run a community agent", open=False, elem_id="join-agent"
-                    ):
+                    ) as join_section:
                         gr.Markdown(
                             # "The agent owns its bounded FIFO and reports it
                             # on every poll" is true and is a sentence for
                             # somebody reading the queue implementation. The
                             # person here is about to run a worker on their own
                             # machine and wants to know what it will do.
-                            "Download a build, generate a pairing code, then start the "
-                            "worker. It takes a fixed number of requests at a time, runs "
-                            "them one after another, and tells this server how many are "
-                            "waiting."
+                            "Run the worker on your own machine and it joins this "
+                            "server. It takes a fixed number of requests at a time, "
+                            "runs them one after another, and tells this server how "
+                            "many are waiting."
                         )
                         # The address and the code, filled in. This used to be
                         # a command with the word SERVER in the middle of it,
@@ -3490,10 +3490,29 @@ class DistinctUI:
                         # is Python and always was; the panel above now says
                         # so, and the only control left is the one that mints
                         # the code those instructions need.
-                        with gr.Row(elem_classes="c-tail__row"):
-                            create_code = gr.Button(
-                                "Generate pairing code", variant="primary", scale=0
-                            )
+                        # NO BUTTON TO ASK FOR THE CODE. IT IS THERE WHEN YOU LOOK.
+                        #
+                        # Nobody opens this panel for any reason other than to
+                        # attach a worker, so making them press a button to
+                        # request the one thing the panel exists to give was
+                        # ceremony rather than consent. Opening the section
+                        # mints it, the way a router has its password printed
+                        # on the box instead of a button to request one.
+                        #
+                        # It stays SERVER-issued, and that part is not
+                        # ceremony: this code is what proves an arriving
+                        # worker was invited by whoever owns this server. A
+                        # code the worker invented would prove nothing, and
+                        # anyone could then attach a machine to anyone's
+                        # server. The code the *worker* makes is the other
+                        # one — the access code it prints once paired, which
+                        # is what you hand to the people you want to let use
+                        # your machine, and which any number of them can
+                        # redeem.
+                        refresh_code = gr.Button(
+                            "New code", size="sm", variant="secondary", scale=0,
+                            elem_classes="c-join__refresh",
+                        )
 
                     with gr.Accordion("Model assessments and their sources", open=False):
                         gr.HTML(
@@ -3791,7 +3810,11 @@ class DistinctUI:
                 queue=False,
                 api_visibility="private",
             )
-            create_code.click(
+            # Opening the section is the request; there is nothing else to ask
+            # for in here. The small "New code" control stays for the one case
+            # somebody genuinely wants a second one: the first has expired or
+            # has already been used.
+            join_section.expand(
                 self.pairing_code,
                 inputs=[session_state],
                 # Into the panel, so the address and the code appear in one
@@ -3800,6 +3823,13 @@ class DistinctUI:
                 queue=False,
                 api_visibility="private",
             )
+            refresh_code.click(
+                self.pairing_code,
+                inputs=[session_state],
+                outputs=[join_panel],
+                queue=False,
+                api_visibility="private",
+            )
             # Two seconds, not five. The activity panel counts elapsed time
             # and streams the worker's steps, and a spinner that updates
             # every five seconds reads as a stall. The refresh is in-memory

scripts/live_e2e.py

@@ -412,8 +412,15 @@ def open_section(page, title: str) -> None:
 
 
 def generate_pairing_code(page) -> str:
+    """Open the section and read the code it mints.
+
+    There is no button to press any more: opening the panel is the request,
+    because attaching a worker is the only reason anybody opens it. This
+    helper is left with the same name and contract so every caller reads the
+    same way.
+    """
+
     open_section(page, "Run a community agent")
-    page.get_by_role("button", name=re.compile("Generate pairing code", re.I)).click(timeout=20000)
     page.wait_for_timeout(3000)
     text = page.inner_text("body")
     # The code is groups of upper-case characters joined by hyphens. Anchored