`dsh` shipped two config trees that were 43 rows the same: apps/cli/cordis.yml composed web as 74 flat rows, while the TUI booted examples/tui-agent/cordis.yml whose single `@deepseek-ai/dsh-tui-demo` row mounted twelve plugins behind a twenty-key pass-through Config. Neither file was what its location claimed — apps/cli hardcoded the "example" as the product default and the "demo" bundle was the application — and every capability change had to be made twice. - apps/cli/base.cordis.yml holds the 43 shared rows; tui.cordis.yml and web.cordis.yml are patch lists stating only what differs per surface - overlays apply as SIBLING patch lists at one include level, because include patches never cross an include boundary. Precedence: base < surface < (--config | personal ~/.dsh/config.yaml) < launcher flag/profile patches - `--config` now applies an overlay INSTEAD OF the personal one, so a demo or test tree never inherits the user's route; new `--config-replace` boots a file as the entire tree (the old `--config` behaviour). Both survive /resume - vendor/include: index each `insert`ed row as it is added so a later patch can configure or disable it. Upstream built the id index once before the patch loop, leaving every surface-only row — the whole TUI front door — silently unpatchable from user config. Logged as local modification 8 - session identity moves to dsh-agent-loop's CONFIGURED_AGENT_IDENTITIES_KEY; dsh-tui's MAIN_SESSION_ID_KEY is deleted (only the bundle read it) - delete examples/tui-agent, examples/cordis-agent, packages/examples/tui-demo; TUI tests → apps/cli/tests, cordis e2e → packages/cordis/tool-cordis/tests, examples/code-mode survives as an overlay leaf - `dsh web` gains --config, threaded into AppCLIEntry as an extra overlay Three latent defects surfaced and are fixed here: the TUI captured the optional sessionQuery service once at construction and could permanently disable /resume when it won the mount race; the session-store root silently reverted to a project-local ./.sessions; --config-replace was dropped by the resume handoff. Verified by booting each tree through the real Loader (TUI 55 entries, web 75, zero unsettled) rather than reading YAML. All eight terminal snapshots replay byte-identically; 14/14 PTY smoke, 112/112 snapshots, 25/25 doc-sync, hygiene and lint clean.
87 lines
4.8 KiB
Plaintext
87 lines
4.8 KiB
Plaintext
terminal 100x36 buffer=normal length=43 base=7 viewport=7
|
|
lifecycle started=1 stopped=0 progress=inactive
|
|
title "Use the workflow tool exactly — DSH TUI snapshot"
|
|
cursor hidden column=7 viewportRow=35 bufferRow=42
|
|
buffer
|
|
0| " DEEPSEEK HARNESS"
|
|
style 1-8 fg=bright-magenta bold
|
|
style 10-16 bold
|
|
1| " Use the workflow tool exactly"
|
|
style 1-29 dim
|
|
2| " main-session"
|
|
style 1-12 dim
|
|
3| <blank>
|
|
4| "You "
|
|
style 0-2 fg=bright-magenta bold underline
|
|
5| "Use the workflow tool exactly once, with args omitted, meta set to { \"name\": \"snapshot-flow\", "
|
|
6| "\"description\": \"one child for the snapshot\" }, and this EXACT script body (copy it verbatim): "
|
|
7| "phase('Run') "
|
|
8| "const reply = await agent('Reply with exactly the word WF_CHILD_OK and nothing else.') "
|
|
9| "return { reply } "
|
|
10| "After the workflow returns, reply with the single word WORKFLOW_DONE and stop. Do not use any other "
|
|
11| "tool. "
|
|
12| <blank>
|
|
13| "Assistant "
|
|
style 0-8 fg=bright-magenta bold underline
|
|
14| "Reasoning "
|
|
style 0-8 dim italic
|
|
15| "The user wants me to use the workflow tool exactly once with specific parameters. Let me carefully "
|
|
style 0-99 dim italic
|
|
16| "follow the instructions: "
|
|
style 0-23 dim italic
|
|
17| " "
|
|
18| "1. args omitted (so I don't include it) "
|
|
style 0-2 fg=bright-magenta
|
|
style 3-38 dim italic
|
|
19| "2. meta = { \"name\": \"snapshot-flow\", \"description\": \"one child for the snapshot\" } "
|
|
style 0-2 fg=bright-magenta
|
|
style 3-81 dim italic
|
|
20| "3. script = as given verbatim "
|
|
style 0-2 fg=bright-magenta
|
|
style 3-28 dim italic
|
|
21| "4. After it returns, reply with \"WORKFLOW_DONE\" "
|
|
style 0-2 fg=bright-magenta
|
|
style 3-46 dim italic
|
|
22| " "
|
|
23| "Let me do exactly that. "
|
|
style 0-22 dim italic
|
|
24| <blank>
|
|
25| "● Tool / workflow"
|
|
style 0-16 fg=green
|
|
26| "workflow: snapshot-flow "
|
|
style 0-99 dim
|
|
27| "workflow \"snapshot-flow\" completed (1 agent). "
|
|
style 0-99 dim
|
|
28| "Return value: "
|
|
style 0-99 dim
|
|
29| "{ "
|
|
style 0-99 dim
|
|
30| " \"reply\": \"WF_CHILD_OK\" "
|
|
style 0-99 dim
|
|
31| "} "
|
|
style 0-99 dim
|
|
32| "Model wait 0.0s · Completed 2026-07-21 12:00:00 "
|
|
style 0-46 dim
|
|
33| <blank>
|
|
34| "Assistant "
|
|
style 0-8 fg=bright-magenta bold underline
|
|
35| "Reasoning "
|
|
style 0-8 dim italic
|
|
36| "The workflow returned successfully with the reply \"WF_CHILD_OK\". Now I need to reply with exactly "
|
|
style 0-99 dim italic
|
|
37| "\"WORKFLOW_DONE\" and stop. "
|
|
style 0-24 dim italic
|
|
38| "WORKFLOW_DONE "
|
|
39| "Model wait 0.0s · Completed 2026-07-21 12:00:00 "
|
|
style 0-46 dim
|
|
40| <blank>
|
|
41| "/workspace/project deepseek-v4-flash ↑3.5k ↓227 cache 47% 3% context"
|
|
style 0-44 fg=bright-magenta bold
|
|
style 47-63 dim
|
|
style 66-86 dim
|
|
style 89-98 dim
|
|
42| " dsh ◍ "
|
|
style 1-3 fg=bright-magenta bold
|
|
style 5-6 dim
|
|
style 7-7 inverse
|