pi2dsh 0.2.0 → 0.3.0

package/README.md

@@ -45,7 +45,7 @@ Three delivery modes:
 Three hard rules keep it general:
 
 1. The core contains **no `if (packageName === …)`** branching.
-2. Every capability has a **public-API contract test** (`pnpm test`, 41 tests); "some plugin loads" is never the success criterion.
+2. Every capability has a **public-API contract test** (`pnpm test`, 49 tests); "some plugin loads" is never the success criterion.
 3. The top-50 corpus is verified **black-box only**: failures file public ABI gaps, and fixing one gap unlocks every package that hits it (e.g. one jiti subpath-alias fix unlocked 4 packages at once).
 
 ## Progress: Pi catalog top 50 by monthly downloads
@@ -54,30 +54,28 @@ Status as of 2026-08-14. Static analysis screens; the black-box run certifies. F
 
 | Tier | Count | Meaning |
 |---|---|---|
-| ✅ **Tested working** | **32 / 50** | Mounted in a real DSH runtime AND real execution verified: 29 returned success, 3 ran their business logic end-to-end and rejected the synthetic probe arguments (4 of the 32 additionally passed deep verification: real LSP subprocess, web search/fetch, PNG generation, official `dsh plugin` add/activate/remove) |
-| 🟡 **Mounts, not fully verified** | **7 / 50** | Loads and registers its tools/commands/skills in a real DSH runtime; full execution needs user credentials/services (3), is an event-hook package with no callable surface to probe (3), or hit a test-harness limitation (1: strict live-agent identity checks in userQuestions — the same path passes in the deep-verification layer) |
-| ❌ **Not yet supported** | **11 / 50** | Attributed below — all on the roadmap |
-| **Total mountable today** | **39 / 50** | |
+| ✅ **Tested working** | **41 / 50** | Mounted in a real DSH runtime AND real execution verified: 35 returned success, 6 ran their business logic end-to-end and rejected the synthetic probe arguments (4 additionally passed deep verification: real LSP subprocess, web search/fetch, PNG generation, official `dsh plugin` add/activate/remove; 2 of the 41 verified through host mode) |
+| 🟡 **Mounts, not fully verified** | **9 / 50** | Loads and registers its tools/commands/skills in a real DSH runtime; full execution needs user credentials/services (3), exposes no safely-probeable callable surface — event-hook packages or tools whose names indicate shared-state mutation, which the harness never invokes (4), was still executing when the 20s probe timeout hit — it dispatches a child `pi` process the fixture environment cannot serve (1), or hit a test-harness limitation (1: strict live-agent identity checks in userQuestions — the same path passes in the deep-verification layer) |
+| ❌ **Not yet supported** | **0 / 50** | The last four Pi-internal-runtime packages are bridged: vendored built-in tool constructors, provider factories, a real-semantics `ExtensionRunner` facade, and `createAgentSession` driving genuine DSH child agents |
+| **Total mountable today** | **50 / 50** | 48 through convert/host bundles directly; 2 snapshot-limited packages through host mode ([evidence](community/host-mode-results.json)) |
 
 Additional verified layers: a **host bundle** mounting two unmodified packages passed the official plugin-manager flow end-to-end; a **real model run** (`deepseek-v4-flash`) called a migrated Pi tool with the durable session log asserted and zero credential persistence ([evidence](community/live-deepseek-results.json)).
 
-### The 11 not yet supported, attributed
+### How the last four internal-runtime packages were bridged
 
-*Pi-internal runtime users (4) — need bespoke adapters, next on the roadmap:*
-`@tintinweb/pi-subagents` (calls `createAgentSession`/`createCodingTools` at load), `pi-landstrip` (calls `createBashToolDefinition`, Pi's built-in tool constructors), `pi-provider-litellm` (needs Pi's provider SDK factories; in DSH, model routing belongs to native llm adapters), `pi-fabric` (uses `wrapRegisteredTool` + references build-time-generated worker assets missing from its published tarball).
+Each landed as a reusable public-surface bridge, not a package patch: `pi-landstrip` and `pi-fabric` run on Pi's built-in tool constructors (bash/read/edit/write/grep/find/ls) vendored byte-identical with their pure-logic closure; `pi-provider-litellm` runs on the vendored pi-ai `createProvider` factory (model transports stay native to DSH llm); `pi-fabric` additionally hooks a real-semantics `ExtensionRunner` facade — patching `prototype.getAllRegisteredTools` genuinely filters the tool catalog, as under Pi; `@tintinweb/pi-subagents` runs on `createAgentSession` bridged to genuine DSH child agents through `ctx.agents` — the bridge owns no model loop, so compositions without one fail explicitly instead of simulating a subagent.
 
-*Package defects visible under any host (5) — will be reported upstream:*
-`pi-lens` (resource manifest escapes the package root), `pi-hermes-memory` + `@mjasnikovs/pi-task` (Bun-only `bun:sqlite`), `pi-harness-runtime` (imports playwright without declaring it), `mitsupi` (imports googleapis/ws without declaring them).
+### Correction: the "5 package defects" earlier versions reported
 
-*Convert-snapshot limitation (2) — host mode already covers them:*
-`pi-hashline-edit-pro`, `pi-interview` (read package files at runtime that static closure analysis cannot prove; the host bundle keeps the whole package directory).
+An earlier revision of this page (and our launch posts) attributed 5 blocked packages to upstream package defects. On re-verification **all five were faults in this project's own static screening, not in the packages** — high-download packages deserved that skepticism. Concretely: `bun:sqlite` is a host builtin of Pi's Bun-compiled distribution, and both `pi-hermes-memory` and `@mjasnikovs/pi-task` gate it behind runtime detection with proper Node fallbacks (better-sqlite3 / node:sqlite); `pi-harness-runtime`'s playwright and `mitsupi`'s googleapis/ws sit only on lazily-evaluated feature paths that never run at extension load; `pi-lens`'s out-of-tree skills path is skipped by Pi's own loader, and its bundler-stale worker URLs behave identically under Pi. The screener now models load-time vs lazy reachability, treats `bun:*` like `node:*`, and preserves published file layout — after which **all five mount, four grade tested-working, and no upstream issue was warranted**. The screening rules that produced the misjudgment are contract-tested against regressions.
 
-### Roadmap: all 50
+### Roadmap
 
-1. Lift the 7 "mounts, not fully verified" to tested-working (credentialed fixtures, per-package probe arguments).
-2. Bridge Pi's internal `AgentSession`/tool-constructor surfaces onto DSH natives to unlock the 4 internal-runtime packages.
-3. File upstream issues for the 5 package defects; adopt fixes as they land.
-4. Route the 2 snapshot-limited packages through host mode by default.
+1. Lift the 9 "mounts, not fully verified" to tested-working (credentialed fixtures, per-package probe arguments, a live-agent probe path for userQuestions).
+2. ✅ Done: interactive OAuth host seam — Pi provider `oauth.login/refreshToken/getApiKey` flows run on DSH-native interaction, credentials persist with Pi's `auth.json` semantics with double-checked-lock refresh, and the four official Pi flows ship built in; verified end-to-end against a real ChatGPT Pro account (see "Interactive OAuth" above).
+3. ✅ Done: all four Pi-internal-runtime packages bridged (see above) — every top-50 package mounts.
+4. ✅ Done: the 2 snapshot-limited packages verified through host mode ([evidence](community/host-mode-results.json)).
+5. ✅ Done: re-verified the 5 packages we had wrongly reported as defective; corrected the screener and this page (see above).
 
 ## Quick start
 
@@ -94,6 +92,18 @@ node dist/cli.mjs mcp-config                        # Pi mcpServers → DSH patc
 dsh plugin --profile headless add file:$PWD/pi-host
 ```
 
+## Interactive OAuth: sign in with your subscription
+
+DSH ships static HTTP headers only; pi2dsh adds the interactive OAuth layer from the Pi ecosystem. Any Pi provider package that registers an `oauth` block gets a working `/login <provider>` command on DSH, driven by the package's own protocol code. Pi's four official flows ship built in (vendored byte-identical): **OpenAI Codex (ChatGPT Plus/Pro)**, **Anthropic**, **GitHub Copilot**, **Kimi Code**.
+
+```sh
+# inside a DSH session with a pi2dsh host bundle mounted
+/login openai-codex     # prints the authorization URL, spins up the localhost callback
+# → approve in your browser; the credential lands in auth.json (0600)
+```
+
+What you get, end to end: PKCE + `localhost:1455` callback (device-code fallback for headless boxes), credentials persisted in Pi's `auth.json` format — so packages like `@narumitw/pi-accounts` manage the same file they already know — automatic refresh with Pi's double-checked-lock rotation (5-minute expiry window, refreshed token persisted before release), and `getProviderAuth`/`getApiKeyForProvider` on the extension registry returning live keys. Verified against a real ChatGPT Pro account: browser authorization → callback → token exchange → store → refreshable key (`scripts/verify-oauth-e2e.mjs` reproduces it; on networks that need a proxy, the script honors `HTTPS_PROXY`).
+
 ## Compatibility boundaries (explicit, never silent)
 
 | Area | Mapping |
@@ -101,7 +111,7 @@ dsh plugin --profile headless add file:$PWD/pi-host
 | Tools | Native DSH tools; Pi's in-place `tool_call` argument mutation works for Pi-owned tools (DSH-native tools reject it — DSH logs arguments before policy) |
 | Sessions | Messages project from DSH's durable log; Pi custom entries/labels/names persist in a pi2dsh sidecar (DSH has no out-of-repo plugin-event channel yet) |
 | Pi TUI | Pure logic vendored byte-identical; components construct headlessly; `ui.custom` resolves `undefined` exactly like Pi's own rpc mode |
-| Providers/OAuth | Declarations recorded; transports and credentials stay native to DSH `llm`/`credentials` |
+| Providers/OAuth | Interactive OAuth is live: `/login <provider>` runs the package's own flow, credentials persist in Pi's `auth.json` with automatic refresh; model transports stay native to DSH `llm` |
 | Session tree writes | `fork`/`navigateTree`/`switchSession` fail explicitly (DSH lists pi-style entry trees as deferred) |
 | Terminal decoration | footer/statusline/shortcuts register but never fire — matching Pi's own non-TUI modes |
 
@@ -110,7 +120,7 @@ Full machine-readable matrix: `pi2dsh matrix --json`. Capability-by-capability a
 ## Development and verification
 
 ```sh
-pnpm verify                                   # typecheck + 41 contract tests + packaging
+pnpm verify                                   # typecheck + 49 contract tests + packaging
 pnpm audit:community                          # static screening, top 50
 node scripts/blackbox-community.mjs community/blackbox-results.json --exercise
 pnpm test:community                           # deep runtime + official manager + host e2e

package/README.zh.md

@@ -45,7 +45,7 @@ DeepSeek Harness 原生服务（Cordis 组合）
 保持通用性的三条硬规则：
 
 1. 核心**没有任何 `if (packageName === …)`** 包名分支。
-2. 每项能力有**公共 API 契约测试**（`pnpm test`，41 个）；"某个插件能加载"从不作为成功标准。
+2. 每项能力有**公共 API 契约测试**（`pnpm test`，49 个）；"某个插件能加载"从不作为成功标准。
 3. 前 50 只做**黑盒验收**：失败产生公共 ABI 缺口工单，修一个缺口、同类包一起解锁（例：一次 jiti 子路径 alias 修复同时解锁 4 个包）。
 
 ## 进度：Pi 官方目录下载量前 50
@@ -54,30 +54,28 @@ DeepSeek Harness 原生服务（Cordis 组合）
 
 | 档位 | 数量 | 含义 |
 |---|---|---|
-| ✅ **已测可用** | **32 / 50** | 在真实 DSH runtime 挂载且**真实执行**验证：29 个成功返回，3 个业务逻辑端到端真跑（拒绝了合成探针参数）；其中 4 个另通过深度验证：真 LSP 子进程、真搜索/抓取、PNG 真落盘、官方 `dsh plugin` 安装/激活/卸载全流程 |
-| 🟡 **能接入、未全测** | **7 / 50** | 在真实 DSH runtime 加载并注册出工具/命令/skill；完整执行还需用户凭证或外部服务（3 个）、纯事件钩子包没有可探测调用面（3 个）、测试装置限制（1 个：userQuestions 严格校验 live agent 身份——同一链路在深度验证层已通过） |
-| ❌ **尚未接入** | **11 / 50** | 逐个归因见下——全部在路线图上 |
-| **今天即可挂载** | **39 / 50** | |
+| ✅ **已测可用** | **41 / 50** | 在真实 DSH runtime 挂载且**真实执行**验证：35 个成功返回，6 个业务逻辑端到端真跑（拒绝了合成探针参数）；其中 4 个另通过深度验证：真 LSP 子进程、真搜索/抓取、PNG 真落盘、官方 `dsh plugin` 安装/激活/卸载全流程；41 个中有 2 个经 host 模式验证 |
+| 🟡 **能接入、未全测** | **9 / 50** | 在真实 DSH runtime 加载并注册出工具/命令/skill；完整执行还需用户凭证或外部服务（3 个）、没有可安全探测的调用面——纯事件钩子包或工具名表明会改共享状态、探针从不调用（4 个）、探针 20 秒超时时仍在执行——它要派发一个子 `pi` 进程，探针环境无法提供（1 个）、测试装置限制（1 个：userQuestions 严格校验 live agent 身份——同一链路在深度验证层已通过） |
+| ❌ **尚未接入** | **0 / 50** | 最后 4 个 Pi 内部运行时包已全部桥接：内建工具构造器 vendored、provider 工厂、真语义 `ExtensionRunner` 门面、`createAgentSession` 驱动真实 DSH 子代理 |
+| **今天即可挂载** | **50 / 50** | 48 个经 convert/host bundle 直接挂载；2 个快照受限包经 host 模式（[证据](community/host-mode-results.json)） |
 
 另有两层验证：**host bundle** 合装两个原样 Pi 包走完官方插件管理器全流程；**真实模型**（deepseek-v4-flash）调用迁移后的 Pi 工具，durable 会话日志逐项断言、凭证零落盘（[证据](community/live-deepseek-results.json)）。
 
-### 尚未接入的 11 个，逐个归因
+### 最后 4 个内部运行时包是怎么桥接的
 
-**依赖 Pi 内部运行时（4 个）——需要专用适配，路线图下一步：**
-`@tintinweb/pi-subagents`（加载即调 `createAgentSession`/`createCodingTools`）、`pi-landstrip`（调 `createBashToolDefinition` 等 Pi 内建工具构造器）、`pi-provider-litellm`（要 Pi 的 provider SDK 工厂；DSH 里模型路由属于原生 llm adapter 职权）、`pi-fabric`（用 `wrapRegisteredTool` 内部 API + 引用发布包里根本不存在的构建期生成文件）。
+每个都落成了可复用的公共面桥，不是逐包补丁：`pi-landstrip` 与 `pi-fabric` 跑在 vendored 字节级的 Pi 内建工具构造器上（bash/read/edit/write/grep/find/ls 及其纯逻辑闭包）；`pi-provider-litellm` 跑在 vendored 的 pi-ai `createProvider` 工厂上（模型传输始终归 DSH llm 原生）；`pi-fabric` 另挂真语义 `ExtensionRunner` 门面——patch `prototype.getAllRegisteredTools` 能真实过滤工具目录，与 Pi 下行为一致；`@tintinweb/pi-subagents` 跑在 `createAgentSession` → 真实 DSH 子代理桥上（经 `ctx.agents` 走宿主 loop 工厂）——桥不自带模型循环，无 loop 的组合显式失败，绝不假装跑了子代理。
 
-**包自身缺陷，换任何宿主都一样（5 个）——将向上游提 issue：**
-`pi-lens`（资源清单越界逃出包根）、`pi-hermes-memory` 与 `@mjasnikovs/pi-task`（Bun 专属 `bun:sqlite`）、`pi-harness-runtime`（import 了未声明的 playwright）、`mitsupi`（import 了未声明的 googleapis/ws）。
+### 更正：早期版本报告的"5 个包缺陷"
 
-**Convert 快照模式限制（2 个）——host 模式已可覆盖：**
-`pi-hashline-edit-pro`、`pi-interview`（运行时读包内文件，静态闭包证不出来；host bundle 保留整包目录即可用）。
+本页早期版本（以及我们的发布帖）曾把 5 个被挡的包归因为"包自身缺陷"。复查后确认：**五个全部是本项目静态筛查自己的判定问题，不是包的问题**——大下载量的包本就值得这份怀疑。具体：`bun:sqlite` 是 Pi 官方 Bun 编译发行版的宿主内建，`pi-hermes-memory` 与 `@mjasnikovs/pi-task` 都做了运行时检测并带正规 Node 回退（better-sqlite3 / node:sqlite）；`pi-harness-runtime` 的 playwright 和 `mitsupi` 的 googleapis/ws 只出现在惰性求值的功能路径上，扩展加载期根本不会执行；`pi-lens` 的越界 skills 路径 Pi 自己的 loader 也是跳过处理，其打包器残留的 worker 路径在 Pi 下行为完全相同。筛查器现已区分加载期与惰性可达、把 `bun:*` 与 `node:*` 同等对待、并原样保留发布文件布局——修正后**五个包全部可挂载、四个达到已测可用，无需向任何上游提 issue**。产生误判的判定规则已补契约测试防止回归。
 
-### 路线图：50 个全部接入
+### 路线图
 
-1. 把 7 个"能接入、未全测"提升为"已测可用"（带凭证的 fixture、按包定制探针参数）。
-2. 做 Pi 内部 `AgentSession`/工具构造器面 → DSH 原生服务的桥，解锁 4 个内部运行时包。
-3. 给 5 个包缺陷向上游提 issue，跟进修复。
-4. 2 个快照受限包默认走 host 模式。
+1. 把 9 个"能接入、未全测"提升为"已测可用"（带凭证的 fixture、按包定制探针参数、给 userQuestions 补 live agent 探针链路）。
+2. ✅ 已完成：交互式 OAuth host seam——Pi provider 的 `oauth.login/refreshToken/getApiKey` 流跑在 DSH 原生交互上，凭证按 Pi `auth.json` 语义持久化并带双检锁刷新，四条官方流内建；已用真实 ChatGPT Pro 账号端到端验证（见上文"交互式 OAuth"）。
+3. ✅ 已完成：4 个 Pi 内部运行时包全部桥接（见上）——前 50 全部可挂载。
+4. ✅ 已完成：2 个快照受限包经 host 模式实测通过（[证据](community/host-mode-results.json)）。
+5. ✅ 已完成：复查曾被错误报告为"有缺陷"的 5 个包，修正筛查器与本页（见上）。
 
 ## 快速开始
 
@@ -94,6 +92,18 @@ node dist/cli.mjs mcp-config                        # Pi mcpServers → DSH patc
 dsh plugin --profile headless add file:$PWD/pi-host
 ```
 
+## 交互式 OAuth：用你的订阅账号登录
+
+DSH 原生只有静态 HTTP headers；pi2dsh 把 Pi 生态的交互式 OAuth 层带了过来。任何注册了 `oauth` 块的 Pi provider 包，在 DSH 上都直接获得可用的 `/login <provider>` 命令，登录流程由包自己的协议代码驱动。Pi 的四条官方流内建（vendored 字节级）：**OpenAI Codex（ChatGPT Plus/Pro）**、**Anthropic**、**GitHub Copilot**、**Kimi Code**。
+
+```sh
+# 在挂载了 pi2dsh host bundle 的 DSH 会话里
+/login openai-codex     # 打印授权 URL，同时拉起 localhost 回调服务
+# → 浏览器里点击授权；凭证落盘 auth.json（0600）
+```
+
+端到端你得到的是：PKCE + `localhost:1455` 回调（无头环境有 device-code 备选）、凭证按 Pi 的 `auth.json` 格式持久化——所以 `@narumitw/pi-accounts` 这类包管理的就是它们熟悉的同一份文件——自动刷新走 Pi 的双检锁轮换（5 分钟过期窗口，轮换后的 token 先落盘再放锁）、扩展注册表的 `getProviderAuth`/`getApiKeyForProvider` 返回真实可用的 key。已用真实 ChatGPT Pro 账号完整验证：浏览器授权 → 回调 → 换 token → 落盘 → 可刷新的 key（`scripts/verify-oauth-e2e.mjs` 可复现；需要代理的网络下脚本尊重 `HTTPS_PROXY`）。
+
 ## 兼容边界（显式声明，绝不静默）
 
 | 领域 | 映射 |
@@ -101,7 +111,7 @@ dsh plugin --profile headless add file:$PWD/pi-host
 | 工具 | 原生 DSH 工具；Pi 的 `tool_call` 原地改参对 Pi 自有工具生效（DSH 原生工具拒绝——DSH 有意先记日志后跑策略） |
 | 会话 | 消息从 DSH durable 日志投影；Pi 自定义 entry/label/name 持久化在 pi2dsh sidecar（DSH 目前没有第三方插件事件通道） |
 | Pi TUI | 纯逻辑 vendored 字节一致；组件类同签名 headless 构造；`ui.custom` 与 Pi 官方 rpc 模式一样返回 undefined |
-| Provider/OAuth | 声明被记录；传输与密钥始终由 DSH `llm`/`credentials` 原生持有 |
+| Provider/OAuth | 交互式 OAuth 已可用：`/login <provider>` 跑包自己的流程，凭证按 Pi `auth.json` 持久化并自动刷新；模型传输仍由 DSH `llm` 原生持有 |
 | 会话树写操作 | `fork`/`navigateTree`/`switchSession` 显式失败（DSH 官方将 pi 式 entry tree 列为 deferred） |
 | 终端装饰 | footer/statusline/快捷键注册成功但永不触发——与 Pi 自己的非 TUI 模式一致 |
 
@@ -110,7 +120,7 @@ dsh plugin --profile headless add file:$PWD/pi-host
 ## 开发与验证
 
 ```sh
-pnpm verify                                   # 类型检查 + 41 契约测试 + 打包检查
+pnpm verify                                   # 类型检查 + 49 契约测试 + 打包检查
 pnpm audit:community                          # 前 50 静态筛查
 node scripts/blackbox-community.mjs community/blackbox-results.json --exercise
 pnpm test:community                           # 深链路 + 官方插件管理器 + host e2e