@dsh-cove/dsh-web-all 0.0.0-stage → 0.4.3

package/presets/code-vibe.patch.yml

@@ -0,0 +1,325 @@
+# Bundled `code-vibe` preset for DSH 0.2. Its metadata, scoped composition,
+# and skill assets live in this package and are declared explicitly below.
+- insert:
+    - id: preset-code-vibe
+      name: '@deepseek-ai/dsh-agent-preset'
+      config:
+        id: code-vibe
+        name: 许愿式编程
+        description: 把高层产品愿望收敛为可运行、经过真实验收的软件；保留标准编码工具、计划、目标、子代理、工作流与技能目录。
+        order: 5
+        plugins:
+          # The `code-vibe` agent preset (许愿式编程 / wish programming): the standard
+          # coding tool set presented NATIVELY — the model sees every tool schema and
+          # calls tools one per action, NOT Code Mode's `run_code` program transport.
+          #
+          # The `tool-presentation` row below pins `mode: native` so this agent never
+          # inherits a deployment-wide `code`/`both` default. (The shipped `code` preset
+          # is the Code Mode variant; this preset is the native variant, with the
+          # wish-programming persona and skill layered on top.)
+          #
+          # The registry itself stays on the host plane — the agent loop's scheduler and
+          # the API proxy's presenters are its consumers — so what this preset owns is
+          # the PRESENTATION of that registry for this agent alone. Code Mode sessions
+          # run beside this native one in the same process, each seeing its own catalog.
+          #
+          # This file is an AGENT-PLANE composition. It is mounted under one agent's
+          # scope context, so every tool and prompt section it registers belongs to that
+          # session alone. The host composition (`base.cordis.yml` + `web.cordis.yml`)
+          # keeps everything a preset must not own: the registries themselves, the
+          # sandbox and approval stack, persistence, and the model route.
+          #
+          # A service row here MUST sit inside a group carrying an `isolate` realm.
+          # Without one it publishes into the root realm, where it is process-global
+          # rather than per-session and the second session mounting this preset collides
+          # with the first. `true` means an entry-local realm — one private instance per
+          # mounted session. A shared label would pool one instance across sessions.
+
+          # ── identity ────────────────────────────────────────────────────────────────
+
+          # The preset's own persona, shadowing the deployment default for this agent.
+          # `{{model}}` and `{{cwd}}` resolve from the agent's own route and workspace.
+          - id: persona
+            name: '@deepseek-ai/dsh-persona'
+            config:
+              # 0.1.6-alpha.1: field renamed text → prefix (required)
+              suffix: Your working directory is {{cwd}}.
+              prefix: |-
+                You are a wish-programming coding agent powered by the {{model}} model.
+
+                CORE COMMITMENTS (四条，冲突时优先于一切转述):
+                1. USER'S ORIGINAL WORDS ARE THE HIGHEST AUTHORITY: record them verbatim into docs/wish/<id>/quote.md at intake; downstream artifacts only quote and interpret; on conflict the original wins and goes back to the user. Qualitative words absent from the original (推倒重画/全部重做…) are 〔PM 推断〕 until confirmed.
+                2. YOU ARE THE FRONT-DESK PM: the user only talks to you; translate everything into user language (no engineering vocabulary without a plain explanation). Decision points put to the user are user-value trade-offs ONLY (新手 vs 老手、开放 vs 管控、快 vs 全) — permission/technical decisions stay inside.
+                3. User confirms BEFORE implementation delegation: --confirm/--approve --by <用户> comes from the user, never you (markers are audit records; the real gate is the user). Completion requires a runnable result + real acceptance evidence (multi-viewport screenshots), not a design or scaffold.
+                4. SELF-SERVICE BEFORE ESCALATION: exhaust .env*/seed/prior sessions/memoir/artifacts and technical verification (lint/typecheck/browser) BEFORE asking; escalate with ONE precise request when nothing exists; one blocked step never halts all tracks — park, continue, report in parallel.
+
+                FIRST ACTION on every task: run the product-understanding gate. For design-flavored wishes (页面/前端/设计/体验/对标/重设计/IA/迁移/拆分), BEFORE any implementation delegation, produce the three-part prelude and WAIT: ① quote the user's words verbatim side-by-side with your understanding, ② module-positioning request, ③ plan preview. Until confirmed, subagents only read.
+
+                SKILL LOADING — mandatory per task type (catalog is authoritative; verify_preset_budgets catches nonexistent names):
+                - building a system/app/tool/platform → load `wish-programming` BEFORE any other app-building skill. Its five stages are the process: 需求理解(不拆)→设计规范单(不拆+拍板)→实现(2~4 片 anchor 先行, 白名单禁发明)→机械验收(独立 deny-write agent)→用户 judge(真实渲染). Rejected ≥2 by user → mini-postmortem.
+                - 写任何文案/确认包/注释/README → `dsh-prose-standard`; 清理推理残留 → `dsh-trim-cot-leakage`.
+                - 删除/重构/既有代码判定 → `dsh-find-simplifications` (简化三态: 不可达/收窄/证据不足).
+                - 切片测试/验收 → `dsh-ci-test-reliability` (报告协议: 只报实跑命令; retries/skips never "passing").
+                - 模型路由/委托判据 → `agent-operation` (继承优先、同族换档; 绝不委托需求理解/设计决策/产品判断 — conductor 自己执行).
+                - design-flavored 愿望 → `frontend-design` (LOAD-MAP 硬门, 先于设计文档); 验收/走查/体验审计 → `quality-review` (先证伪再 Pass); 评审/merge 前 → `code-review`.
+
+                Workspace rule: selected workspace is the only authorized target; if unrelated, ask exactly one question for a dedicated workspace, then end the turn. Keep only four things resident: 需求原文/确认结论/语义不变量/模块进度摘要; push detail into artifacts. Delegate only what needs no context of yours (fresh context is an asset). Report progress by user-perceivable milestones. Never route to hosted builders/Lark/Feishu/Miaoda unless the user explicitly names that platform.
+          - id: agent-instructions
+            name: '@deepseek-ai/dsh-agent-instructions'
+            config:
+              maxBytes: 65536
+
+          # ── time context ────────────────────────────────────────────────────────────
+
+          # Opt-in per-step clock context. Backs the wish-programming timebox rule and
+          # the journey UPDATED_AT claims with a real sampled clock plus an elapsed-time
+          # baseline, instead of the model guessing wall time. Throttled to one injection
+          # per 60s so long runs do not pay a context message on every step; the browser
+          # zone is used when one unique zone is attached to the request, else the Node
+          # process zone. Remove this row to drop the added tokens entirely.
+          - id: time-context
+            name: '@deepseek-ai/dsh-time-context'
+            config:
+              refreshIntervalMs: 60000
+
+          # ── shell ───────────────────────────────────────────────────────────────────
+
+          # `shell-env` stays in the HOST composition: `apps/cli/src/web.ts` injects it to
+          # publish `DSH_WEB_URL`/`DSH_WEB_MODE`, and a host row that injects a service is
+          # the criterion for host-plane ownership — injection resolves before any session
+          # exists, so there is no agent to key by. Behind a preset realm those variables
+          # never reached the model's shell at all. Both shell tools consume the host
+          # registry from here; their executors (`bash-sandbox`/`pwsh-sandbox`) are
+          # host-plane too.
+          - id: tool-bash
+            name: '@deepseek-ai/dsh-tool-bash'
+            disabled: !!js process.platform === 'win32'
+
+          - id: tool-pwsh
+            name: '@deepseek-ai/dsh-tool-pwsh'
+            disabled: !!js process.platform !== 'win32'
+
+          # ── filesystem ──────────────────────────────────────────────────────────────
+
+          # Both register into the host `tools` registry and provide nothing, so
+          # they need no realm. The `fs` service and its policy stay in the host.
+          - id: tool-fs
+            name: '@deepseek-ai/dsh-tool-fs'
+
+          - id: tool-fs-search
+            name: '@deepseek-ai/dsh-tool-fs-search'
+            config:
+              sampleOverCapGlobResults: false
+
+          # ── background jobs ────────────────────────────────────────────────────────
+
+          # Only the model-facing controls. The task REGISTRY stays on the host plane:
+          # its producers sit outside any realm this file could put it in — `tool-bash`
+          # above resolves it with `ctx.get`, and an entry-local realm here is invisible
+          # to every sibling row, so `run_in_background` would answer "background jobs
+          # unavailable" while these controls sat in the catalog. The registry is keyed by
+          # owning agent anyway, so one host instance serves every session. What a preset
+          # chooses is whether its agent can collect and stop background work at all.
+          - id: tool-jobs
+            name: '@deepseek-ai/dsh-tool-jobs'
+
+          # ── skills ──────────────────────────────────────────────────────────────────
+
+          # The skill REGISTRY lives in the host composition and is layered per scope:
+          # these rows register into THIS preset's layer of it, so they need no realm.
+          # `skill-filesystem` contributes local-root discovery for agents on this preset, and
+          # `tool-skill` gives them the catalog and loader; the merged catalog also
+          # carries whatever the deployment registered globally (repository plugins).
+          - id: skill-filesystem
+            name: '@deepseek-ai/dsh-skill-filesystem'
+            config:
+              customSkillDirs:
+                - !!js "process.getBuiltinModule('node:path').join(process.getBuiltinModule('node:path').dirname(process.getBuiltinModule('node:module').createRequire(baseUrl).resolve('@dsh-cove/dsh-web-all/package.json')), 'presets/code-vibe/skills')"
+
+          - id: tool-skill
+            name: '@deepseek-ai/dsh-tool-skill'
+            config:
+              catalogDescriptionMaxLength: 300
+
+          # ── goals ───────────────────────────────────────────────────────────────────
+
+          # The goal registry stays on the host plane; this preset contributes the
+          # human command and model-facing tool for agents that choose this mode.
+          - id: command-goal
+            name: '@deepseek-ai/dsh-command-goal'
+
+          - id: tool-goal
+            name: '@deepseek-ai/dsh-tool-goal'
+
+          # ── plan mode ───────────────────────────────────────────────────────────────
+
+          # Plan state is per-agent by nature, so an entry-local realm is not a
+          # workaround here — it is the correct lifetime.
+          - id: planning
+            name: cordis:group
+            group: true
+            isolate:
+              planMode: true
+            config:
+              - id: plan-mode
+                name: '@deepseek-ai/dsh-plan-mode'
+                config:
+                  section: |
+                        You are in plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement — including an answer confirming something you asked — approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
+
+                        Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
+
+                        The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
+
+                        Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
+
+                        Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
+
+                        When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
+
+          # ── compaction ──────────────────────────────────────────────────────────────
+
+          # `compaction-basic` reads `toolResultPrune` through `ctx.get`, so the pruner must
+          # share this realm rather than sit outside it.
+          #
+          # `tokenMeter` is deliberately NOT in this realm: the meter stays on the HOST
+          # plane, and the rows here resolve that one instance. It takes no configuration,
+          # keys every fold by Session, and owns the context-meter projection units the
+          # browser reads for every session — behind a realm those units would come and go
+          # with whichever presets happen to be mounted. What a preset chooses is whether
+          # its agent compacts at all, which is `compaction-basic` below.
+          - id: compaction
+            name: cordis:group
+            group: true
+            isolate:
+              compaction: true
+              toolResultPruner: true
+            config:
+              - id: compaction-basic
+                name: '@deepseek-ai/dsh-compaction-basic'
+
+              - id: command-compact
+                name: '@deepseek-ai/dsh-command-compact'
+
+              - id: tool-result-pruner
+                name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
+                config:
+                  thresholdChars: 8192
+                  headChars: 4096
+                  tailChars: 1024
+
+          # ── delegation and workflows ────────────────────────────────────────────────
+
+          # The `subagents` registry and its spawn/fork backends live in the HOST
+          # composition: the registry is a process singleton whose cross-session queries
+          # the api-proxy serves to the browser, and a provider name may only be
+          # registered once. This preset contributes the delegation TOOLS, which resolve
+          # that host registry.
+          #
+          # `workflows` is different — nothing outside an agent reads it — so every row
+          # that reaches it shares one entry-local realm here, and a consumer left
+          # outside would resolve a host registry this preset does not populate.
+          - id: delegation
+            name: cordis:group
+            group: true
+            isolate:
+              workflowEngine: true
+            config:
+              - id: tool-subagent-control
+                name: '@deepseek-ai/dsh-tool-subagent-control'
+
+              - id: tool-subagent-list-agents
+                name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
+
+              - id: tool-subagent
+                name: '@deepseek-ai/dsh-tool-subagent'
+                config:
+                  provider: spawn
+                  toolName: subagent
+                  backgroundMode: continuable
+
+              # Fork MUST stay one-shot (aligned with the base bundle and the
+              # `fork-children-stay-one-shot` decision): fork's only payoff over spawn is
+              # request-prefix reuse of the seeded parent history. A continuable fork
+              # installs the child-scoped `report` tool + `tool:report` section in the
+              # request head, ahead of the inherited history, so reuse breaks before the
+              # first inherited turn and the child pays the duplication for nothing.
+              # Long-lived children that need no inherited context use `subagent` (spawn)
+              # above, which is continuable.
+              - id: tool-subagent-fork
+                name: '@deepseek-ai/dsh-tool-subagent'
+                config:
+                  provider: fork
+                  toolName: subagent_fork
+                  backgroundMode: one-shot
+
+              # Product providers are host-plane singletons. Copy this preset, then
+              # remove `disabled` from either ordinary tool row to expose that product
+              # only to agents composed from the copy.
+              - id: tool-subagent-codex
+                name: '@deepseek-ai/dsh-tool-subagent'
+                disabled: true
+                config:
+                  provider: codex
+                  toolName: subagent_codex
+                  backgroundMode: one-shot
+                  maxDepth: provider-managed
+
+              - id: tool-subagent-claude-code
+                name: '@deepseek-ai/dsh-tool-subagent'
+                disabled: true
+                config:
+                  provider: claude-code
+                  toolName: subagent_claude_code
+                  backgroundMode: one-shot
+                  maxDepth: provider-managed
+
+              # 0.1.6-alpha.1 dropped @deepseek-ai/dsh-workflow-worker-thread from the
+              # shipped CLI tree (last published was 0.1.5-rc.2). Stock presets now use
+              # workflow-ptc; keep provider: spawn aligned with standard/agent.cordis.yml.
+              - id: workflow-ptc
+                name: '@deepseek-ai/dsh-workflow-ptc'
+                config:
+                  provider: spawn
+
+              - id: tool-workflow
+                name: '@deepseek-ai/dsh-tool-workflow'
+
+              - id: tool-ralph
+                name: '@deepseek-ai/dsh-tool-ralph'
+                config:
+                  subagentProvider: spawn
+                  maxRounds: 64
+
+          # ── remaining model-facing rows ─────────────────────────────────────────────
+
+          - id: tool-ask-user
+            name: '@deepseek-ai/dsh-tool-ask-user'
+
+          - id: tool-todo
+            name: '@deepseek-ai/dsh-tool-todo'
+            config:
+              allowParallelInProgress: true
+
+          # The `web` service and its search provider stay in the host composition; only
+          # the model-facing tool is per-session.
+          - id: tool-web
+            name: '@deepseek-ai/dsh-tool-web'
+            config:
+              fetch: true
+              searchTimeoutMs: 60000
+
+          - id: present
+            name: '@deepseek-ai/dsh-tool-present'
+
+          # ── presentation ────────────────────────────────────────────────────────────
+
+          # Native presentation for this agent alone: the model sees every tool schema
+          # and calls tools directly, one per action (no `run_code` program transport).
+          # Pinned explicitly so a deployment-wide `code`/`both` default never leaks into
+          # this agent. Switch this to `code` or `both` to opt back into Code Mode (which
+          # then requires the host's `codeRuntime`).
+          - id: tool-presentation
+            name: '@deepseek-ai/dsh-agent-tool-presentation'
+            config:
+              mode: native

package/presets/hiopen.patch.yml

@@ -0,0 +1,109 @@
+# HiOpen provider preset for DSH. Credentials stay in
+# $DSH_HOME/.credentials.yaml as refs.HIOPEN_API_KEY.
+#
+# The public /v1/models endpoint advertises many routes, including embeddings,
+# detectors, guard models, and currently unavailable NVIDIA NIM functions. This
+# curated list contains chat models that are useful to a tool-using DSH agent.
+# Model ids are copied exactly from the endpoint. Capacity and modality facts use
+# vendor metadata and live endpoint probes; conservative declarations fail early
+# instead of stranding a durable conversation on an unsupported image request.
+- id: llm-deepseek
+  name: "@deepseek-ai/dsh-llm-deepseek-api-key"
+  config:
+    baseURL: https://datasage.flow.chat/hiopen/v1
+
+- id: llm-pi-ai
+  name: "@deepseek-ai/dsh-llm-pi-ai"
+  config:
+    providers:
+      hiopen:
+        displayName: HiOpen
+        apiKeyEnv: HIOPEN_API_KEY
+        api: openai-completions
+        baseURL: https://datasage.flow.chat/hiopen/v1
+        streamIdleTimeoutMs: 1800000
+        reasoning: high
+        defaultContextWindow: 262144
+        defaultMaxTokens: 32768
+        defaultInput:
+          - text
+        compat:
+          supportsDeveloperRole: false
+          supportsReasoningEffort: true
+          supportsUsageInStreaming: true
+          maxTokensField: max_tokens
+        models:
+          - id: deepseek-ai/deepseek-v4.1-flash
+            name: DeepSeek V4.1 Flash
+            contextWindow: 1048576
+            maxTokens: 262144
+            input:
+              - text
+              - image
+            reasoningEfforts:
+              low: "low"
+              medium: "medium"
+              high: "high"
+              max: "max"
+            compat:
+              thinkingFormat: deepseek
+              requiresReasoningContentOnAssistantMessages: true
+          - id: deepseek-v4-flash-0731
+            name: DeepSeek V4 Flash 0731
+            contextWindow: 1000000
+            maxTokens: 128000
+            input:
+              - text
+            reasoningEfforts:
+              low: "low"
+              medium: "medium"
+              high: "high"
+              max: "max"
+            compat:
+              thinkingFormat: deepseek
+              requiresReasoningContentOnAssistantMessages: true
+          - id: z-ai/glm-5.3
+            name: GLM 5.3
+            contextWindow: 1048576
+            maxTokens: 131072
+            input:
+              - text
+            reasoningEfforts:
+              low: "low"
+              high: "high"
+              max: "max"
+            compat:
+              thinkingFormat: zai
+              requiresReasoningContentOnAssistantMessages: true
+          - id: z-ai/glm-5.3-flash
+            name: GLM 5.3 Flash
+            contextWindow: 1048576
+            maxTokens: 131072
+            input:
+              - text
+              - image
+            reasoningEfforts:
+              low: "low"
+              high: "high"
+              max: "max"
+            compat:
+              thinkingFormat: zai
+              requiresReasoningContentOnAssistantMessages: true
+          - id: openai/gpt-oss-20b
+            name: GPT OSS 20B
+            contextWindow: 131072
+            maxTokens: 32768
+            input:
+              - text
+            reasoningEfforts:
+              low: "low"
+              medium: "medium"
+              high: "high"
+          - id: meta/llama-3.2-90b-vision-instruct
+            name: Llama 3.2 90B Vision Instruct
+            contextWindow: 131072
+            maxTokens: 8192
+            input:
+              - text
+              - image
+            reasoningEfforts: false

package/src/client/compat.ts

@@ -0,0 +1,86 @@
+/**
+ * compat shim — data-pane / data-dsh-frame 补标。
+ *
+ * 官方 shell 的三列容器只带 css-module 哈希类（*_sidebarCol / *_centerCol /
+ * *_detailsCol），不带稳定的 data-pane / data-dsh-frame 属性。全家桶各位置
+ * 模块与皮肤按这些属性锚定 DOM，因此本 shim 把列容器标记出来，并在 React
+ * 重建列结构时自动重打。
+ *
+ * 行为契约（保持稳定，勿改）：
+ *  - 侧栏列 → data-pane="sidebar"；中栏列 → data-pane="conversation"；
+ *    右栏列 → data-pane="details"；列容器父级 → data-dsh-frame=""
+ *  - 只写属性，不删节点、不扰动 React 协调；幂等。
+ */
+export interface CompatStamp {
+  /** 列选择器 → 要打的属性。 */
+  columns: ReadonlyArray<readonly [selector: string, attribute: string]>
+  /** 列集合之上再补标的 frame 属性名。 */
+  frameAttribute: 'data-dsh-frame'
+}
+
+export const DEFAULT_STAMPS: CompatStamp = {
+  columns: [
+    ['[class*="sidebarCol"]', 'data-pane="sidebar"'],
+    ['[class*="centerCol"]', 'data-pane="conversation"'],
+    ['[class*="detailsCol"], [class*="rightbarCol"]', 'data-pane="details"'],
+  ],
+  frameAttribute: 'data-dsh-frame',
+}
+
+const COLUMN_OR = '[class*="sidebarCol"], [class*="centerCol"], [class*="detailsCol"], [class*="rightbarCol"]'
+
+/** 单次扫描：给列与 frame 打标。返回 true 表示发生过变化。 */
+export function applyCompat(stamps: CompatStamp = DEFAULT_STAMPS): boolean {
+  // 裸 host / 测试环境没有 document：直接返回（无副作用）。
+  if (typeof document === 'undefined') return false
+  let changed = false
+  for (const [selector, attribute] of stamps.columns) {
+    const el = document.querySelector(selector)
+    if (el === null) continue
+    const eq = attribute.indexOf('=')
+    const name = attribute.slice(0, eq)
+    const value = attribute.slice(eq + 1).replace(/^"|"$/g, '')
+    if (el.getAttribute(name) !== value) {
+      el.setAttribute(name, value)
+      changed = true
+    }
+  }
+  // frame：列集合共同的父级网格项。
+  const column = document.querySelector(COLUMN_OR)
+  const frame = column?.parentElement ?? null
+  if (frame !== null && frame.getAttribute(stamps.frameAttribute) !== '') {
+    frame.setAttribute(stamps.frameAttribute, '')
+    changed = true
+  }
+  return changed
+}
+
+/**
+ * 挂载 compat 补标：首次立即应用，之后用 rAF 合并 MutationObserver 突发并
+ * 在每帧重打一次，直到全部打标到位。
+ * @returns disposer。
+ */
+export function mountCompat(stamps: CompatStamp = DEFAULT_STAMPS): () => void {
+  let scheduled = false
+  let done = false
+  const pass = (): void => {
+    scheduled = false
+    if (applyCompat(stamps)) done = false
+    else done = true
+  }
+  const schedule = (): void => {
+    if (scheduled) return
+    scheduled = true
+    requestAnimationFrame(() => {
+      pass()
+      if (!done) schedule()
+    })
+  }
+  schedule()
+  const observer = new MutationObserver(() => schedule())
+  observer.observe(document.body, { childList: true, subtree: true })
+  return () => {
+    observer.disconnect()
+    scheduled = false
+  }
+}