fab131a366
Review follow-ups on the context provenance row: - the producer name now follows ToolRow's aria-hidden separator dot instead of a literal middot inside the text, so the two disclosure rows expose one accessible-name shape; - the English steering caption becomes the noun `Interjection`, parallel to the Chinese 插话 and to the label this bubble carried before; - the history fold gets its own provenance assertion, so the mapping it declares separately from TranscriptAdapter is pinned on both sides; - the superseded-in-part bullet on the no-interjection-chrome note now enumerates the third Decision bullet too, whose no-badge and no-IconActions clauses had both lapsed.
53 lines
2.6 KiB
Markdown
53 lines
2.6 KiB
Markdown
- banner:
|
|
- navigation "Session hierarchy":
|
|
- button "Ask a research subagent to"
|
|
- text: /
|
|
- button "event-sourcing researcher" [disabled]
|
|
- button "1 subagent":
|
|
- text: 1 subagent
|
|
- img
|
|
- tablist:
|
|
- tab "Chat" [selected]
|
|
- tab "Trajectory"
|
|
- text: Explain event sourcing in one sentence. {{clock}}
|
|
- button "Copy":
|
|
- img
|
|
- button "Branch into a new conversation" [disabled]:
|
|
- img
|
|
- text: Available only on the last message of a completed turn
|
|
- button "Context injection @deepseek-ai/dsh-system-prompt":
|
|
- img
|
|
- img
|
|
- text: Context injection @deepseek-ai/dsh-system-prompt
|
|
- 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}}Ran for {{duration}} Now give the same explanation to a human reader. {{clock}}
|
|
- button "Copy":
|
|
- img
|
|
- button "Branch into a new conversation" [disabled]:
|
|
- img
|
|
- text: Available only on the last message of a completed turn
|
|
- 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}}Ran for {{duration}}
|
|
- 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
|