Files
deepseek-harness/apps/web/tests/snapshots/subagent-conversation/ui.expected.md
T
Tianyi Cui 5c98cbd8f6 test(web): run the subagent-conversation e2e against the locale-aware copy
The ui-subagent catalog and read-only composer copy moved from hardcoded
Chinese to the locale-aware `subagent` namespace, so an en-US headless
browser now renders English. The e2e's selectors and goldens still
asserted the old hardcoded Chinese strings, leaving the scenario unable
to find the catalog trigger.

Convert the selectors to the default (en-US) render and re-record the
catalog goldens (ui, tree, nested) in English. The locale-aware parts of
the remaining goldens were already English (recorded under the en-US
default), so sidebar and fork are untouched.
2026-08-02 14:05:37 +08:00

2.3 KiB

  • banner:
    • navigation "Session hierarchy":
      • button "Ask a research subagent to"
      • text: /
      • button "event-sourcing researcher" [disabled]
    • button "1 subagents":
      • text: 1 subagents
      • img
    • tablist:
      • tab "Chat" [selected]
      • tab "Trajectory"
  • text: Explain event sourcing in one sentence. {{clock}}
  • button "Copy":
    • img
  • button "Branch into a new conversation":
    • img
  • 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.
  • button "Copy":
    • img
  • button "Branch into a new conversation":
    • img
  • 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.
  • button "Copy":
    • img
  • button "Branch into a new conversation":
    • img
  • text: {{clock}}
  • textbox "Message the agent"
  • button "Commands":
    • img
  • 'button "Access mode, current: Workspace Write"': Workspace Write
  • button "Send message" [disabled]
  • text: 2 turns · 2 steps Context 6% of 128K Cache hit 99% Input 15.6K tok · Output 158 tok