fix(web): reconcile rebased subagent contracts

apps/web/tests/core-web-profile.snapshot.ts

@@ -72,6 +72,7 @@ describe('core Web profile', () => {
         "tools": [
           "bash",
           "str_replace_editor",
+          "list_agents",
         ],
       }
     `)

apps/web/tests/shipped-composition.e2e.ts

@@ -28,6 +28,7 @@ const EXPECTED_TOOLS = [
   'edit',
   'exit_plan_mode',
   'get_goal',
+  'list_agents',
   'ralph',
   'read',
   'send_message',

apps/web/tests/snapshots/subagent-conversation/ui.expected.md

@@ -1,43 +1,47 @@
 - banner:
-  - navigation "Session hierarchy":
-    - button "Ask a research subagent to"
-    - text: /
-    - button "event-sourcing researcher" [disabled]
-    - text: · 2 turns
+  - heading "event-sourcing researcher" [level=1]
   - button "1 个子代理":
     - text: 1 个子代理
     - img
   - tablist:
     - tab "Chat" [selected]
     - tab "Trajectory"
-    - tab "Waterfall"
-- text: Explain event sourcing in one sentence.
-- button "复制":
+- text: Explain event sourcing in one sentence. {{clock}}
+- button "Copy":
   - img
-- button "在新对话中分支":
+- button "Branch into a new conversation":
   - img
-- button "编辑":
+- button "Context injection":
   - img
+  - img
+  - text: Context injection
 - button "Think The user is asking for a one-sentence description of event sourcing. This is a straightforward knowledge question that doesn't require any skill loading or tool calls.":
+  - img
   - img
   - text: Think The user is asking for a one-sentence description of event sourcing. This is a straightforward knowledge question that doesn't require any skill loading or tool calls.
 - paragraph: Event sourcing is a pattern where all changes to an application's state are stored as an immutable, append-only sequence of events, rather than persisting only the current state, enabling full auditability, temporal queries, and event-driven architectures.
-- text: Now give the same explanation to a human reader.
-- button "复制":
+- button "Copy":
   - img
-- button "在新对话中分支":
+- button "Branch into a new conversation":
   - img
-- button "编辑":
+- text: {{clock}} Now give the same explanation to a human reader. {{clock}}
+- button "Copy":
+  - img
+- button "Branch into a new conversation":
   - img
 - button "Think The user is asking for a one-sentence description of event sourcing. This is a straightforward knowledge question that doesn't require any skill loading or tool calls.":
+  - img
   - img
   - text: Think The user is asking for a one-sentence description of event sourcing. This is a straightforward knowledge question that doesn't require any skill loading or tool calls.
 - paragraph: Event sourcing is a pattern where all changes to an application's state are stored as an immutable, append-only sequence of events, rather than persisting only the current state, enabling full auditability, temporal queries, and event-driven architectures.
-- text: cache hit 99% · 15,738 tokens · 2 turns · 2 steps
+- button "Copy":
+  - img
+- button "Branch into a new conversation":
+  - img
+- text: {{clock}}
 - textbox "Message the agent"
-- button "Add attachment":
+- button "Commands":
   - img
-- combobox "Access mode":
-  - option "Read-only" [selected]
-  - option "Read-write"
+- 'button "Access mode, current: Full access"': Full access
 - button "Send message" [disabled]
+- text: 2 turns · 2 steps Context 6% of 128K Cache hit 99% Input 15.6K tok · Output 158 tok