Work handed to a second model, which may not ask

subagent_run gives a self-contained piece of work to a helper carrying the
parent's connection, directory, model and effort, and hands its answer back as
the tool result. The mechanism is the one scheduled runs already use -- a hidden
chat, one turn, wake_chat, and a poll -- so tools, rounds, budgets, metrics and
steps all work with no second implementation. The two alternatives were
rejected where they had already been rejected once: a nested Generation is two
replies writing one transcript, and a one-shot complete() has no tools, which
schedule/runner.py records as useless for exactly this case.

Every restriction is a property of the child's row, applied by resolve_tools
after the gates, because a rule that lives in a system message is one a page the
model just read can argue with. No questions, no recursion, nothing that writes
unless the call asked for it and the parent's own mode would not have stopped
first, and commands only from a fixed read-only list -- in every mode including
Auto, because the task text can have come from a page.

Withdrawing ask_user turned out to be half of "nobody is watching". An approval
still built a card nobody could see and parked the reply until approval_timeout,
which from every screen is the feature not working. Chat.unattended is the
question now, and not the kind: _authorise answers with a refusal instead. A
scheduled task's chat had the same hole and is covered by the same flag.

Three bounds, counted where each is knowable: per reply on the parent's
Generation, instance-wide in a set a restart clears, and per helper in settings
of its own so one runs out of room long before the reply that asked. Past the
clock the helper is stopped rather than abandoned, so a partial answer comes
back with a sentence saying so.

Also: four gates had shipped into the scope menu with no name, taking the first
tool's label instead -- the canvas switch read "Canvas written". There is a test
that refuses a family without one.

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

src/lembas/services/tool_labels.py

@@ -72,6 +72,8 @@ LABELS: dict[str, str] = {
     "schedule_list": "Schedules read",
     "schedule_update": "Schedule changed",
     "schedule_cancel": "Schedule stopped",
+    # Work handed to a second model.
+    "subagent_run": "Helper",
     "memory_add": "Memory saved",
     "memory_forget": "Memory removed",
     "skill_get": "Skill read",
@@ -112,6 +114,7 @@ ICONS: dict[str, str] = {
     "schedule_list": "clock",
     "schedule_update": "clock",
     "schedule_cancel": "stop-circle",
+    "subagent_run": "sparkle",
     "memory_add": "star",
     "memory_forget": "trash",
     "skill_get": "sparkle",
@@ -156,6 +159,7 @@ ACTIONS: dict[str, str] = {
     "schedule_create": "Set up a schedule",
     "schedule_update": "Change a schedule",
     "schedule_cancel": "Stop a schedule",
+    "subagent_run": "Send a helper",
     "memory_add": "Remember something",
     "memory_forget": "Forget something",
     "skill_get": "Read a skill",
@@ -193,6 +197,10 @@ DETAIL_KEYS: dict[str, str] = {
     # timing is an object, and the tool answers with it in words afterwards,
     # which is where it is actually checkable.
     "schedule_create": "instruction",
+    # The task, not the title. It is the thing a helper is actually sent, and
+    # the one field worth correcting before it goes -- a task with a wrong path
+    # in it comes back as a confident answer about the wrong thing.
+    "subagent_run": "task",
 }