A reply can stop and ask you something

Three features turn out to be one mechanism: a command waiting to be
approved, a question the model wants answered, and "this reply is waiting
for you" are all — stop the generation, put an interactive block in the
bubble, wait for a POST, carry on. So there is one primitive, and the only
thing using it so far is `ask_user`: a model can offer you a few answers
and a box to write your own.

The shell executor is not here yet. This lands first on purpose, because
it is the riskiest machinery in the feature and it is worth having working
before any subprocess exists to complicate it.

Two things about where the pause sits. It pauses a round, not a call: a
round's calls run together under a semaphore, and parking four coroutines
on four separate answers inside that gather would queue them behind each
other invisibly. And Stop had to be taught about it — `cancel` is read
between streamed chunks and there are no chunks while paused, so the
button did nothing at all until `request_stop` learned to resolve the
pause itself.

Also here: a risk class on every tool (read, write, execute), which is
what the four permission modes will be a table over, and the systemd unit
loses ProtectKernelTunables. That last one is not tidying — it
bind-mounts /proc/sys read-only, which stops bubblewrap mounting /proc at
all, and the obvious workaround would expose this process's environment
and with it the encryption key.

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

src/lembas/services/mcp/registry.py

@@ -27,7 +27,7 @@ from lembas.services import tool_access
 from lembas.services.fetch import FetchError
 from lembas.services.mcp import client
 from lembas.services.mcp.protocol import McpError
-from lembas.services.tools import FAMILY_MCP, ToolContext, ToolDef, ToolOutcome
+from lembas.services.tools import FAMILY_MCP, RISK_WRITE, ToolContext, ToolDef, ToolOutcome
 
 log = logging.getLogger(__name__)
 
@@ -138,6 +138,11 @@ def tool_defs(
                     description=entry.get("description") or f"{name}, from {server.name}.",
                     parameters=entry.get("schema") or {"type": "object", "properties": {}},
                     run=_runner(spec, name, offered),
+                    # Conservative, because nothing in tools/list says. A server
+                    # calling something `search` may still be filing a ticket
+                    # with it, and the cost of being wrong this way is a
+                    # question nobody needed to answer.
+                    risk=RISK_WRITE,
                 )
             )