diff --git a/02-DECISIONS/0258-a-desk-click-performs-only-an-acknowledgement-and-an-answer-is-a-one-time-ticket.md b/02-DECISIONS/0258-a-desk-click-performs-only-an-acknowledgement-and-an-answer-is-a-one-time-ticket.md
index 3ab170e0..1bb6bda8 100644
--- a/02-DECISIONS/0258-a-desk-click-performs-only-an-acknowledgement-and-an-answer-is-a-one-time-ticket.md
+++ b/02-DECISIONS/0258-a-desk-click-performs-only-an-acknowledgement-and-an-answer-is-a-one-time-ticket.md
@@ -47,7 +47,7 @@ ten-second notification or a restart of the notifier's bundle.
    silence answers only the condition it is offered on. A condition's actions outside the list are never
    offered, and a token for one is refused without a call. The controller offers no other action.
    **Release, stop, start and restart are said in words, with where to give them**: "Needs you: release it,
-   or stop it, from the mesh console; this notification cannot do it." This lasts until to-be 46 phases 5
+   or stop it, from the mesh MCP server; this notification cannot do it." This lasts until to-be 46 phases 5
    and 6 authorise answers. It replaces ADR 0253 §6's reading of *acknowledge* and its promise to honour a
    tier.
    **Data loss is never silenced from a notification.** A condition that says data is gone or shrank offers
@@ -81,9 +81,14 @@ ten-second notification or a restart of the notifier's bundle.
    holder keeps its answers under a new name (`grants`), so such a record loads with its old tokens dropped,
    and a click on one of them is refused and said.
 
+> **Progressive insight — 2026-10-08.** The words named "the mesh console" as where an answer no notification
+> can give is given. The glossary retires "console"; the place is the mesh MCP server, and the words now say
+> "from the mesh MCP server; this notification cannot do it." (novox/mesh-controller PR #147). What was
+> decided is unchanged.
+
 ## Consequences
 
-- The delivery-waiting popup past its bound reads "Needs you: start it, or stop it, from the mesh console;
+- The delivery-waiting popup past its bound reads "Needs you: start it, or stop it, from the mesh MCP server;
   this notification cannot do it. …" and offers Details only. Starting or stopping it is not possible from
   the desk until phase 5. That is the honest state, and the words say where the decision lies.
 - Failed services nobody manages still offer Silence for a week. Data that shrank or went offers none.
@@ -120,7 +125,7 @@ ten-second notification or a restart of the notifier's bundle.
   - `cmd/mesh-controller/plain_words_test.go`: the module, held-delivery and waiting conditions offer no
     answer; the relogin words and the kind `relogin-needed` (ADR 0254) are held to the plain rule; a silence
     with the cause `operator-answer` does not count toward a healer wanted, and one by hand still does;
-    "Needs you" without a button names the mesh console, and data loss offers no silence.
+    "Needs you" without a button names the mesh MCP server, and data loss offers no silence.
 
 ## References