dsh-mobile 0.1.0-alpha.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Guangqi Zhang
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,207 @@
+<p align="center">
+  <img src="https://unpkg.com/dsh-mobile@0.1.0-alpha.1/assets/brand/repository-hero.png" alt="A lively whale girl using a phone beside a desktop running DSH" width="100%">
+</p>
+
+<h1 align="center">DSH Mobile</h1>
+
+<p align="center">Private, authenticated LAN access to the stock DeepSeek Harness Web UI.</p>
+
+<p align="center">
+  <a href="https://www.npmjs.com/package/dsh-mobile"><img src="https://img.shields.io/npm/v/dsh-mobile?label=npm&amp;color=CB3837" alt="npm version"></a>
+  <a href="https://www.npmjs.com/package/dsh-mobile"><img src="https://img.shields.io/npm/dm/dsh-mobile?color=2563EB" alt="npm downloads"></a>
+  <img src="https://img.shields.io/badge/build-verified-059669" alt="Verified build">
+  <a href="apps/mobile/README.md"><img src="https://img.shields.io/badge/platform-Android-3DDC84?logo=android&amp;logoColor=white" alt="Android"></a>
+  <a href="#a-native-dsh-plugin"><img src="https://img.shields.io/badge/DSH-stock%20compatible-2563EB" alt="Compatible with stock DSH"></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-0F172A" alt="Apache-2.0 license"></a>
+</p>
+
+<p align="center">
+  <a href="README.zh.md">简体中文</a> ·
+  <a href="#quick-start">Quick start</a> ·
+  <a href="#customize-the-mobile-web-ui">Customize the UI</a> ·
+  <a href="#uninstall">Uninstall</a>
+</p>
+
+> Public npm alpha. The source repository remains private during the current testing phase. Android is the only supported native app. This is a community project, not an official DeepSeek product.
+
+DSH Mobile reuses DSH's own Web application, sessions, and plugin slots. It adds an authenticated HTTPS gateway, device pairing, session revocation, and a small responsive Client face. Use the Android shell without browser chrome, or open the same LAN address directly in any mobile browser.
+
+## Features
+
+| Capability | Android app | Mobile browser |
+| --- | :---: | :---: |
+| Live DSH Web UI | Yes | Yes |
+| Authenticated HTTPS LAN access | Yes | Yes |
+| One-time device pairing | Yes | Yes |
+| Custom mobile CSS | Yes | Yes |
+| File selection and downloads | Yes | Browser-dependent |
+| iOS native app | Not yet | Safari can use the Web UI |
+
+Host-native actions such as opening desktop files remain subject to stock DSH and operating-system restrictions. Treat every paired device as a fully trusted operator of the computer, not as a guest account.
+
+## Quick start
+
+Prerequisites: stock DSH can run through either an installed `dsh` command or the source checkout's `pnpm dsh` script, and the computer and Android device share a trusted private LAN. DSH requires Node.js 22.19.x or Node.js 24 or later.
+
+### Choose the DSH command
+
+If `dsh` is available in the terminal, use the commands below as written.
+
+If you cloned the DSH source and do not have a global `dsh` command, first install its workspace dependencies from the DSH repository root:
+
+```powershell
+corepack enable
+pnpm install
+```
+
+Then replace `dsh` in every example with `pnpm dsh`. The complete source-checkout flow is:
+
+```powershell
+pnpm dsh plugin --profile web add dsh-mobile
+pnpm dsh plugin --profile web exec dsh-mobile setup
+pnpm dsh --profile web
+```
+
+You may also invoke the source checkout from another directory without creating a global command:
+
+```powershell
+pnpm --dir "<path-to-deepseek-harness>" dsh --profile web
+```
+
+### 1. Install
+
+Install the public package directly from npm:
+
+```powershell
+dsh plugin --profile web add dsh-mobile
+```
+
+Repository collaborators and offline installations may instead install an exact tarball:
+
+```powershell
+dsh plugin --profile web add "<path-to-dsh-mobile.tgz>"
+```
+
+No DSH source patch or custom DSH build is required.
+
+### 2. Run setup once
+
+```powershell
+dsh plugin --profile web exec dsh-mobile setup
+```
+
+The setup command selects a private LAN address, creates a local TLS certificate, and stores all plugin-owned configuration under `$DSH_HOME/mobile-access/`. If more than one LAN address is available, select one explicitly:
+
+```powershell
+dsh plugin --profile web exec dsh-mobile setup --address 192.168.1.20
+```
+
+For a non-default DSH Web port:
+
+```powershell
+dsh plugin --profile web exec dsh-mobile setup --dsh-port 39080
+dsh --profile web --port 39080
+```
+
+### 3. Start and pair
+
+```powershell
+dsh --profile web
+```
+
+1. Copy the generated `dsh-mobile-ca.cer` to Android and install it as a user CA certificate.
+2. Open the Mobile card in the lower-left corner of the desktop DSH UI.
+3. Start access and create a pairing link. The link is copied to the clipboard.
+4. Paste the link into the Android app, or open it directly in a mobile browser.
+
+Pairing links expire after two minutes and work once. The app and each browser have separate cookie stores, so pair them separately.
+
+## Everyday control
+
+The Mobile card remains in DSH's lower-left corner. Stopping mobile access closes only the external HTTPS listener and active mobile sessions; the local DSH Web UI keeps running. Starting it again does not reinstall the plugin.
+
+The two access modes are equivalent:
+
+- Android app: a thin system WebView shell without browser address and tab bars.
+- Mobile browser: open the setup origin directly; no app installation is required.
+
+## Customize the mobile Web UI
+
+Setup creates:
+
+```text
+$DSH_HOME/mobile-access/mobile.css
+```
+
+This file loads only through the authenticated mobile gateway. It does not modify the DSH installation and survives DSH upgrades.
+
+Basic theme controls:
+
+```css
+:root {
+  --dsh-mobile-accent: #2563eb;
+  --dsh-mobile-font-scale: 1.05;
+  --dsh-mobile-radius: 16px;
+}
+```
+
+Narrow-screen adjustments:
+
+```css
+@media (max-width: 720px) {
+  textarea { min-height: 88px; }
+  button, [role='button'] { min-height: 48px; }
+}
+```
+
+Prefer CSS variables, spacing, typography, and touch sizes. Do not depend on generated class names. Delete `mobile.css` and refresh to return to the built-in defaults.
+
+## A native DSH plugin
+
+One standard bundle contributes two faces: the Host face owns the gateway and loopback control route; the Client face owns the responsive layer and desktop control card. The package injects only stock `webServer`, installs with `dsh plugin add`, and uninstalls with `dsh plugin remove`.
+
+```mermaid
+flowchart LR
+  Phone["Android app or mobile browser"] -->|"HTTPS and paired session"| Gateway["DSH Mobile plugin"]
+  Gateway -->|"loopback-only proxy"| DSH["Stock DSH Web UI"]
+```
+
+## Security model
+
+- The gateway accepts only the selected private LAN CIDR, exact Host, and same-origin browser requests.
+- The Android app never bypasses TLS validation. The certificate must cover the LAN address in use.
+- Pairing creates an HttpOnly session; devices and active sessions can be revoked from the computer.
+- Control and device-management routes are loopback-only.
+- Authentication happens before any request reaches the stock DSH loopback server. DSH itself is never rebound to `0.0.0.0`.
+
+Do not expose this gateway through public Wi-Fi, port forwarding, a public IP, or an untrusted VPN. See [SECURITY.md](SECURITY.md).
+
+## Uninstall
+
+Normal removal preserves certificates, paired devices, and custom CSS:
+
+```powershell
+dsh plugin --profile web remove dsh-mobile
+```
+
+To remove all local data, purge before removing the package:
+
+```powershell
+dsh plugin --profile web exec dsh-mobile purge --yes
+dsh plugin --profile web remove dsh-mobile
+```
+
+## Android app
+
+The supported native shell lives in [`apps/mobile/android`](apps/mobile/android). It does not bundle a copy of the DSH frontend; it renders the same authenticated HTTPS page used by mobile browsers. See the [Android guide](apps/mobile/README.md).
+
+## Development
+
+```powershell
+npm ci
+npm run verify
+```
+
+Release validation starts from the actual `npm pack` tarball and exercises install, setup, boot, pairing, and uninstall against an isolated stock DSH Web profile.
+
+Apache-2.0 licensed. See [LICENSE](LICENSE).

package/README.zh.md

@@ -0,0 +1,213 @@
+<p align="center">
+  <img src="https://unpkg.com/dsh-mobile@0.1.0-alpha.1/assets/brand/repository-hero.png" alt="鲸鱼娘拿着手机连接桌面上的 DSH" width="100%">
+</p>
+
+<h1 align="center">DSH Mobile</h1>
+
+<p align="center">让手机通过受保护的局域网连接直接控制原生 DeepSeek Harness Web UI。</p>
+
+<p align="center">
+  <a href="https://www.npmjs.com/package/dsh-mobile"><img src="https://img.shields.io/npm/v/dsh-mobile?label=npm&amp;color=CB3837" alt="npm 版本"></a>
+  <a href="https://www.npmjs.com/package/dsh-mobile"><img src="https://img.shields.io/npm/dm/dsh-mobile?color=2563EB" alt="npm 下载量"></a>
+  <img src="https://img.shields.io/badge/build-verified-059669" alt="构建已验证">
+  <a href="apps/mobile/README.zh-CN.md"><img src="https://img.shields.io/badge/platform-Android-3DDC84?logo=android&amp;logoColor=white" alt="Android"></a>
+  <a href="#为什么符合-dsh-的插件理念"><img src="https://img.shields.io/badge/DSH-stock%20compatible-2563EB" alt="兼容原生 DSH"></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-0F172A" alt="Apache-2.0 许可证"></a>
+</p>
+
+<p align="center">
+  <a href="README.md">English</a> ·
+  <a href="#快速开始">快速开始</a> ·
+  <a href="#自定义移动端-web-ui">自定义 UI</a> ·
+  <a href="#卸载">卸载</a>
+</p>
+
+> 当前为公开 npm Alpha，源码仓库在测试阶段暂时保持私有，仅支持 Android。它是社区项目，不是 DeepSeek 官方产品。
+
+DSH Mobile 不是另一套远程控制面板。插件直接复用 DSH 自己的 Web 应用、会话和插件槽位，在外层增加 HTTPS、设备配对、会话撤销和移动端样式。你可以用 Android App 获得无浏览器栏的体验，也可以直接用手机浏览器访问同一个局域网地址。
+
+## 主要能力
+
+| 能力 | Android App | 手机浏览器 |
+| --- | :---: | :---: |
+| 实时访问 DSH Web UI | 支持 | 支持 |
+| HTTPS 局域网入口 | 支持 | 支持 |
+| 一次性设备配对 | 支持 | 支持 |
+| 自定义移动端 CSS | 支持 | 支持 |
+| 文件选择与下载 | 支持 | 由浏览器决定 |
+| iOS | 暂不支持 | 可用 Safari 访问网页 |
+
+宿主文件选择器、打开本机文档等动作仍受原生 DSH 和操作系统限制。配对设备应视为电脑上的完全可信操作者，而不是低权限访客。
+
+## 快速开始
+
+前置条件：能够通过已经安装的 `dsh` 命令或源码仓库中的 `pnpm dsh` 启动原生 DSH，电脑和 Android 手机位于同一可信局域网。DSH 需要 Node.js 22.19.x，或 Node.js 24 以上版本。
+
+### 选择 DSH 命令
+
+如果终端中能够直接运行 `dsh`，后续命令保持原样即可。
+
+如果你直接克隆了 DSH 源码，没有全局 `dsh` 命令，请先在 DSH 源码根目录安装工作区依赖：
+
+```powershell
+corepack enable
+pnpm install
+```
+
+然后把后续示例中的 `dsh` 全部替换为 `pnpm dsh`。源码版的完整快速启动命令如下：
+
+```powershell
+pnpm dsh plugin --profile web add dsh-mobile
+pnpm dsh plugin --profile web exec dsh-mobile setup
+pnpm dsh --profile web
+```
+
+如果当前终端不在 DSH 源码目录，也不需要创建全局命令：
+
+```powershell
+pnpm --dir "<DSH源码目录>" dsh --profile web
+```
+
+### 1. 安装插件
+
+直接从公开 npm 安装：
+
+```powershell
+dsh plugin --profile web add dsh-mobile
+```
+
+仓库协作者或离线环境也可以安装指定 tarball：
+
+```powershell
+dsh plugin --profile web add "<插件安装包路径>"
+```
+
+这两种方式都使用 DSH 官方插件命令，不需要修改或替换 DSH 源码。
+
+### 2. 运行一次设置向导
+
+```powershell
+dsh plugin --profile web exec dsh-mobile setup
+```
+
+向导会自动选择唯一的私有局域网地址，生成本地 TLS 证书，并把配置保存到 `$DSH_HOME/mobile-access/`。如果电脑有多个可用网卡，向导会列出候选地址并要求明确选择：
+
+```powershell
+dsh plugin --profile web exec dsh-mobile setup --address 192.168.1.20
+```
+
+如果 DSH Web 使用非默认端口，也可以一次指定：
+
+```powershell
+dsh plugin --profile web exec dsh-mobile setup --dsh-port 39080
+dsh --profile web --port 39080
+```
+
+### 3. 启动、配对与连接
+
+```powershell
+dsh --profile web
+```
+
+1. 将向导输出的 `dsh-mobile-ca.cer` 复制到 Android，并在系统设置中安装为用户 CA 证书。
+2. 在电脑 DSH 左下角打开“移动端”卡片。
+3. 确认服务已开启，点击“生成配对链接”。链接会复制到剪贴板。
+4. 在 Android App 中粘贴链接，或直接在手机浏览器中打开链接。
+
+配对链接两分钟内有效且只能使用一次。App 与浏览器拥有各自的 Cookie 存储，因此需要分别配对。
+
+## 日常使用
+
+安装后，“移动端”卡片会常驻 DSH 左下角。关闭移动访问只会停止外部 HTTPS 监听并断开移动会话，不会停止 DSH 本身；重新开启不需要再次安装插件。
+
+手机有两种等价入口：
+
+- Android App：使用系统 WebView 打开同一 DSH 页面，没有浏览器地址栏和标签栏。
+- 手机浏览器：直接访问向导显示的 `https://局域网地址:端口`，无需安装 App。
+
+## 自定义移动端 Web UI
+
+设置向导会创建：
+
+```text
+$DSH_HOME/mobile-access/mobile.css
+```
+
+它只在通过移动网关访问时加载，不修改 DSH 安装目录，升级或卸载 DSH 时也不会覆盖它。修改后刷新手机页面即可看到效果。
+
+### 最简单的主题调整
+
+```css
+:root {
+  --dsh-mobile-accent: #2563eb;
+  --dsh-mobile-font-scale: 1.05;
+  --dsh-mobile-radius: 16px;
+}
+```
+
+### 只调整窄屏布局
+
+```css
+@media (max-width: 720px) {
+  textarea {
+    min-height: 88px;
+  }
+
+  button,
+  [role='button'] {
+    min-height: 48px;
+  }
+}
+```
+
+建议优先调整 CSS 变量、字体比例、间距和触控尺寸，不要依赖构建后生成的类名。写错样式不会影响 Host 网关；删除 `mobile.css` 后刷新即可恢复插件默认样式。
+
+## 为什么符合 DSH 的插件理念
+
+DSH Mobile 通过一个标准 bundle 同时贡献两张 face：Host face 提供局域网网关和本地控制接口，Client face 提供移动端样式与左下角控制卡。它只注入原生 `webServer` 服务，通过 `dsh plugin add/remove` 安装和卸载，不修改 `deepseek-harness` 文件。
+
+```mermaid
+flowchart LR
+  Phone["Android App 或手机浏览器"] -->|"HTTPS + 已配对会话"| Gateway["DSH Mobile 插件"]
+  Gateway -->|"仅回环代理"| DSH["原生 DSH Web UI"]
+```
+
+## 安全模型
+
+- 网关只接受设置向导选定的私有局域网 CIDR、精确 Host 和同源浏览器请求。
+- Android App 不跳过 TLS 校验；证书必须覆盖实际访问的局域网 IP。
+- 配对设备获得短期 HttpOnly Session，设备和会话都可在电脑端撤销。
+- 管理接口只允许从电脑回环地址访问，移动端无法打开、关闭网关或管理其他设备。
+- 外层网关在认证后才代理到原生 DSH 的回环端口，不会把 DSH 自身绑定到 `0.0.0.0`。
+
+不要在公共 Wi-Fi、端口转发、公网 IP 或不可信 VPN 中开放本插件。更多说明见 [SECURITY.md](SECURITY.md)。
+
+## 卸载
+
+普通卸载保留证书、已配对设备和自定义 CSS，方便以后重新安装：
+
+```powershell
+dsh plugin --profile web remove dsh-mobile
+```
+
+如果希望彻底删除本地数据，必须先运行清理，再卸载包：
+
+```powershell
+dsh plugin --profile web exec dsh-mobile purge --yes
+dsh plugin --profile web remove dsh-mobile
+```
+
+## Android App
+
+当前仅维护 Android 薄壳，源码位于 [`apps/mobile/android`](apps/mobile/android)。App 不复制 DSH 前端，只渲染插件提供的同一 HTTPS 页面；浏览器访问始终是一等能力。构建与安全边界见 [Android 文档](apps/mobile/README.zh-CN.md)。
+
+## 开发
+
+```powershell
+npm ci
+npm run verify
+```
+
+真实安装验证应从 `npm pack` 生成的 tarball 开始，并在隔离的原生 DSH Web profile 中完成安装、设置、启动、配对和卸载。
+
+Apache-2.0 licensed. See [LICENSE](LICENSE).

package/SECURITY.md

@@ -0,0 +1,29 @@
+# Security policy
+
+`dsh-mobile` exposes a control surface that can run tools on the host computer. Treat every paired device as security-sensitive.
+
+## Supported versions
+
+Only the newest prerelease receives security fixes while the project is in alpha. The README compatibility table identifies the exact DSH release tested with each plugin version.
+
+## Reporting a vulnerability
+
+Do not open a public issue for a suspected vulnerability. Use GitHub's private vulnerability-reporting form for `saya-ch/dsh-mobile`. Include the affected version, deployment topology, reproduction steps, and whether a device credential, session Cookie, or local access is required.
+
+The maintainer will acknowledge a complete report within seven days. Publication timing is coordinated with the reporter after a fix and a revocation or upgrade path are available.
+
+## Deployment requirements
+
+- Keep the ordinary DSH Web listener on loopback.
+- Expose only the plugin-owned HTTPS listener to the LAN.
+- Use a certificate trusted by every client platform; never instruct a WebView to ignore TLS errors.
+- Keep pairing closed except during a short local onboarding action.
+- Revoke a lost device immediately and rotate the device registry if credential theft is suspected.
+- Do not expose the gateway directly to the public Internet.
+- Treat every paired device as a fully trusted operator. Stock DSH methods reached through the authenticated loopback proxy may read configuration or run tools with the desktop user's authority.
+
+## Known alpha limitation
+
+The current DSH HTML boot process contains inline JavaScript and applies some styles dynamically. To keep the stock Web UI runnable, the gateway's Content Security Policy currently includes `script-src 'self' 'unsafe-inline'` and `style-src 'self' 'unsafe-inline'`. The remaining directives still restrict origins, connections, frames, objects, workers, images, and form targets, but this policy does not eliminate script-injection risk. Removing these allowances requires upstream DSH support for nonces, stable hashes, or external boot resources.
+
+This repository never accepts private keys, npm tokens, pairing values, device credentials, Cookies, or captured settings in issues, logs, fixtures, or example configuration.

package/cordis.patch.yml

@@ -0,0 +1,18 @@
+# Community bundle for the stock DSH Web profile. Installation contributes a
+# Host gateway and a browser Client face; it does not patch DSH source files.
+- insert:
+    - id: mobile-access
+      name: dsh-mobile
+      inject: [webServer]
+      config:
+        setupFile: !!js dshHomePath('mobile-access/setup.json')
+        stateFile: !!js dshHomePath('mobile-access/devices.json')
+        controlFile: !!js dshHomePath('mobile-access/control.json')
+        customCssFile: !!js dshHomePath('mobile-access/mobile.css')
+        initiallyEnabled: false
+        listenHost: 127.0.0.1
+        listenPort: 3443
+        upstreamOrigin: http://127.0.0.1:3080
+        allowedCidrs: [127.0.0.0/8]
+        tls:
+          mode: disabled