@ban-sky/dsh-github 0.0.0-stage → 0.4.2

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 ban-sky
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,247 @@
-# Temporary Holding Version
+# dsh-github
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+[English](README.md) | [中文](README.zh.md)
+
+GitHub integration for the DeepSeek Harness Web UI. Sign in with GitHub's
+official OAuth **device flow**, then create, list, clone, pull, commit and push
+repositories from a single Settings page — or work on the current session folder
+directly from a button above the composer. An optional agent tool exposes the
+same operations to the model.
+
+Security comes first: the access token lives only in the local DSH credential
+store and is never written to the settings file, a git remote, git config, a
+command line, a log line or a Tool result.
+
+## Features
+
+- **Official sign-in** — GitHub OAuth device flow (`https://github.com/login/device`).
+  No password is ever handled by the plugin.
+- **Repositories** — list the account's repositories (owner, collaborator and
+  organization member), create a new repository (public/private, optional
+  README), clone any `owner/name` into the configured clone root.
+- **Local checkouts** — inspect branch, tracking state, ahead/behind and working
+  tree changes; `git pull --ff-only`; commit selected paths (or everything) and
+  push.
+- **Session folder actions** — the GitHub button above the composer clones into,
+  publishes, pulls, updates (fetch) and pushes the current session working
+  directory.
+- **Agent tool** (`github`, off by default) — the same operations as a Tool, so
+  the model can act on GitHub when the user enables it.
+- **Bilingual UI** — Chinese and English, following the Harness locale.
+
+## Requirements
+
+- Node.js 20+ (the Harness already provides this).
+- `git` on `PATH` (HTTPS remotes only).
+- A GitHub **OAuth App** with the *device flow* enabled — one minute of setup,
+  see below. (A device-flow-capable OAuth App client ID is public information;
+  it is not a secret.)
+- Until an OAuth App is configured the plugin still opens; it explains what is
+  missing instead of failing silently.
+
+## Install
+
+**From npm:**
+
+Use the Harness `plugin_manager` tool with `install_bundle` and the exact version
+`@ban-sky/dsh-github@0.4.2` as the target. The name carries a scope because
+`dsh-github` is taken on npm; the Release packages contain the same code.
+
+**From a release (recommended):**
+
+Every release ships two packages; pick the one for your host. Both unpack to
+`package/`:
+
+| Package | For |
+| --- | --- |
+| `dsh-github-<version>.tgz` | DSH Web / desktop: the Web UI only |
+| `dsh-github-<version>-dsh-go.tgz` | the DSH GO phone app: Web UI plus the native panel and composer entries |
+
+Open the [Releases](https://github.com/ban-sky/dsh-github/releases) page in a
+browser where you are signed in, or use the GitHub CLI:
+
+```bash
+gh release download v0.4.2 -R ban-sky/dsh-github   # needs gh auth login first
+sha256sum -c SHA256SUMS.txt
+tar -xzf dsh-github-0.4.2.tgz                     # web
+tar -xzf dsh-github-0.4.2-dsh-go.tgz              # phone
+```
+
+> The plain `releases/download/...` URL of a **private** repository only accepts
+> a browser session; an API token gets a 404 there. For scripts use
+> `gh release download`, or call
+> `GET /repos/ban-sky/dsh-github/releases/assets/<id>` with
+> `Accept: application/octet-stream`.
+
+Then install `package/` with the Harness `plugin_manager` tool
+(`install_bundle target:/path/to/package`). On a phone you can also run
+`dsh plugin --profile web add /path/to/package`.
+
+**From a source checkout:** install this directory as a bundle (Settings →
+Plugins → install from directory, or the Harness `plugin_manager` tool with
+`install_bundle`). The bundle mounts:
+
+- Host: the `/api/github` authenticated route, the `github` authorization flow,
+  and (when enabled) the `github` tool.
+- Client: one `Settings → GitHub` page.
+
+## DSH GO
+
+The plugin also speaks the DSH GO surface: `package.json.dshGo` (protocol v1)
+declares the native panel and the composer entries (`minApp` 1.0.13), and the
+`-dsh-go.tgz` package ships `lib/dsh-go.js`. The npm package carries the Web UI
+and that surface together, so `@ban-sky/dsh-github` fits either host.
+
+This plugin is not submitted to any plugin market. npm and the GitHub Release are
+the only distribution channels.
+
+## Setup: create the OAuth App
+
+1. GitHub → **Settings → Developer settings → OAuth Apps → New OAuth App**.
+2. Application name: anything, e.g. `DSH`; Homepage URL: anything you control
+   (`https://github.com/` is fine).
+3. **Enable "Device flow"** on the app page. This is required: the plugin uses
+   the device authorization grant, not a redirect callback.
+4. Copy the **Client ID** (`Iv1.…` or `Ov23…`) into **Settings → GitHub →
+   Client ID** and save.
+
+## Sign in
+
+1. Settings → GitHub → **Sign in with GitHub**.
+2. A one-time code appears. Open <https://github.com/login/device> (the plugin
+   only ever links to that exact host) and enter the code.
+3. Approve the request. The page updates as soon as GitHub confirms, and shows
+   the signed-in account.
+
+The requested scopes are `repo` (read/write access to repositories, including
+private ones) and `workflow` (lets a push create or update files under
+`.github/workflows`). GitHub shows both on the approval screen.
+
+If you signed in with an older release, the stored grant only has `repo`, so
+GitHub refuses pushes that touch workflow files ("refusing to allow an OAuth App
+to create or update workflow ... without `workflow` scope"). Settings → GitHub
+then shows a warning with a **Re-authorize** button; one more device-flow
+approval adds the scope, and the account, settings and local repositories are
+left untouched.
+
+Sign out deletes the stored grant from the credential store immediately; the
+token is also invalidated locally for every in-flight operation.
+
+## Session folder actions
+
+The composer button sends only the **sessionId** to the Host. The Host resolves
+the session's committed working directory through the agents and
+workingDirectory services, so the Client can never name an arbitrary path.
+
+| Action | Behaviour |
+| --- | --- |
+| Clone | Clones `owner/name` into `<session folder>/<name>`; refuses existing, non-empty or symlinked targets. |
+| Create and push | Creates the repository in your account (private by default), runs `git init -b main` in the session folder, adds `origin`, commits and pushes. Only runs when the folder itself is the repository root; refuses when it already contains a repository or lives inside another one. |
+| Pull | `git pull --ff-only` on the session repository. |
+| Update | `git fetch --prune`, refreshing ahead/behind without touching the working tree. |
+| Commit | Commits every change (or selected files), optionally followed by a push. |
+
+When the session folder is not itself a repository, the plugin uses the **single**
+immediate child repository (the one just cloned) for later actions. With more
+than one child repository it refuses to guess.
+
+The button adapts to the viewport: on desktop it shows the “GitHub” label, and on
+the phone web UI (viewport ≤ 640px) it collapses to a 26px branch icon so a narrow
+composer can never squeeze the label into a vertical column. The icon button keeps
+its `aria-label`, so screen readers and tooltips still name it.
+
+## DSH GO (the phone app)
+
+DSH GO draws its own Flutter UI, so it cannot render the Web settings page. On a
+host that provides the `dshGo` service the plugin registers a native surface that
+shares this plugin's one service instance (one token, one settings file, one
+sign-in state machine):
+
+- **GitHub panel**: account state, device-code sign-in (copy the code, open the
+  authorization page, cancel, sign out), the Agent-tool switch, and
+  refresh/fetch/pull/push for the current session folder. Reachable from the add
+  sheet, the session details "Plugins" tab, or "All features".
+- **Composer entries**: native form inputs are not available everywhere, so
+  text-driven work uses the message box: paste the Client ID and tap "Save ID",
+  type a commit message and tap "Commit", type `owner/name` and tap "Clone".
+- An app that does not advertise the `form` / `textField` components gets the
+  panel without input fields, only those entries and their instructions, instead
+  of a form nobody can type into.
+- Remove any older standalone adaptation package on the same host first, so two
+  GitHub panels do not compete.
+
+Hosts without the `dshGo` service are unaffected: none of this code runs there.
+
+## Settings
+
+| Setting | Meaning |
+| --- | --- |
+| **Client ID** | Public Client ID of your OAuth App (requires device flow). |
+| **Clone root** | Directory that clones must stay inside. Clones are placed at `<root>/<owner>/<name>`; paths that escape the root (including through symlinks) are rejected. Defaults to `~/github`. |
+| **Agent tool** | Registers the `github` tool for the model. Takes effect on the next plugin mount (restart or re-save the plugin), as the page indicates. |
+
+The settings file is `$DSH_HOME/dsh-github.json` (created with mode `0600`),
+and it never contains the token.
+
+## Agent tool
+
+`github` accepts `action`:
+
+| Action | Arguments | Result |
+| --- | --- | --- |
+| `status` | `path` | Sign-in state, settings and local checkouts |
+| `list_repos` | — | Repositories of the signed-in account |
+| `create_repo` | `name`, `description?`, `private?`, `autoInit?` | New repository |
+| `clone` | `fullName` | Cloned checkout path + status |
+| `pull` | `path` | Fast-forward pull result |
+| `commit` | `path`, `message`, `files?` | Commit result, optionally appended to the next push |
+| `push` | `path` | Push result (sets upstream on first push) |
+
+Failures come back as `{ ok: false, code, message }` with the same redaction as
+the UI.
+
+## Security model
+
+- Device flow only: the token is obtained from GitHub's token endpoint over
+  TLS and stored with `ctx.credentials.modifyRecord` as a `grant` record under
+  the key `dsh-github/token` (in `$DSH_HOME/.credentials.yaml`, mode `0600`).
+- The token is read per operation; it is never cached in the settings file, the
+  UI payload, or the Tool description.
+- Git never sees the token in `argv`, in a remote URL, or in git config. It is
+  passed only through the child process environment and answered by a one-shot
+  inline credential helper (`-c credential.helper=!…`); every configured
+  credential helper is cleared first and `GIT_TERMINAL_PROMPT=0` prevents any
+  interactive prompt or implicit credential persistence.
+- Only `https://github.com/<owner>/<name>` remotes are used or accepted;
+  `http`, SSH, other hosts and URLs with embedded credentials are rejected.
+  Pull/push refuse to run on a checkout whose `origin` is not such a URL.
+- Clone and commit paths are validated and contained: no `..`, no absolute
+  paths, no symlink escapes, no option-looking pathspecs.
+- Every error message and Tool result is redacted (known tokens, `ghp_…`/
+  `github_pat_…` shapes and `user:password@` URL parts).
+- The HTTP route is an authenticated Harness fetch endpoint (`POST
+  /api/github`); it accepts JSON only, caps the body at 1 MiB, and returns
+  business errors without leaking secrets.
+
+## Limits
+
+- One GitHub account per Harness profile.
+- Git operations only (list/create/clone/pull/commit/push); no pull requests,
+  issues, releases or merges.
+- No automatic credential refresh: when GitHub revokes or expires the grant,
+  the page asks you to sign in again.
+
+## Layout
+
+```
+index.js            Host entry (route, authorization flow, optional tool)
+client.js           Web UI: Settings → GitHub
+lib/github-api.js   Device flow + REST calls (token only in an auth header)
+lib/git.js          git invocations, remote/URL and path containment checks
+lib/service.js      State machine, dispatch, redaction boundary
+lib/http.js         POST /api/github handler
+lib/tools.js        `github` agent tool
+lib/config.js       Non-secret settings ($DSH_HOME/dsh-github.json)
+lib/validate.js     Owner/repo/path/message validation
+lib/errors.js       Error codes + secret redaction
+```

package/README.zh.md

@@ -0,0 +1,210 @@
+# dsh-github
+
+[English](README.md) | [中文](README.zh.md)
+
+DeepSeek Harness Web UI 的 GitHub 插件。用 GitHub 官方 OAuth **设备码流程**登录，
+然后在设置页里创建、列出、克隆、拉取、提交、推送仓库，或在任意会话的输入框
+下方直接操作该会话目录里的仓库；可选地把同样的能力注册成 agent 工具。
+
+安全优先：访问令牌只存在本机 DSH 凭据库中，绝不写进设置文件、git remote、
+git config、命令行参数、日志或 Tool 返回值。
+
+## 功能
+
+- **官方登录** —— GitHub OAuth 设备码流程（`https://github.com/login/device`），
+  插件不接触密码。
+- **仓库管理** —— 列出账号可访问的仓库（自己的、协作者、组织成员），创建新仓库
+  （公开/私有，可选初始化 README），把 `owner/name` 克隆到配置的克隆根目录。
+- **本地检出** —— 查看分支、上游跟踪、ahead/behind、工作区改动；`git pull
+  --ff-only`；提交指定路径（或全部改动）并推送。
+- **会话目录操作** —— 每个会话的输入框旁有 GitHub 按钮：在会话工作目录里克隆仓库、
+  新建仓库并推送（发布当前目录）、拉取、更新（fetch）和提交/推送。
+- **Agent 工具**（`github`，默认关闭）—— 与设置页相同的操作，开启后模型可使用。
+- **中英双语界面**，跟随 Harness 的界面语言。
+
+## 前置条件
+
+- Node.js 20+（Harness 已提供）。
+- `PATH` 中有 `git`（仅 HTTPS remote）。
+- 一个启用了 **Device flow** 的 GitHub **OAuth App**：一分钟配置，见下。
+  （Client ID 是公开信息，不是密钥。）
+- 未配置 OAuth App 时插件照常打开，会提示缺少什么，而不是静默失败。
+
+## 安装
+
+**从 npm 安装**：
+
+在 Harness 里用 `plugin_manager` 的 `install_bundle`，target 写精确版本
+`@ban-sky/dsh-github@0.4.2`。包名带 scope 是因为 `dsh-github` 在 npm 上已被他人
+占用；Release 里的安装包内容相同。
+
+**从 Release 下载安装包**（推荐）：
+
+每次发布出两个包，按宿主挑一个，都解出 `package/`：
+
+| 安装包 | 给谁用 |
+| --- | --- |
+| `dsh-github-<版本>.tgz` | DSH 网页版 / 桌面端：只有 Web UI |
+| `dsh-github-<版本>-dsh-go.tgz` | DSH GO 手机 App：Web UI + 原生面板和输入框入口 |
+
+在浏览器里登录 GitHub 后打开
+[Releases](https://github.com/ban-sky/dsh-github/releases) 下载，或者用 GitHub CLI：
+
+```bash
+gh release download v0.4.2 -R ban-sky/dsh-github   # 需要先 gh auth login
+sha256sum -c SHA256SUMS.txt
+tar -xzf dsh-github-0.4.2.tgz                     # 网页版
+tar -xzf dsh-github-0.4.2-dsh-go.tgz              # 手机用这个
+```
+
+> 私有仓库的 `releases/download/...` 直链只认浏览器登录态，API 令牌访问会
+> 404；脚本里请用 `gh release download`，或调
+> `GET /repos/ban-sky/dsh-github/releases/assets/<id>` 并带
+> `Accept: application/octet-stream`。
+
+然后在 Harness 里用 `plugin_manager` 的 `install_bundle` 指向解出的
+`package/` 目录即可；DSH GO 也可以直接 `dsh plugin --profile web add /path/to/package`。
+
+**从源码目录安装**：把本仓库目录作为 bundle 安装（设置 → 插件 → 从目录安装，
+或 `plugin_manager` 工具的 `install_bundle`）。安装后：
+
+- Host 端：`/api/github` 认证路由、`github` 授权流程，以及（开启后）`github` 工具。
+- Client 端：一个 `设置 → GitHub` 页面。
+
+## DSH GO
+
+插件同时提供 DSH GO 原生界面：`package.json` 的 `dshGo` 协议 v1 声明原生面板与
+输入框入口（`minApp` 1.0.13），`-dsh-go.tgz` 里带 `lib/dsh-go.js`。npm 上的包同时
+包含 Web UI 与这套界面，因此 `@ban-sky/dsh-github` 对两种宿主都适用。
+
+本插件不提交任何插件市场，分发渠道只有 npm 与 GitHub Release。
+
+## 配置：创建 OAuth App
+
+1. GitHub → **Settings → Developer settings → OAuth Apps → New OAuth App**。
+2. Application name 任意，如 `DSH`；Homepage URL 填你自己的地址
+   （`https://github.com/` 也可以）。
+3. 在应用页面打开 **"Device flow"**。插件用的是设备授权，不依赖回调地址。
+4. 复制 **Client ID**（`Iv1.…` 或 `Ov23…`）填入 **设置 → GitHub → Client ID** 并保存。
+
+## 登录
+
+1. 设置 → GitHub → **使用 GitHub 登录**。
+2. 页面显示一次性设备码。打开 <https://github.com/login/device> 输入该码
+   （插件只会把这一精确地址渲染成链接）。
+3. 在 GitHub 上批准。页面会自动刷新并显示已登录账号。
+
+申请的 scope 是 `repo`（含私有仓库的读写权限）和 `workflow`（允许推送创建或修改
+`.github/workflows` 下的文件）。GitHub 的批准页会显示这两个 scope。
+
+如果你是用旧版本登录的，已存授权只有 `repo`，GitHub 会拒绝任何涉及工作流文件的推送
+（报 "refusing to allow an OAuth App to create or update workflow ... without
+`workflow` scope"）。此时设置页会显示提示和 **重新授权** 按钮：再走一次设备码授权即可
+补上 scope，账号、设置文件和本地仓库都不受影响。
+
+退出登录会立即从凭据库删除授权记录，并让正在进行的操作失效。
+
+## 会话目录操作
+
+会话输入框下方的 GitHub 按钮只把 **sessionId** 发给 Host；Host 通过 agents 与
+workingDirectory 服务自行解析该会话已提交的工作目录，客户端无法指定任意路径。
+
+| 操作 | 说明 |
+| --- | --- |
+| 克隆 | 把 `owner/name` 克隆到 `<会话目录>/<name>`；目标已存在、非空、符号链接逃逸都会拒绝。 |
+| 创建并推送 | 在账号下创建仓库（默认私有），在会话目录 `git init -b main`、添加 `origin`、提交并推送。仅当该目录本身是仓库根目录时执行；目录内已有仓库或位于别的仓库中会拒绝。 |
+| 拉取 | 对会话目录里的仓库执行 `git pull --ff-only`。 |
+| 更新 | `git fetch --prune`，刷新 ahead/behind，不改变工作区。 |
+| 提交 | 提交全部改动（或指定文件），可选择随后推送。 |
+
+会话目录本身不是仓库时，插件会识别目录里**唯一**的直接子仓库（即刚克隆的那个），
+并在后续操作中沿用它；有多个子仓库时不作猜测。
+
+按钮会随屏幕宽度自适应：桌面端显示“GitHub”文字标签，**手机网页版（视口宽度
+≤ 640px）折叠成 26px 的分支图标按钮**，避免窄容器把文字挤成竖排；图标按钮仍带
+`aria-label`，读屏软件与悬停提示照常可用。
+
+## DSH GO 手机端
+
+DSH GO 的手机界面是 Flutter 原生的，画不了 Web UI。在提供 `dshGo` 服务的宿主上，
+插件会额外注册一套原生界面，和设置页共用同一个服务实例（同一份令牌、同一份配置、
+同一个登录状态机）：
+
+- **GitHub 面板**：加号面板里的 GitHub、对话详情「插件」页签、或「全部功能」都能
+  打开。里面有账号状态、设备码登录（复制设备码 / 打开授权页 / 取消 / 退出）、
+  Agent 工具开关，以及针对当前对话目录的刷新、更新、拉取、推送。
+- **输入框胶囊**：原生 App 不保证有能填的表单输入框，所以需要文字的操作走输入框
+  ——把 Client ID 粘进去点「存 ID」，把提交信息写进去点「提交」，把 `owner/name`
+  写进去点加号里的「克隆」。
+- App 没上报 `form` / `textField` 组件能力时，面板不画输入框，只保留上面这些入口
+  和说明，避免出现点不动的假表单。
+- 同一台机器上如果装过早期的独立适配包，先卸掉它再用本插件，免得出现两个 GitHub
+  面板抢同一个位置。
+
+网页版不受影响：没有 `dshGo` 服务的宿主上这些代码不会执行。
+
+## 设置项
+
+| 设置 | 含义 |
+| --- | --- |
+| **Client ID** | 你的 OAuth App 的公开 Client ID（需启用 Device flow）。 |
+| **克隆根目录** | 克隆必须落在此目录内，实际路径为 `<root>/<owner>/<name>`；越界路径（含符号链接逃逸）一律拒绝。默认 `~/github`。 |
+| **Agent 工具** | 为模型注册 `github` 工具。下次挂载插件后生效（重启或重新保存插件），页面会提示。 |
+
+设置文件为 `$DSH_HOME/dsh-github.json`（权限 `0600`），里面没有令牌。
+
+## Agent 工具
+
+`github` 的 `action`：
+
+| action | 参数 | 结果 |
+| --- | --- | --- |
+| `status` | `path` | 登录状态、设置与本地检出 |
+| `list_repos` | — | 已登录账号的仓库 |
+| `create_repo` | `name`、`description?`、`private?`、`autoInit?` | 新仓库 |
+| `clone` | `fullName` | 克隆路径与状态 |
+| `pull` | `path` | 快进拉取结果 |
+| `commit` | `path`、`message`、`files?` | 提交结果，可选择随后推送 |
+| `push` | `path` | 推送结果（首次推送会设置上游） |
+
+失败统一返回 `{ ok: false, code, message }`，与界面同样做脱敏。
+
+## 安全模型
+
+- 只用设备码流程：令牌经 TLS 从 GitHub 令牌端点取得，用
+  `ctx.credentials.modifyRecord` 以 `grant` 记录存到 `dsh-github/token`
+  （`$DSH_HOME/.credentials.yaml`，权限 `0600`）。
+- 每次操作现读令牌；设置文件、UI 返回值和 Tool 结果里都没有令牌。
+- git 的 `argv`、remote URL、git config 中都看不到令牌。令牌只通过子进程环境变量
+  传入，由一次性内联 credential helper（`-c credential.helper=!…`）应答；之前先清空
+  所有已配置的 helper，并设置 `GIT_TERMINAL_PROMPT=0`，杜绝交互提示与隐式保存凭据。
+- 只使用或接受 `https://github.com/<owner>/<name>` 形式的 remote；`http`、SSH、
+  其它域名以及内嵌凭据的 URL 一律拒绝；`origin` 不符合时拉取/推送直接拒绝。
+- 克隆与提交路径做包含性校验：禁止 `..`、绝对路径、符号链接逃逸和形似选项的
+  pathspec。
+- 所有错误信息和 Tool 结果都会脱敏（已知令牌、`ghp_…`/`github_pat_…` 形态、
+  `user:password@` 片段）。
+- HTTP 路由是 Harness 的认证 fetch 端点（`POST /api/github`），只接受 JSON，
+  请求体上限 1 MiB，业务错误不回传密钥。
+
+## 限制
+
+- 每个 Harness profile 只支持一个 GitHub 账号。
+- 只做 git 操作（列出/创建/克隆/拉取/提交/推送）；不含 PR、Issue、Release、合并。
+- 不自动刷新凭据：GitHub 撤销或过期后，页面会要求重新登录。
+
+## 目录结构
+
+```
+index.js            Host 入口（路由、授权流程、可选工具）
+client.js           Web UI：设置 → GitHub
+lib/github-api.js   设备码流程 + REST 调用（令牌只放在 auth 头）
+lib/git.js          git 调用、remote/URL 与路径包含性校验
+lib/service.js      状态机、dispatch、脱敏边界
+lib/http.js         POST /api/github 处理器
+lib/tools.js        `github` agent 工具
+lib/dsh-go.js       DSH GO 原生面板 + 输入框入口（共用同一服务实例）
+lib/config.js       非秘密设置（$DSH_HOME/dsh-github.json）
+lib/validate.js     owner/repo/路径/提交信息校验
+lib/errors.js       错误码 + 密钥脱敏
+```