dsh-webui-studio 0.1.0 → 0.2.1

package/PRODUCT.md

@@ -26,7 +26,7 @@ Its defining mechanism is a stable DSH control plane paired with one isolated Gi
 
 ## Operating Context
 
-Studio is served by a stable local `dsh web` Host at `/studio`. The stable Host owns the Studio interface, Draft registry, and Agent sessions. Each running Draft is previewed by a separate child `dsh web` Host inside Studio's main iframe, which can expand to fullscreen.
+Studio is served by a stable local `dsh web` Host at `/studio`. The stable Host owns the Studio interface, Draft registry, and Agent sessions. Studio can inspect that Host's current WebUI directly in read-only mode. Each running Draft is previewed by a separate child `dsh web` Host inside Studio's main iframe, which can expand to fullscreen.
 
 Developers may create a minimal new Web Client plugin or import an existing local plugin folder as an isolated snapshot. A new plugin remains Studio-only by default; creation may record an optional absolute destination for a new or empty local folder, but Studio does not touch that folder until the user explicitly saves the project there. Later explicit saves synchronize the Studio snapshot without deleting destination-only files. Studio validates the Web Client manifest, excludes `.git` and `node_modules`, rejects symbolic links, and commits the copy into a Studio-owned Git repository without modifying the source folder. Draft repositories, worktrees, runtime homes, and registry records live under the stable Harness home's `studio` directory.
 
@@ -35,16 +35,20 @@ The normal loop is to start a Draft Preview Host, interact with the WebUI in Bro
 ## Capabilities and Constraints
 
 - Every Draft owns an isolated worktree, child Harness home, `profiles/web`, dependency installation, Harmony state, and Preview Host. Multiple Draft Preview Hosts may run at once.
-- The implemented profile mode snapshots the main `web` profile. Relative `link:` dependencies are made absolute and the Draft package is linked to its worktree. Custom profile configuration is intentionally unavailable until its editor exists; Studio must not silently fall back to the main profile.
+- A Draft snapshots either the main `web` profile or another local profile selected by absolute folder path. Relative `link:` dependencies are resolved against the selected source profile, and the Draft package is linked to its worktree. Studio never modifies the source profile and never silently falls back to the main profile.
 - Browse mode preserves normal WebUI interaction. Inspect mode captures a redacted DOM snapshot and provides best-effort React component, owner, and source mapping.
 - The Source panel edits UTF-8 files inside the selected Draft package. Builds use the package's fixed `scripts.build`; activation completes only after Preview confirms the new live Client graph revision.
 - Readiness inspection covers package identity, DSH exports, built and Patch artifacts, dependencies, Harmony state and order, target version bounds, and differential Source Patch providers. Package inspection uses `npm pack --dry-run --json --ignore-scripts` through the managed DSH subprocess runtime.
-- Agent sessions stay in the stable DSH and inherit its model and session configuration. Draft-specific Agent tooling may see the current selection, inspect Harmony, read installed dependency source without writing it, read and exactly patch Draft files, build and reload, and check Preview status. Preview-derived DOM, source, Patch, and comment data is untrusted evidence rather than Agent instruction. The child Preview Host does not own the Agent control plane.
+- Agent sessions stay in the stable DSH and retain their model, history, identity, and session configuration. Studio can create a session or temporarily attach an existing ordinary session. Entering Studio mode adds one scoped tool set, runtime skill, system instruction, and target context; leaving removes that scope and restores ordinary DSH composition. Current-instance mode exposes only read-only tools for the live DOM selection, Harmony profile and targets, installed dependency source, and Preview status. Draft mode additionally exposes Draft files, exact patches, build, and reload. The Agent panel answers pending one-shot tool approvals, structured questions, and plan reviews through the Host interaction protocol. Preview-derived DOM, source, Patch, and comment data is untrusted evidence rather than Agent instruction. The child Preview Host does not own the Agent control plane.
+- The stable Host exposes the same current-instance inspection set to out-of-process Agents through a stateless Streamable HTTP MCP endpoint at `/studio/mcp`. It remains loopback-only and contains no Draft write, build, reload, or profile mutation tools; the external Agent owns edits in its own workspace. Harmony and dependency inspection are Host-native, while live DOM selection is supplied by an open current-instance Studio Preview.
 - The official WebUI continues to use its own-origin `/api` and WebSockets. Studio does not proxy WebUI traffic or introduce a second backend address.
-- Draft labels are persisted independently from npm package names. Studio stores ordered open Draft tabs and the active Draft in `$DSH_HOME/studio/workspace.json`; closing every tab remains an explicit empty workspace across Host restarts. Plugin Management can reopen any persisted Draft, and closing a tab never stops or deletes it. Unsaved Source changes block tab switching and closing until saved.
+- Draft labels are persisted independently from npm package names. Studio stores ordered open Draft tabs and the active Draft in `$DSH_HOME/studio/workspace.json`; closing every tab remains an explicit empty workspace across Host restarts, and closing a tab never stops or deletes its Draft. Unsaved Source changes block tab switching and closing until saved.
+- Plugin Management reads the active Draft Preview's public Harmony profile and inspection. Provider controls stay in the sidebar; the wider Patch ordering workspace stages Patch order and enablement, then commits the Draft profile through one transactional hot reload. The stable Studio Host is never modified.
+- Element CSS editing persists generated, subtree-scoped CSS beside the registered Element source and restores the editable rule model after a Studio reload.
+- Automatic CSS Patch creation analyzes named Component declarations, presents every match for confirmation, and emits a Component decorator plus Draft client export without touching existing JSX call sites or Props.
 - Stopping a Draft terminates its child Host but preserves its repository, worktree, profile, and registry record. Closing the Studio page does not delete Drafts.
 - A Draft package must be a buildable DSH Web Client package with `dsh.client.platform: "web"`, the required package exports, and a non-empty `scripts.build`.
-- Studio is a local development surface. Its Host extension is disabled when `dsh web` is not bound to `127.0.0.1`.
+- Studio is a local development surface. Its Host plugin is disabled when `dsh web` is not bound to `127.0.0.1`.
 
 ## Brand Commitments
 
@@ -54,7 +58,7 @@ Studio is a focused developer environment rather than a decorative mod manager.
 
 ## Evidence on Hand
 
-- The runnable Studio Host extension and browser application live under `src`.
+- The runnable Studio Host plugin and browser application live under `src`.
 - The implemented architecture and development contract are documented in `README.md`.
 - Harmony runtime behavior and public terminology are documented in the repository root `README.md`.
 - React-aware patch factories available to Draft plugin authors are documented by the upstream `dsh-harmony-react` package.
@@ -66,7 +70,7 @@ Studio is a focused developer environment rather than a decorative mod manager.
 - Preserve the stable DSH environment: unfinished Draft code belongs in isolated Preview Hosts.
 - Express changes as distributable plugin and Harmony artifacts, not arbitrary edits to installed WebUI sources.
 - Preview the real system: retain DSH origin, plugin graph, data, and interaction semantics during testing.
-- Make state transitions explicit: distinguish staged, built, preview-pending, active, stopped, and preserved Draft state.
+- Make state transitions explicit: distinguish built, preview-pending, active, stopped, and preserved Draft state.
 - Keep the development loop layered and direct: inspect, edit, build, activate, and verify without hiding the underlying files or Patch behavior.
 
 ## Accessibility & Inclusion

package/README.md

@@ -16,17 +16,17 @@
   <p>
     <a href="#getting-started"><strong>Get started</strong></a>
     ·
-    <a href="https://github.com/CH4ACKO3/dsh-webui-studio/issues">Report a bug</a>
+    <a href="https://github.com/memorax-ai/dsh-webui-studio/issues">Report a bug</a>
     ·
-    <a href="https://github.com/CH4ACKO3/dsh-webui-studio/issues">Request a feature</a>
+    <a href="https://github.com/memorax-ai/dsh-webui-studio/issues">Request a feature</a>
   </p>
 
   [![License: MIT](https://img.shields.io/badge/license-MIT-0b63f6.svg)](LICENSE)
-  [![CI](https://github.com/CH4ACKO3/dsh-webui-studio/actions/workflows/ci.yml/badge.svg)](https://github.com/CH4ACKO3/dsh-webui-studio/actions/workflows/ci.yml)
+  [![CI](https://github.com/memorax-ai/dsh-webui-studio/actions/workflows/ci.yml/badge.svg)](https://github.com/memorax-ai/dsh-webui-studio/actions/workflows/ci.yml)
   [![npm](https://img.shields.io/npm/v/dsh-webui-studio.svg?color=0b63f6)](https://www.npmjs.com/package/dsh-webui-studio)
   [![Node.js](https://img.shields.io/badge/node-%5E22.22.3%20%7C%7C%20%3E%3D24.11.1-2f6f3e.svg)](package.json)
-  [![GitHub stars](https://img.shields.io/github/stars/CH4ACKO3/dsh-webui-studio?style=flat&color=0b63f6)](https://github.com/CH4ACKO3/dsh-webui-studio/stargazers)
-  [![Powered by Harmony](https://img.shields.io/badge/powered%20by-dsh--harmony-111827.svg)](https://github.com/CH4ACKO3/dsh-harmony)
+  [![GitHub stars](https://img.shields.io/github/stars/memorax-ai/dsh-webui-studio?style=flat&color=0b63f6)](https://github.com/memorax-ai/dsh-webui-studio/stargazers)
+  [![Powered by Harmony](https://memorax-ai.github.io/dsh-harmony/harmony-powered.svg)](https://memorax-ai.github.io/dsh-harmony/)
 
   [简体中文](README.zh-CN.md) / [English](README.md)
 </div>
@@ -39,7 +39,7 @@ distributable plugin-owned artifacts.
 
 Studio is an independent downstream application of
 [`dsh-harmony`](https://github.com/CH4ACKO3/dsh-harmony). It uses Harmony's
-public Host extension, runtime, Patch engine, and Draft APIs together with the
+public runtime, Patch engine, service API, and CLI control surface together with the
 generic React registration API from
 [`dsh-harmony-react`](https://github.com/CH4ACKO3/dsh-harmony/tree/main/packages/react).
 The dependency direction stays one-way: Studio depends on Harmony; Harmony does
@@ -51,12 +51,18 @@ not depend on Studio.
 - [x] Give every Draft its own Git worktree, `DSH_HOME`, profile, dependencies, and child Host
 - [x] Preview the official WebUI without loading Draft code into the stable Host
 - [x] Browse normally or inspect DOM, React owners, source candidates, and Patch traces
+- [x] Surface plugin-registered Element controls automatically; save defaults and subtree-scoped CSS back to Draft source
+- [x] Review Component declaration matches and generate CSS decorators without changing existing call-site props
+- [x] Reorder and toggle both Harmony providers and individual Patches through one transactional reload
 - [x] Edit Draft source with CodeMirror and protect installed dependency sources as read-only
 - [x] Build, apply through Harmony, reload, and confirm the live Client graph revision
-- [x] Run Draft-scoped DSH Agents with explicit Studio tools
+- [x] Start a Draft-scoped Agent or continue an existing DSH session with temporary Studio tools, skill, and context
+- [x] Let an external Agent inspect the running WebUI through a local read-only Streamable HTTP MCP endpoint
+- [x] Answer one-shot tool approvals, structured questions, and plan reviews without leaving Studio
 - [x] Check package exports, artifacts, Patch state, ordering, dependencies, and pack output
 - [x] Run multiple isolated Draft Preview Hosts at the same time
-- [ ] Configure custom Draft profiles in the UI
+- [x] Snapshot the current WebUI profile or another local profile into each isolated Draft runtime
+- [x] Reorder plugins and enable or disable Harmony Providers through one transactional hot reload
 
 ## How it works
 
@@ -75,6 +81,9 @@ The stable Host owns the Studio interface, Draft registry, and Agent sessions.
 Each Draft owns an isolated worktree and child Preview Host. A build becomes
 active only after the Preview confirms the new live Client graph revision.
 Stopping a Draft terminates its child Host but preserves its files and state.
+An existing ordinary DSH session can enter Studio mode without losing its
+history or identity. Leaving Studio removes the scoped Draft tools, skill, and
+context so the session resumes through its ordinary DSH composition.
 
 Studio is served locally at:
 
@@ -82,6 +91,35 @@ Studio is served locally at:
 http://127.0.0.1:<dsh-port>/studio
 ```
 
+External Agents can connect to the running instance through MCP at:
+
+```text
+http://127.0.0.1:<dsh-port>/studio/mcp
+```
+
+A typical MCP client entry is:
+
+```json
+{
+  "mcpServers": {
+    "dsh-webui-studio": {
+      "type": "http",
+      "url": "http://127.0.0.1:<dsh-port>/studio/mcp"
+    }
+  }
+}
+```
+
+Add that URL as a Streamable HTTP MCP server in the external Agent. It exposes
+`studio_get_context`, `studio_get_selection`, `studio_get_harmony_profile`,
+`studio_inspect_harmony_target`, `studio_read_dependency_source`, and
+`studio_preview_status`. These tools inspect the current Host only; the external
+Agent remains responsible for editing and building its own WebUI project. Harmony
+profile, Patch, and dependency-source inspection work directly from the Host.
+DOM selection is available while Studio is open and an element is selected in
+the current-instance Preview. The endpoint follows Studio's existing loopback-only
+boundary, including access through an SSH loopback tunnel.
+
 Its managed data lives under `$DSH_HOME/studio/`:
 
 ```text
@@ -104,33 +142,39 @@ its Web Client manifest, then copies an isolated snapshot without `.git` or
 `node_modules` into a Studio-owned Git repository. Symbolic links are rejected,
 and the original folder is never modified.
 
+Each Draft can start from the stable Host's current `web` profile or from
+another local DSH profile selected by absolute folder path. Studio copies that
+profile's manifest and configuration into the isolated runtime and resolves
+relative `link:` dependencies against the selected source folder. The source
+profile remains untouched.
+
 Draft display names are independent from npm package identities and can be
 renamed in the instance panel. Studio persists the ordered open tabs and active
 Draft in `workspace.json`; closing a tab only removes it from the current
-workspace and never stops or deletes the Draft. Plugin Management can reopen
-any persisted Draft. Unsaved Source changes must be saved with `Ctrl+S` or
+workspace and never stops or deletes the Draft. Unsaved Source changes must be saved with `Ctrl+S` or
 `Command+S` before switching or closing tabs.
 
 ## Getting started
 
 > [!IMPORTANT]
-> Studio requires the public Harmony extension and Draft APIs documented in
+> Studio requires the public Harmony service and CLI APIs documented in
 > [`docs/harmony-api-requirements.md`](docs/harmony-api-requirements.md).
-> `dsh-harmony@0.1.3` is the minimum compatible release.
+> `dsh-harmony@0.8.7` is the minimum compatible release.
 
 ```sh
-dsh plugin --profile web add dsh-webui-studio --allow-build=dsh-harmony
+dsh plugin --profile web add dsh-webui-studio
 dsh web
 ```
 
-Harmony is resolved transitively and does not need to be installed as a second
-plugin. The build permission allows its global-only DSH shim installer; normal
-profile installs do not modify the global command.
+Studio includes Harmony as a transitive dependency. On the first visit to
+`/studio`, approve **Install Harmony and restart**; the page installs the
+launcher and returns to Studio after the local DSH process restarts. No second
+package command is required. An existing Harmony launcher skips this setup.
 
 To develop Studio itself from source:
 
 ```sh
-git clone https://github.com/CH4ACKO3/dsh-webui-studio.git
+git clone https://github.com/memorax-ai/dsh-webui-studio.git
 cd dsh-webui-studio
 npm install
 npm run check
@@ -143,8 +187,7 @@ To exercise the same single-package installation path as a release artifact:
 
 ```sh
 studio_tarball="$(npm pack --silent --ignore-scripts)"
-dsh plugin --profile web add "file:$(pwd)/${studio_tarball}" \
-  --allow-build=dsh-harmony
+dsh plugin --profile web add "file:$(pwd)/${studio_tarball}"
 ```
 
 Open the Studio URL printed by the local `dsh web` process, create or import a
@@ -166,6 +209,9 @@ A Draft package must:
 | `npm run check` | Run typecheck, tests, build, and packed fresh-install integration |
 | `npm run test:integration` | Pack and install the tarball in a fresh DSH home, then exercise Host, Draft, Preview, build, activation, and shutdown end to end |
 
+For isolated Agent environments on a remote Docker host, see
+[`docs/remote-development.md`](docs/remote-development.md).
+
 The integration test requires a Harmony build that exposes the APIs described
 in the compatibility note above.
 
@@ -176,6 +222,8 @@ in the compatibility note above.
 - Preview DOM, React, source, Patch, and comment data is treated as untrusted evidence.
 - Source writes stay inside the selected Draft package and never follow symbolic links outside it.
 - Registered element boundaries and Patch traces are candidate evidence, not claims of exact DOM ownership.
+- Element controls change the live Preview through plugin bindings. **Save to plugin source** updates declared default initializers and generated subtree-scoped CSS inside the Draft worktree; it never rewrites component use sites or freezes the runtime binding.
+- Automatic CSS Patch creation uses a Harmony React Component decorator. Studio shows every matching declaration before writing, adds an immediately available Draft client export, and leaves all existing JSX calls and Props intact.
 
 ## Frequently asked questions
 
@@ -201,11 +249,11 @@ The DSH WebUI exposes many useful slots, but Studio aims for deeper and more
 flexible changes—including UI and behavior introduced by other plugins—while
 keeping independently authored modifications as compatible as possible.
 [`dsh-harmony`](https://github.com/CH4ACKO3/dsh-harmony) provides the runtime
-patching and extension model that makes this possible.
+patching and runtime model that makes this possible.
 
 ## Related projects
 
-- [`dsh-harmony`](https://github.com/CH4ACKO3/dsh-harmony) - runtime patching, Host extension mounting, Draft lifecycle, and Patch inspection
+- [`dsh-harmony`](https://github.com/CH4ACKO3/dsh-harmony) - runtime patching, transactional plugin reloads, and Patch inspection
 - [`dsh-harmony-react`](https://github.com/CH4ACKO3/dsh-harmony/tree/main/packages/react) - React-aware Patch factories and Studio element/variable registration
 
 ## License

package/README.zh-CN.md

@@ -16,17 +16,17 @@
   <p>
     <a href="#快速开始"><strong>快速开始</strong></a>
     ·
-    <a href="https://github.com/CH4ACKO3/dsh-webui-studio/issues">报告问题</a>
+    <a href="https://github.com/memorax-ai/dsh-webui-studio/issues">报告问题</a>
     ·
-    <a href="https://github.com/CH4ACKO3/dsh-webui-studio/issues">功能建议</a>
+    <a href="https://github.com/memorax-ai/dsh-webui-studio/issues">功能建议</a>
   </p>
 
   [![License: MIT](https://img.shields.io/badge/license-MIT-0b63f6.svg)](LICENSE)
-  [![CI](https://github.com/CH4ACKO3/dsh-webui-studio/actions/workflows/ci.yml/badge.svg)](https://github.com/CH4ACKO3/dsh-webui-studio/actions/workflows/ci.yml)
+  [![CI](https://github.com/memorax-ai/dsh-webui-studio/actions/workflows/ci.yml/badge.svg)](https://github.com/memorax-ai/dsh-webui-studio/actions/workflows/ci.yml)
   [![npm](https://img.shields.io/npm/v/dsh-webui-studio.svg?color=0b63f6)](https://www.npmjs.com/package/dsh-webui-studio)
   [![Node.js](https://img.shields.io/badge/node-%5E22.22.3%20%7C%7C%20%3E%3D24.11.1-2f6f3e.svg)](package.json)
-  [![GitHub stars](https://img.shields.io/github/stars/CH4ACKO3/dsh-webui-studio?style=flat&color=0b63f6)](https://github.com/CH4ACKO3/dsh-webui-studio/stargazers)
-  [![Powered by Harmony](https://img.shields.io/badge/powered%20by-dsh--harmony-111827.svg)](https://github.com/CH4ACKO3/dsh-harmony)
+  [![GitHub stars](https://img.shields.io/github/stars/memorax-ai/dsh-webui-studio?style=flat&color=0b63f6)](https://github.com/memorax-ai/dsh-webui-studio/stargazers)
+  [![Powered by Harmony](https://memorax-ai.github.io/dsh-harmony/harmony-powered.svg)](https://memorax-ai.github.io/dsh-harmony/)
 
   [简体中文](README.zh-CN.md) / [English](README.md)
 </div>
@@ -37,8 +37,8 @@ WebUI Studio 不是模拟页面生成器。它运行在官方 DSH WebUI 和真
 把可视化检查与源码修改转化为可分发、由插件自身拥有的产物。
 
 Studio 是 [`dsh-harmony`](https://github.com/CH4ACKO3/dsh-harmony)
-的独立下游应用。它通过公共 package exports 使用 Harmony 的 Host extension、runtime、
-Patch engine 与 Draft API，并使用
+的独立下游应用。它通过公共 package exports 使用 Harmony 的 runtime、Patch engine、
+service API 与 CLI 控制面，并使用
 [`dsh-harmony-react`](https://github.com/CH4ACKO3/dsh-harmony/tree/main/packages/react)
 提供的通用 React 注册 API。依赖始终保持单向：Studio 依赖 Harmony，Harmony 不依赖 Studio。
 
@@ -48,12 +48,18 @@ Patch engine 与 Draft API，并使用
 - [x] 为每个 Draft 分配独立 Git worktree、`DSH_HOME`、profile、依赖树和 child Host
 - [x] 预览官方 WebUI，同时不把 Draft 代码加载进稳定 Host
 - [x] 正常浏览，或检查 DOM、React owner、源码候选和 Patch trace
+- [x] 自动展示插件注册的 Element 控件，并将默认值与限定在当前子树内的 CSS 保存回草稿源码
+- [x] 检查 Component 声明命中后生成 CSS decorator，不修改既有调用点 Props
+- [x] 通过一次事务热重载调整 Harmony Provider 与单个 Patch 的顺序和启停状态
 - [x] 使用 CodeMirror 编辑 Draft 源码，并保持已安装依赖源码只读
 - [x] 构建、经 Harmony 应用、重载，并确认实时 Client graph revision
-- [x] 运行带显式 Studio tools 的 Draft 级 DSH Agent
+- [x] 新建 Draft 级 Agent，或让已有 DSH 会话临时挂载 Studio tools、Skill 与上下文后继续工作
+- [x] 让外部 Agent 通过本机只读 Streamable HTTP MCP 入口检查正在运行的 WebUI
+- [x] 无需离开 Studio 即可处理单次工具授权、结构化问题和计划审核
 - [x] 检查 package exports、构建产物、Patch 状态、顺序、依赖和 pack 输出
 - [x] 同时运行多个相互隔离的 Draft Preview Host
-- [ ] 在 UI 中配置自定义 Draft profile
+- [x] 将当前 WebUI profile 或其它本地 profile 复制到每个 Draft 的隔离运行环境
+- [x] 通过一次事务热重载调整插件顺序并启停 Harmony Provider
 
 ## 工作原理
 
@@ -71,6 +77,8 @@ flowchart LR
 稳定 Host 负责 Studio 界面、Draft registry 和 Agent session。每个 Draft 拥有隔离的
 worktree 与 child Preview Host。只有在 Preview 确认新的实时 Client graph revision 后，
 构建结果才会激活。停止 Draft 只终止 child Host，不会删除文件和状态。
+已有普通 DSH 会话可以在不丢失历史或会话身份的情况下进入 Studio 模式。退出 Studio
+会移除 Draft 专属的工具、Skill 与上下文，让会话恢复为普通 DSH 组合。
 
 Studio 的本地地址为：
 
@@ -78,6 +86,33 @@ Studio 的本地地址为：
 http://127.0.0.1:<dsh-port>/studio
 ```
 
+外部 Agent 可以通过以下 MCP 地址连接正在运行的实例：
+
+```text
+http://127.0.0.1:<dsh-port>/studio/mcp
+```
+
+常见 MCP 客户端可使用如下配置：
+
+```json
+{
+  "mcpServers": {
+    "dsh-webui-studio": {
+      "type": "http",
+      "url": "http://127.0.0.1:<dsh-port>/studio/mcp"
+    }
+  }
+}
+```
+
+在外部 Agent 中将该地址添加为 Streamable HTTP MCP server，即可调用
+`studio_get_context`、`studio_get_selection`、`studio_get_harmony_profile`、
+`studio_inspect_harmony_target`、`studio_read_dependency_source` 和
+`studio_preview_status`。这些工具只检查当前 Host；外部 Agent 继续负责修改和构建自己的
+WebUI 项目。Harmony profile、Patch 与依赖源码检查由 Host 直接提供。DOM 选择信息需要
+打开 Studio，并在“当前实例”Preview 中选中元素。MCP 入口沿用 Studio 仅限 loopback
+访问的边界，也可以通过 SSH loopback tunnel 使用。
+
 托管数据位于 `$DSH_HOME/studio/`：
 
 ```text
@@ -97,30 +132,35 @@ Studio 只接受本机绝对文件夹路径；验证 Web Client manifest 后，
 `node_modules`，将快照复制到 Studio 自有 Git repository。符号链接会被拒绝，原插件
 文件夹始终保持只读且不会被修改。
 
+每个 Draft 可以使用稳定 Host 当前的 `web` profile，也可以通过绝对文件夹路径选择
+另一个本地 DSH profile。Studio 会将其清单与配置复制到 Draft 的隔离运行环境，并以
+所选源文件夹为基准解析相对 `link:` 依赖；源 profile 始终不会被修改。
+
 Draft 显示名与 npm package identity 相互独立，可在实例面板中重命名。Studio 会在
 `workspace.json` 中保存标签顺序与当前 Draft；关闭标签只会将其移出当前工作区，不会
-停止或删除 Draft。所有持久化 Draft 都可以从插件管理页重新打开。Source 存在未保存
+停止或删除 Draft。Source 存在未保存
 修改时，必须先按 `Ctrl+S` 或 `Command+S` 保存，才能切换或关闭标签。
 
 ## 快速开始
 
 > [!IMPORTANT]
 > Studio 依赖 [`docs/harmony-api-requirements.md`](docs/harmony-api-requirements.md)
-> 中列出的 Harmony 公共 extension 与 Draft API，最低兼容版本为
-> `dsh-harmony@0.1.3`。
+> 中列出的 Harmony 公共 service 与 CLI API，最低兼容版本为
+> `dsh-harmony@0.8.7`。
 
 ```sh
-dsh plugin --profile web add dsh-webui-studio --allow-build=dsh-harmony
+dsh plugin --profile web add dsh-webui-studio
 dsh web
 ```
 
-Harmony 会作为传递依赖自动解析，无需作为第二个插件单独安装。该构建权限用于允许其
-仅在全局安装时生效的 DSH shim 安装器；普通 profile 安装不会修改全局命令。
+Studio 会把 Harmony 作为传递依赖一并安装。第一次访问 `/studio` 时，点击
+**安装 Harmony 并重启**；页面会安装 launcher，并在本地 DSH 进程重启后自动返回
+Studio，无需再执行第二条 package 安装命令。已经安装 Harmony launcher 时会跳过此步骤。
 
 如需开发 Studio 本身：
 
 ```sh
-git clone https://github.com/CH4ACKO3/dsh-webui-studio.git
+git clone https://github.com/memorax-ai/dsh-webui-studio.git
 cd dsh-webui-studio
 npm install
 npm run check
@@ -133,8 +173,7 @@ dsh web
 
 ```sh
 studio_tarball="$(npm pack --silent --ignore-scripts)"
-dsh plugin --profile web add "file:$(pwd)/${studio_tarball}" \
-  --allow-build=dsh-harmony
+dsh plugin --profile web add "file:$(pwd)/${studio_tarball}"
 ```
 
 打开本地 `dsh web` 进程输出的 Studio 地址，创建或导入 Draft，然后启动它的 Preview Host。
@@ -155,6 +194,9 @@ Draft package 必须：
 | `npm run check` | 运行 typecheck、测试、构建和 tarball 全新安装集成验证 |
 | `npm run test:integration` | 将 tarball 安装到全新的 DSH home，再端到端验证 Host、Draft、Preview、构建、激活与停止 |
 
+如需在远程 Docker 主机上运行相互隔离的 Agent 开发环境，请参阅
+[`docs/remote-development.md`](docs/remote-development.md)。
+
 集成测试需要 Harmony build 已公开兼容性说明中列出的 API。
 
 ## 设计边界
@@ -164,6 +206,8 @@ Draft package 必须：
 - 来自 Preview 的 DOM、React、源码、Patch 与注释数据均被视为不可信证据。
 - 源码写入始终限制在所选 Draft package 内，且不会沿符号链接写到外部。
 - 已注册 element boundary 与 Patch trace 只是候选证据，不代表对 DOM 的精确所有权声明。
+- Element 控件通过插件 binding 修改实时 Preview。“保存到插件源码”会在 Draft 工作树中更新插件声明的默认初始化值与限定子树 CSS，不会改写组件使用位置，也不会固定运行时 binding。
+- 自动 CSS Patch 使用 Harmony React 的 Component decorator。Studio 会先展示所有声明命中，再写入可立即加载的 Draft client export；现有 JSX 调用与 Props 保持不变。
 
 ## 常见问题
 
@@ -184,11 +228,11 @@ Agent，而是为 Agent 和开发者提供更好的交互式修改体验。
 DSH WebUI 已经提供了许多 Slot 点位，但 Studio 不满足于此。我们希望实现更深层、
 更高自由度的修改，包括修改其他插件加入的 UI 和逻辑，同时让不同修改插件之间尽可能
 兼容。[`dsh-harmony`](https://github.com/CH4ACKO3/dsh-harmony) 提供的运行时 Patch 与
-扩展模型，让这种能力成为可能。
+运行时模型，让这种能力成为可能。
 
 ## 相关项目
 
-- [`dsh-harmony`](https://github.com/CH4ACKO3/dsh-harmony) - runtime patch、Host extension 挂载、Draft 生命周期与 Patch 检查
+- [`dsh-harmony`](https://github.com/CH4ACKO3/dsh-harmony) - runtime patch、事务式插件重载与 Patch 检查
 - [`dsh-harmony-react`](https://github.com/CH4ACKO3/dsh-harmony/tree/main/packages/react) - React-aware Patch 工厂与 Studio element/variable 注册
 
 ## 许可证