super-dsh 0.3.0-c → 0.3.0-e

package/node_modules/better-dsh/dsh-docs/user/guide/python-sdk.md

@@ -1,150 +0,0 @@
-# Get started with the Python SDK
-
-English | [中文](python-sdk.zh.md)
-
-This tutorial installs the published Python SDK, runs the shipped standalone minimal profile, and shows how to customize the same `dsh` profile from your own program.
-
-## Prerequisites
-
-- Python 3.10 or newer
-- Git
-- Linux x64, Linux arm64, macOS 14 or newer on arm64, or Windows x64
-- A DeepSeek-compatible API endpoint and credential
-- An isolated workspace and an isolated Harness home
-
-## Install the SDK
-
-### Linux and macOS
-
-```sh
-git clone https://github.com/deepseek-ai/deepseek-harness.git
-cd deepseek-harness
-python -m venv .venv
-. .venv/bin/activate
-python -m pip install deepseek-harness-sdk
-```
-
-### Windows PowerShell
-
-```powershell
-git clone https://github.com/deepseek-ai/deepseek-harness.git
-Set-Location deepseek-harness
-py -3.10 -m venv .venv
-.venv\Scripts\Activate.ps1
-python -m pip install deepseek-harness-sdk
-```
-
-The installation includes a matching native runtime wheel and the `dsh` command. Normal SDK execution needs no system Node.js. Repository contributors who build the artifacts should use the [Python contributor workflow](../../../python/development.md).
-
-## Run the checked-in example
-
-Export the credential and, when needed, a compatible proxy endpoint:
-
-### Linux and macOS
-
-```sh
-export DEEPSEEK_API_KEY=sk-your-key-here
-# export DEEPSEEK_BASE_URL=http://127.0.0.1:8000/v1
-```
-
-### Windows PowerShell
-
-```powershell
-$env:DEEPSEEK_API_KEY = "sk-your-key-here"
-# $env:DEEPSEEK_BASE_URL = "http://127.0.0.1:8000/v1"
-```
-
-Run one task with explicit workspace and home paths:
-
-### Linux and macOS
-
-```sh
-python python/sdk/examples/minimal.py \
-  --workspace /absolute/path/to/disposable-workspace \
-  --dsh-home /absolute/path/to/example-dsh-home \
-  --session-id example-001 \
-  "Inspect the repository and fix the failing tests."
-```
-
-### Windows PowerShell
-
-```powershell
-python python/sdk/examples/minimal.py `
-  --workspace C:\work\disposable-workspace `
-  --dsh-home C:\work\example-dsh-home `
-  --session-id example-001 `
-  "Inspect the repository and fix the failing tests."
-```
-
-The script prints the final assistant response. The selected home receives the generated `sdk-minimal` profile, installed plugins, and uncompressed JSONL session logs under `sessions/`. The example and SDK never silently read `~/.dsh`.
-
-## Use the SDK in your program
-
-```python
-from pathlib import Path
-
-from deepseek_harness import DeepSeekHarness
-
-workspace = Path("/absolute/path/to/disposable-workspace").resolve()
-dsh_home = Path("/absolute/path/to/example-dsh-home").resolve()
-with DeepSeekHarness(
-    provider="deepseek-official",
-    model="deepseek-v4-flash",
-    max_tokens=49_152,
-    cwd=str(workspace),
-    dsh_home=str(dsh_home),
-    profile="sdk-minimal",
-) as harness:
-    result = harness.run(
-        "Inspect the repository and fix the failing tests.",
-        session_id="example-001",
-    )
-
-print(result.final_response)
-```
-
-The SDK starts the bundled `dsh --profile sdk-minimal` process lazily and reuses it until context-manager exit. The profile, its persistent patch, the home patch, and any ordered `patches` tuple form the application configuration. There is no separate Python runtime bin or complete-config option.
-
-## Install or define plugins
-
-Use `dsh plugin` for dependencies and bundle layers that should persist in this home:
-
-### Linux and macOS
-
-```sh
-export DSH_HOME=/absolute/path/to/example-dsh-home
-dsh --profile sdk-minimal --dump-default-config >/dev/null
-dsh plugin --profile sdk-minimal add file:/absolute/path/to/my-plugin-bundle
-```
-
-### Windows PowerShell
-
-```powershell
-$env:DSH_HOME = "C:\work\example-dsh-home"
-dsh --profile sdk-minimal --dump-default-config | Out-Null
-dsh plugin --profile sdk-minimal add file:C:/work/my-plugin-bundle
-```
-
-The first command initializes the shipped standalone profile. The second forwards package management to `pnpm`, then records any installed package that exports a `dsh.bundle` layer. Install `pnpm` only for this management command; launching the installed SDK does not need it. Edit `$DSH_HOME/profiles/sdk-minimal/cordis.patch.yml` for persistent row changes, or pass patch files from Python for per-launch changes.
-
-Another `profile` is valid when it includes `@deepseek-ai/dsh-sdk-app` or another JSON-RPC server row. Missing server rows, unresolved plugins, and invalid patches fail during startup instead of falling back to another composition.
-
-## Understand the minimal profile
-
-| Property | Value |
-|---|---|
-| System prompt | `DSH_SYSTEM_PROMPT`, falling back to `You are a helpful software engineer assistant.` |
-| Model in `minimal.py` | `--model`, then `DSH_MODEL`, then `deepseek-v4-flash` |
-| Model-facing tools | Persistent `bash` on Linux/macOS or `pwsh` on Windows, plus `str_replace_editor` |
-| Shell timeout | 300 seconds |
-| Editor output limit | 16,000 characters |
-| Runtime context and compaction | Absent |
-| Session persistence | Uncompressed JSONL under `<dsh_home>/sessions` |
-
-The profile's sole bundle inserts the complete tree over an empty root and does not include `dsh-base`; later base-profile tools therefore cannot appear implicitly. It contains the SDK protocol, one environment-configured DeepSeek adapter, local execution, and persistence, while settings, managed credentials, telemetry, Web tools, subagents, local instruction discovery, and compaction are absent. It pins `danger-full-access`, so the platform-selected persistent shell and editor can modify any path visible to the runtime; use a disposable checkout or container.
-
-The installed wheel still packages the full `web` profile and frontend assets. Run `dsh web` against an explicit `DSH_HOME` when a Python SDK deployment also needs the browser application; `web` is a separate CLI application and cannot serve a Python SDK client.
-
-Use a fresh home when profiles, plugins, credentials, settings, and sessions must be isolated. Use a fresh session id for independent work; reuse a harness, home, and id only to continue the same durable conversation and session-owned resources.
-
-The [bundle reference](../../../packages/bundle/sdk-minimal/README.md) owns the exact tree, and the [example reference](../../../python/sdk/examples/README.md) owns the runnable program. The [Python SDK reference](../../../python/sdk/README.md) covers lifecycle, results, notifications, and low-level behavior; the [dsh CLI reference](../../../apps/cli/reference/README.md) covers profile layering.

package/node_modules/better-dsh/dsh-docs/user/guide/python-sdk.zh.md

@@ -1,150 +0,0 @@
-# Python SDK 入门
-
-[English](python-sdk.md) | 中文
-
-本教程安装已发布的 Python SDK，运行随附的独立极简 profile，并说明如何从自己的程序自定义同一个 `dsh` profile。
-
-## 前置条件
-
-- Python 3.10 或更高版本
-- Git
-- Linux x64、Linux arm64、arm64 上的 macOS 14 或更高版本，或 Windows x64
-- DeepSeek 兼容的 API endpoint 与凭据
-- 隔离的 workspace 与隔离的 Harness home
-
-## 安装 SDK
-
-### Linux 与 macOS
-
-```sh
-git clone https://github.com/deepseek-ai/deepseek-harness.git
-cd deepseek-harness
-python -m venv .venv
-. .venv/bin/activate
-python -m pip install deepseek-harness-sdk
-```
-
-### Windows PowerShell
-
-```powershell
-git clone https://github.com/deepseek-ai/deepseek-harness.git
-Set-Location deepseek-harness
-py -3.10 -m venv .venv
-.venv\Scripts\Activate.ps1
-python -m pip install deepseek-harness-sdk
-```
-
-安装内容包含匹配的原生运行时 wheel 与 `dsh` 命令。普通 SDK 运行不需要系统 Node.js。需要构建产物的仓库贡献者应使用 [Python 贡献者工作流](../../../python/development.zh.md)。
-
-## 运行检入示例
-
-导出凭据；使用兼容代理时再设置 endpoint：
-
-### Linux 与 macOS
-
-```sh
-export DEEPSEEK_API_KEY=sk-your-key-here
-# export DEEPSEEK_BASE_URL=http://127.0.0.1:8000/v1
-```
-
-### Windows PowerShell
-
-```powershell
-$env:DEEPSEEK_API_KEY = "sk-your-key-here"
-# $env:DEEPSEEK_BASE_URL = "http://127.0.0.1:8000/v1"
-```
-
-使用显式 workspace 与 home 路径运行一个任务：
-
-### Linux 与 macOS
-
-```sh
-python python/sdk/examples/minimal.py \
-  --workspace /absolute/path/to/disposable-workspace \
-  --dsh-home /absolute/path/to/example-dsh-home \
-  --session-id example-001 \
-  "Inspect the repository and fix the failing tests."
-```
-
-### Windows PowerShell
-
-```powershell
-python python/sdk/examples/minimal.py `
-  --workspace C:\work\disposable-workspace `
-  --dsh-home C:\work\example-dsh-home `
-  --session-id example-001 `
-  "Inspect the repository and fix the failing tests."
-```
-
-脚本会打印最终 assistant 响应。所选 home 会保存生成的 `sdk-minimal` profile、已安装插件，以及 `sessions/` 下的未压缩 JSONL 会话日志。示例与 SDK 绝不会静默读取 `~/.dsh`。
-
-## 在程序中使用 SDK
-
-```python
-from pathlib import Path
-
-from deepseek_harness import DeepSeekHarness
-
-workspace = Path("/absolute/path/to/disposable-workspace").resolve()
-dsh_home = Path("/absolute/path/to/example-dsh-home").resolve()
-with DeepSeekHarness(
-    provider="deepseek-official",
-    model="deepseek-v4-flash",
-    max_tokens=49_152,
-    cwd=str(workspace),
-    dsh_home=str(dsh_home),
-    profile="sdk-minimal",
-) as harness:
-    result = harness.run(
-        "Inspect the repository and fix the failing tests.",
-        session_id="example-001",
-    )
-
-print(result.final_response)
-```
-
-SDK 会延迟启动内置的 `dsh --profile sdk-minimal` 进程，并复用到上下文管理器退出。Profile、其持久 patch、home patch 与任何有序 `patches` tuple 共同组成应用配置。不存在独立 Python 运行时 bin 或完整配置选项。
-
-## 安装或定义插件
-
-需要在该 home 中持久保存依赖与 bundle 层时，使用 `dsh plugin`：
-
-### Linux 与 macOS
-
-```sh
-export DSH_HOME=/absolute/path/to/example-dsh-home
-dsh --profile sdk-minimal --dump-default-config >/dev/null
-dsh plugin --profile sdk-minimal add file:/absolute/path/to/my-plugin-bundle
-```
-
-### Windows PowerShell
-
-```powershell
-$env:DSH_HOME = "C:\work\example-dsh-home"
-dsh --profile sdk-minimal --dump-default-config | Out-Null
-dsh plugin --profile sdk-minimal add file:C:/work/my-plugin-bundle
-```
-
-第一个命令初始化随附的独立 profile。第二个命令把包管理转发给 `pnpm`，然后记录所有导出 `dsh.bundle` 层的已安装包。只有执行此管理命令时才需要安装 `pnpm`；启动已安装 SDK 不需要它。持久配置项变更应编辑 `$DSH_HOME/profiles/sdk-minimal/cordis.patch.yml`；单次启动变更则从 Python 传入 patch 文件。
-
-另一个 `profile` 只有包含 `@deepseek-ai/dsh-sdk-app` 或另一个 JSON-RPC server 配置项时才有效。缺失 server 配置项、无法解析的插件和非法 patch 会在启动时失败，不会回退到其他组合。
-
-## 理解极简 profile
-
-| 属性 | 值 |
-|---|---|
-| 系统提示词 | `DSH_SYSTEM_PROMPT`，未设置时为 `You are a helpful software engineer assistant.` |
-| `minimal.py` 的模型 | `--model`，然后是 `DSH_MODEL`，最后是 `deepseek-v4-flash` |
-| 面向模型的工具 | Linux／macOS 上的持久 `bash` 或 Windows 上的 `pwsh`，以及 `str_replace_editor` |
-| Shell 超时 | 300 秒 |
-| Editor 输出上限 | 16,000 字符 |
-| 运行时上下文与 compaction | 不存在 |
-| 会话持久化 | `<dsh_home>/sessions` 下的未压缩 JSONL |
-
-该 profile 的唯一组合包会在空根之上插入完整配置树，且不包含 `dsh-base`，因此基础 profile 以后新增的工具不会隐式出现。它包含 SDK 协议、一个由环境配置的 DeepSeek 适配器、本地执行与持久化；settings、托管凭据、遥测、Web 工具、subagent、本地指令发现和 compaction 均不存在。它固定使用 `danger-full-access`，因此按平台选择的持久 shell 与 editor 可以修改运行时可见的任何路径；应使用一次性 checkout 或容器。
-
-已安装 wheel 仍会打包完整 `web` profile 与前端产物。如果 Python SDK 部署还需要浏览器应用，请针对显式 `DSH_HOME` 运行 `dsh web`；`web` 是独立 CLI 应用，不能为 Python SDK client 提供服务。
-
-需要隔离 profile、插件、凭据、设置与会话时，应使用新的 home。独立工作应使用新的 session id；只有继续同一段持久对话和会话资源时，才同时复用 harness、home 与 id。
-
-[组合包参考](../../../packages/bundle/sdk-minimal/README.zh.md)定义确切配置树，[示例参考](../../../python/sdk/examples/README.zh.md)定义可运行程序。[Python SDK 参考](../../../python/sdk/README.zh.md)介绍生命周期、结果、通知与底层行为；[dsh CLI 参考](../../../apps/cli/reference/README.zh.md)介绍 profile 分层。

package/node_modules/better-dsh/dsh-docs/user/guide/schedule.md

@@ -1,21 +0,0 @@
-# Schedule session-local reminders
-
-English | [中文](schedule.zh.md)
-
-This overlay opts one `dsh web` process into Schedule reminders without changing the shipped default Web composition:
-
-```sh
-dsh web --patch apps/cli/config/examples/schedule/cordis.yml
-```
-
-The current overlay supports reminders created with a positive whole-number `after_seconds`, an absolute `at` target, or a fixed-rate `every_seconds` interval of at least 300 seconds. The model manages them through `schedule_create`, `schedule_list`, and `schedule_delete`; every result identifies delivery as `session-local`.
-
-With this overlay enabled, a successfully opened Session with active reminders shows a read-only catalog in the conversation header. It lists the complete prompt, scheduled or overdue status, one-time or exact repeating cadence, browser-local target time, and relative time. The sidebar also places a non-interactive alarm after the title of grouped, flat, and search rows when their currently available projection value is non-empty. These surfaces never create, edit, delete, or acknowledge reminders, and a cold Session's cached alarm can be briefly missing or stale.
-
-The browser attaches its IANA zone to each prompt. Time-context tells the model to interpret otherwise-unqualified dates and times in that request's browser zone. This assumption belongs to natural-language interpretation only: `schedule_create.at` must be either a strict RFC 3339 date-time with `Z` or a numeric offset, or `{ date, time, time_zone }` with an explicit `UTC` or IANA Area/Location zone. Schedule does not retain or infer a Session default zone. Daylight-saving gaps are rejected, overlaps choose the first instant, and successful records keep only the resulting UTC target.
-
-The original Session log owns each reminder. A live root Agent waits until it is fully idle, then queues a normal follow-up turn in that conversation. It never steers current work and adds no separate receipt or reminder card. Closing the process or leaving the Session cold stops its in-memory timer without deleting the record; reopening that same Session restores the wait and delivers an overdue reminder. Reading cold history never activates it, and a fork does not inherit its parent's reminders.
-
-Every reminders stay aligned to their creation time. If one is overdue, only its latest due occurrence is presented and the next target remains on the original fixed-rate sequence. All distinct Every records overdue at the same idle decision are combined into one follow-up with one occurrence each; missed intervals do not create a backlog. Due one-shots run before that batch. Calendar and Cron expressions are not supported.
-
-Create and actual delete operations acknowledge success only after Session persistence confirms their event prefix. Schedule does not provide browser, operating-system, email, SMS, or other external notification. A durable dispatch records that the follow-up was queued; it does not acknowledge model success or user receipt.

package/node_modules/better-dsh/dsh-docs/user/guide/schedule.zh.md

@@ -1,21 +0,0 @@
-# 安排会话内提醒
-
-[English](schedule.md) | 中文
-
-此 overlay 让一个 `dsh web` 进程显式启用 Schedule 提醒，同时不改变交付的默认 Web 组合：
-
-```sh
-dsh web --patch apps/cli/config/examples/schedule/cordis.yml
-```
-
-当前 overlay 支持使用正整数 `after_seconds`、绝对时间 `at` 目标，或至少 300 秒的固定速率 `every_seconds` 间隔创建提醒。模型通过 `schedule_create`、`schedule_list` 和 `schedule_delete` 管理它们；每个结果都会把交付标为 `session-local`。
-
-启用此 overlay 后，成功打开且存在活动提醒的 Session 会在对话 header 中显示只读目录。目录列出完整 prompt、等待中或已逾期状态、单次或精确重复周期、浏览器本地目标时间与相对时间。侧边栏还会在 grouped、flat 与 search 行当前可用的 projection 值非空时，于标题后显示不可交互的闹钟。这些界面不会创建、编辑、删除或确认提醒；cold Session 的缓存闹钟允许短暂漏显或残留。
-
-浏览器会为每条提示词附加其 IANA 时区。Time-context 会告诉模型，把未明确限定时区的日期和时间解释为该请求的浏览器时区。此假设仅用于自然语言解释：`schedule_create.at` 必须是带 `Z` 或数值偏移量且严格符合 RFC 3339 的日期时间，或是带显式 `UTC` 或 IANA Area/Location 时区的 `{ date, time, time_zone }`。Schedule 不保留或推断 Session 默认时区。夏令时缺口会被拒绝，重叠时段选择第一个时刻；成功创建的记录只保留所得的 UTC 目标。
-
-每条提醒由原 Session 日志拥有。live 根 Agent 会等待到完全 idle，再在该对话中排入一个普通 follow-up 轮次。它绝不会中途引导当前工作，也不会添加独立回执或提醒卡片。关闭进程或让 Session 保持 cold 会停止内存 timer，但不会删除记录；重新打开同一个 Session 会恢复等待并交付逾期提醒。查看 cold 历史不会激活提醒，fork 也不会继承父 Session 的提醒。
-
-Every 提醒始终与其创建时刻对齐。如果提醒逾期，只会呈现最新一个到期发生时点，下一个目标仍保留在原固定速率序列上。同一次 idle 决策中逾期的所有不同 Every 记录会合并为一个 follow-up，每条记录各有一个发生时点；错过的间隔不会形成积压。已到期的一次性提醒会在该批次之前运行。不支持日历表达式和 Cron 表达式。
-
-创建和实际删除操作只有在 Session persistence 确认对应事件前缀后才会确认成功。Schedule 不提供浏览器、操作系统、邮件、短信或其他外部通知。持久 dispatch 会记录 follow-up 已经入队；它不确认模型成功或用户已收到提醒。

package/node_modules/better-dsh/dsh-docs/user/index.md

@@ -1,11 +0,0 @@
----
-layout: false
-head:
-  - - meta
-    - http-equiv: refresh
-      content: 0; url=./guide/quickstart
----
-
-# DeepSeek Harness
-
-English | [中文](index.zh.md)

package/node_modules/better-dsh/dsh-docs/user/index.zh.md

@@ -1,11 +0,0 @@
----
-layout: false
-head:
-  - - meta
-    - http-equiv: refresh
-      content: 0; url=./guide/quickstart
----
-
-# DeepSeek Harness
-
-[English](index.md) | 中文

package/node_modules/better-dsh/dsh-docs/web-styling.md

@@ -1,29 +0,0 @@
-# Web UI style reference
-
-English | [中文](web-styling.zh.md)
-
-This reference defines styling ownership and component rules for browser client packages. The current token values live in [`packages/client/ui-theme/src/styles/`](../packages/client/ui-theme/src/styles/); this document does not duplicate that generated-by-source inventory.
-
-## Ownership
-
-[`ui-theme`](../packages/client/ui-theme/README.md) owns the `--dsw-*` static scale, semantic aliases, typography, motion, gradients, shadows, scrollbar styles, and light/dark preference. [`ui-layout`](../packages/client/ui-layout/README.md) applies the resolved theme snapshot to the document. Feature packages consume semantic aliases and do not define another global theme.
-
-Global style sheets belong in `ui-theme/src/styles/`. Component styles live beside their component as CSS Modules. A component may define a local custom property when its value is part of that component's layout or presentation contract; shared colors, typography, elevation, and motion belong to the theme package.
-
-## Component rules
-
-- Use CSS Modules and `clsx`; do not add a component library or Tailwind.
-- Use `--dsw-alias-*` semantic tokens in feature components. Do not copy static palette values or write literal colors there.
-- Keep theme selectors out of feature component CSS. Light/dark overrides belong to the theme owner.
-- Pair font sizes with line heights and use the theme typography variables when an existing role matches.
-- Keep source text, terminal output, and diff lines unwrapped when their component contract requires column preservation; use the shared scrollbar styles rather than component-specific scrollbar selectors.
-- Put presentation in CSS. Inline React styles may pass component-local custom-property values but must not encode theme branches.
-- Preserve keyboard focus visibility and reduced-motion behavior when adding transitions or hover-only controls.
-- Rounded corners inherit the global superellipse smoothing from ui-theme's `corner-shape.css` on supporting engines. Pair `corner-shape: round` with every full-round `border-radius` (`50%`, `100%`, or a pill radius) so circles and capsules keep circular arcs; the ui-theme corner-shape spec enforces the pairing.
-- Elevated surfaces (menus, popovers, modals, panels, floating buttons, the composer) set `border: 0` and take `box-shadow: var(--dsw-elevation-panel)`, `var(--dsw-elevation-prominent)`, or the composer's `var(--dsw-elevation-soft)` (larger blur at lower alpha): the 0.5px hairline stroke is the first shadow layer, and `--dsw-elevation-stroke-color` rebinds or suppresses it per surface or state. Never pair a `--dsw-alias-border-*` border with an lv/elevation shadow — the ui-theme elevation spec rejects the pairing; state-colored borders (warn panels) stay real borders.
-- Flat borders and separators that use a neutral `--dsw-alias-border-*` token draw at `0.5px` — buttons, inputs, cards, row dividers, and separators drawn as filled boxes (menu separators, the conversation header seam, markdown `hr`, vertical rails) share the hairline weight, which Chromium paints as one device pixel. Dashed affordances and state-colored borders keep 1px; spinner ring tracks keep their width through the spec's explicit allowlist. The ui-theme elevation spec rejects wider neutral solid borders.
-- Clickable artifact links (markdown anchors, prose file mentions, web source and fetch links, produced-file chips, workflow member links) color through `--dsw-alias-link` at `font-weight: 500`, with no underline at rest and a dotted 3px-offset underline on hover/focus. Text-leading anchors also lead with the ui-primitives `LinkIcon` category glyph riding `currentColor`; workflow member links and image-only anchors carry no glyph, and tool-row file links keep their grey dotted affordance ([clickable-link Agent Note](../.agents/notes/implemented/feature/2026-09-04-web-clickable-link-styles.md)).
-
-## Changing the system
-
-Add or change a shared token in the owning `ui-theme` sheet, then consume its semantic alias from feature packages. Update the owning package reference when a public styling contract changes. Visual behavior follows the [testing policy](testing.md); the [styling-system Agent Note](../.agents/notes/implemented/process/2026-07-19-web-styling-system.md) records framework rationale.

package/node_modules/better-dsh/dsh-docs/web-styling.zh.md

@@ -1,29 +0,0 @@
-# Web UI 样式参考
-
-[English](web-styling.md) | 中文
-
-本文规定浏览器客户端包的样式职责归属与组件规则。当前 token 值位于 [`packages/client/ui-theme/src/styles/`](../packages/client/ui-theme/src/styles/)；本文不重复这份由源码生成的清单。
-
-## 职责归属
-
-[`ui-theme`](../packages/client/ui-theme/README.zh.md) 负责 `--dsw-*` 静态色阶、语义别名、排版、动效、渐变、阴影、滚动条样式以及明暗主题偏好。[`ui-layout`](../packages/client/ui-layout/README.zh.md) 将解析后的主题快照应用到文档。功能包使用语义别名，不得另行定义全局主题。
-
-全局样式表归 `ui-theme/src/styles/` 所有。组件样式以 CSS Modules 形式放在组件旁。当某个值属于该组件的布局或呈现约定时，组件可以定义局部自定义属性；共享颜色、排版、层级和动效属于主题包。
-
-## 组件规则
-
-- 使用 CSS Modules 和 `clsx`；不得添加组件库或 Tailwind。
-- 功能组件使用 `--dsw-alias-*` 语义 token。不得复制静态色板值或在其中写入颜色字面量。
-- 功能组件 CSS 不得包含主题选择器。明暗主题覆盖属于主题所有方。
-- 字体大小必须与行高配对；已有角色匹配时使用主题排版变量。
-- 当组件约定要求保留列结构时，源码文本、终端输出和 diff 行不得换行；使用共享滚动条样式，不得定义组件专用滚动条选择器。
-- 呈现规则写在 CSS 中。React 内联样式可以传递组件局部自定义属性值，但不得编码主题分支。
-- 添加过渡动画或仅悬停可见的控件时，保留清晰可见的键盘焦点和减少动态效果行为。
-- 支持的引擎上，圆角继承 ui-theme `corner-shape.css` 的全局超级椭圆平滑。每个正圆 `border-radius`（`50%`、`100%` 或胶囊半径）必须配对 `corner-shape: round`，使圆形与胶囊保持圆弧；ui-theme 的 corner-shape spec 强制这一配对。
-- 高层级表面（菜单、浮层、对话框、面板、悬浮按钮、输入框）设 `border: 0` 并使用 `box-shadow: var(--dsw-elevation-panel)`、`var(--dsw-elevation-prominent)` 或输入框专用的 `var(--dsw-elevation-soft)`（更大模糊、更低透明度）：0.5px 发丝描边是第一层投影，`--dsw-elevation-stroke-color` 可按表面或状态重绑或抑制描边。不得将 `--dsw-alias-border-*` border 与 lv/elevation 投影配对——ui-theme 的 elevation spec 会拒绝；状态色 border（warn 面板）保持真 border。
-- 使用中性 `--dsw-alias-border-*` token 的平面边框与分割线一律 `0.5px`——按钮、输入框、卡片、行分割线，以及以填充盒绘制的分隔线（菜单分隔、对话标题栏接缝、markdown `hr`、竖向轨道线）共用发丝线粗细，Chromium 将其绘制为一个设备像素。dashed 记号与状态色 border 保持 1px；spinner 圆环经 spec 的显式豁免保留原宽度。更宽的中性 solid border 会被 ui-theme elevation spec 拒绝。
-- 可点击产物链接（Markdown 锚点、正文文件引用、网页来源与抓取链接、产物 chips、workflow 成员链接）经 `--dsw-alias-link` 着色、`font-weight: 500`，默认无下划线，hover/focus 时为 3px offset 的点状下划线。带文字的锚点另以 ui-primitives 的 `LinkIcon` 分类图形（随 `currentColor`）作前置；workflow 成员链接与只包图片的锚点不带图形，工具行文件链接保持其灰色点线示能（[可点击链接 Agent Note](../.agents/notes/implemented/feature/2026-09-04-web-clickable-link-styles.zh.md)）。
-
-## 变更系统
-
-在所属 `ui-theme` 样式表中添加或修改共享 token，然后在功能包中使用其语义别名。公共样式约定发生变化时，更新所属包的参考文档。视觉行为遵循[测试策略](testing.zh.md)；[样式系统 Agent Note](../.agents/notes/implemented/process/2026-07-19-web-styling-system.zh.md) 记录框架依据。

package/node_modules/better-dsh/eval-description.md

@@ -1,33 +0,0 @@
-Run one Python cell on a session-persistent scripting pad. One `eval` call = one cell; the pad's state persists across calls and turns — variables, imports, and definitions from earlier cells stay alive.
-
-Work incrementally: imports → define → test → use, each its own cell. Re-run setup only after `reset` or a crash.
-
-## Arguments
-
-- `cell` (required): one Python program body. Top-level `await` works; top-level `return` is a SyntaxError — the cell runs in module scope (REPL semantics, not a function body).
-- `description` (required): a short summary of what the cell does — shown as the call's title in the UI.
-- `timeout` (optional): wall-clock budget in seconds; the cell is interrupted (then force-stopped) when exceeded. Omit for the runtime default.
-- `reset` (optional): restart the pad EMPTY first — earlier state is discarded.
-
-## Direct calls vs cells
-
-Payload-shaped work (one long read, one edit, one command) → direct tool call. Logic-shaped work (loops, conditions, fan-out, composing many tool results into one step) → an `eval` cell. Only what the cell prints or returns comes back — curate it.
-
-Delegation: `agent` is the unified agent-spawn entry; `subagent` is its native alias — both delegate through the same runtime, so call either.
-
-## Calling tools from a cell
-
-Every session tool is callable from a cell as `await tool.<name>(args)` with ONE positional argument: `args` is the tool's parameter object written as a Python dict literal, same field names (`true`/`false`/`null` become `True`/`False`/`None`). A failed call raises `ToolCallError` with `.toolName` naming the tool. Tool names that are not plain identifiers (e.g. contain hyphens) have no `tool.<name>` member — call those as direct tool calls.
-
-```python
-print(await tool.read({"path": "docs/README.md", "limit": 5}))
-
-r = await tool.bash({"command": "ls -la src/", "description": "List source directory"})
-print(r["stdout"]["text"])
-
-import asyncio
-matches, files = await asyncio.gather(
-    tool.grep({"pattern": "TODO", "path": "src"}),
-    tool.glob({"pattern": "**/*.ts", "path": "src"}),
-)
-```

package/node_modules/better-dsh/lib/BrowserWebSocketTransport-D1aFReu_.js

@@ -1,4 +0,0 @@
-import "./util-BHL_dfV_.js";
-import { t as BrowserWebSocketTransport } from "./BrowserWebSocketTransport-wm99h94r.js";
-
-export { BrowserWebSocketTransport };

package/node_modules/better-dsh/lib/BrowserWebSocketTransport-wm99h94r.js

@@ -1,39 +0,0 @@
-import { o as debugCatchError } from "./util-BHL_dfV_.js";
-
-//#region node_modules/puppeteer-core/lib/puppeteer/common/BrowserWebSocketTransport.js
-/**
-* @internal
-*/
-var BrowserWebSocketTransport = class BrowserWebSocketTransport {
-	static create(url) {
-		return new Promise((resolve, reject) => {
-			const ws = new WebSocket(url);
-			ws.addEventListener("open", () => {
-				return resolve(new BrowserWebSocketTransport(ws));
-			});
-			ws.addEventListener("error", reject);
-		});
-	}
-	#ws;
-	onmessage;
-	onclose;
-	constructor(ws) {
-		this.#ws = ws;
-		this.#ws.addEventListener("message", (event) => {
-			if (this.onmessage) this.onmessage.call(null, event.data);
-		});
-		this.#ws.addEventListener("close", () => {
-			if (this.onclose) this.onclose.call(null);
-		});
-		this.#ws.addEventListener("error", debugCatchError);
-	}
-	send(message) {
-		this.#ws.send(message);
-	}
-	close() {
-		this.#ws.close();
-	}
-};
-
-//#endregion
-export { BrowserWebSocketTransport as t };

package/node_modules/better-dsh/lib/LaunchOptions-B874eBu2.js

@@ -1,4 +0,0 @@
-import "./main-CupOhMp5.js";
-import { t as convertPuppeteerChannelToBrowsersChannel } from "./LaunchOptions-kGXcZOe0.js";
-
-export { convertPuppeteerChannelToBrowsersChannel };

package/node_modules/better-dsh/lib/LaunchOptions-kGXcZOe0.js

@@ -1,17 +0,0 @@
-import { b as ChromeReleaseChannel } from "./main-CupOhMp5.js";
-
-//#region node_modules/puppeteer-core/lib/puppeteer/node/LaunchOptions.js
-/**
-* @internal
-*/
-function convertPuppeteerChannelToBrowsersChannel(channel) {
-	switch (channel) {
-		case "chrome": return ChromeReleaseChannel.STABLE;
-		case "chrome-dev": return ChromeReleaseChannel.DEV;
-		case "chrome-beta": return ChromeReleaseChannel.BETA;
-		case "chrome-canary": return ChromeReleaseChannel.CANARY;
-	}
-}
-
-//#endregion
-export { convertPuppeteerChannelToBrowsersChannel as t };

package/node_modules/better-dsh/lib/NodeWebSocketTransport-BRLjmu2R.js

@@ -1,4 +0,0 @@
-import "./util-BHL_dfV_.js";
-import { t as NodeWebSocketTransport } from "./NodeWebSocketTransport-D9ysYGLM.js";
-
-export { NodeWebSocketTransport };