npm - pi-dsh-mimic - Versions diffs - 0.1.1 → 0.1.2 - Mend

pi-dsh-mimic 0.1.1 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (10) hide show

package/README.md CHANGED Viewed

@@ -1,71 +1,49 @@
-[Repository index](../../README.en.md) · [简体中文](README.zh-CN.md) · [Experiments and design](docs/advanced.md) · [Project2 evidence ledger (Chinese canonical)](docs/project2-evidence.md)
+[Repository index](../../README.en.md) · [简体中文](README.zh-CN.md) ·
+[Experiments and design](docs/advanced.md) ·
+[Project2 evidence ledger](docs/project2-evidence.md)
 # pi-dsh-mimic
-`pi-dsh-mimic` reproduces the DeepSeek Harness Minimal environment for the
-first model request in [Pi](https://github.com/earendil-works/pi). DeepSeek V4
-Pro begins from a verified high-capability trajectory; after the first valid
-response, execution returns immediately to Pi with its complete tool catalog
-and the user's other plugins.
+`pi-dsh-mimic` changes only the first DeepSeek V4 Pro request in
+[Pi](https://github.com/earendil-works/pi). The real task begins with the DSH
+Minimal persona and its `bash` and `str_replace_editor` tools. After the first
+valid response, later requests return to Pi-native formatting and the complete
+tool catalog.
-One session gets both:
+It does not require the full DSH harness and adds no extra model round.
-- the V4 Pro engineering trajectory established by a DSH Minimal first request;
-- Pi's mature tools, session management, and plugin ecosystem.
+## How it works
-Users do not need to install or run the complete DSH harness, and the session
-does not remain restricted to Minimal's two tools.
+1. In a fresh target session, the original task becomes the Minimal request.
+2. The first successful assistant response or actual tool call ends bootstrap.
+3. Later requests keep the Minimal persona while Pi again owns payload encoding,
+   tool ordering, and plugin tools.
-## How it works
+Provider errors and aborted responses do not consume bootstrap. A small Pi
+custom entry persists the phase across resume. If the process crashes after a
+completed response but before the phase is recorded, durable assistant/tool
+history repairs the state on reload.
+## Experimental result
+On one frozen Project2 V4.1b long-horizon maintenance task, default Pi scored
+92. Four final runs of the same one-shot flow scored 98, 96, 96, and 98. This
+comparison supports the current first-request design; it does not establish a
+general result across projects, model revisions, or evaluations.
-For a fresh target session, the real task itself becomes the first model
-request:
-1. request #1 uses the Minimal persona and exposes only DSH-style `bash` and
-   `str_replace_editor`;
-2. after the first successful assistant response or durable tool call, request
-   #2 restores Pi's native provider payload and complete current tool catalog;
-3. the Minimal persona remains for the session, while Pi's larger generated
-   system prompt is not replayed as an extra user message.
-The extension adds no identity warm-up or model round, makes no hidden copy of
-the task, does not inject `We need`, and does not proxy the API.
-## Project2 results
-Project2 V4.1b is a personal, self-hosted long-horizon repository-maintenance
-evaluation. The model repairs a multi-module Python backend and ESP32-S3
-firmware project covering authentication and session privacy, database
-migrations, cross-module features, backward compatibility,
-Wi-Fi/MQTT/NVS/protocol and ESP-IDF contracts, and delivery evidence. It is not
-a general benchmark; these scores compare engineering completion on one frozen
-task.
-Default Pi scored 92. Four final runs of the same one-shot request flow scored
-**98, 96, 96, and 98**, all with F3 at 16/16:
-| Run | Provider | Score | Key dimensions |
-| --- | --- | ---: | --- |
-| Default Pi baseline | Official DeepSeek API | 92 | F3 11, F6 10, F8 6 |
-| Early Minimal-mimic prototype | Official DeepSeek API | **98** | F3 16, F6 10, F8 7 |
-| Same-flow replication | Official DeepSeek API | 96 | F3 16, F6 10, F8 5 |
-| First packaged implementation | Official DeepSeek API | 96 | F3 16, F6 8, F8 7 |
-| Current independent implementation | OpenCode Go | **98** | F3 16, F6 10, F8 7 |
-The results show that a DSH Minimal first request can establish a strong V4 Pro
-trajectory inside Pi and that restoring Pi's full tool catalog does not break
-it. See [Experiments and design](docs/advanced.md) for the rejected alternatives
-and the evidence behind each implementation choice. The
-[Project2 evidence ledger](docs/project2-evidence.md), maintained in Chinese,
-contains evaluator IDs and sources.
+See [Experiments and design](docs/advanced.md) for conditions, negative results,
+and implementation choices. The [Project2 evidence ledger](docs/project2-evidence.md)
+contains the complete runs and evaluator sources.
 ## Install and use
-Requirements: Node.js 22.19 or later, Pi 0.84.2 or later, and either official
-DeepSeek API or OpenCode Go configuration. Pi 0.84.2 includes both provider
-routes.
+Requirements: Node.js 22.19 or later, Pi 0.84.2 or later, and a provider
+configured in Pi whose model id contains `deepseek-v4-pro`. The official
+DeepSeek API and OpenCode Go are the repository-qualified routes. The extension
+also activates for third-party providers; compatibility, data handling, and
+billing then follow the provider selected by the user.
-Install from npm for the current user:
+Install for the current user:
 ```bash
 pi install npm:pi-dsh-mimic
@@ -85,53 +63,28 @@ pi -e ./packages/pi-dsh-mimic \
   --model deepseek-v4-pro
 ```
-For OpenCode Go, configure Pi's expected `OPENCODE_API_KEY` environment variable
-and select the `opencode-go` provider. The package is published to npm with the
-`pi-package` keyword required by the
-[Pi Package Catalog](https://pi.dev/packages).
+For OpenCode Go, set Pi's expected `OPENCODE_API_KEY` environment variable and
+select the `opencode-go` provider.
 Select V4 Pro before starting a new session. Switching to V4 Pro inside an
-existing conversation does not forge a new bootstrap.
+existing conversation does not create a synthetic bootstrap. The extension
+registers `str_replace_editor` in a target session; if that same session later
+switches to another model, the tool may remain in the current catalog. Start a
+new session when a clean non-target tool catalog matters.
-## Request lifecycle
+## Request changes
-| | Bootstrap request | Execution requests |
+| | First request | Later requests |
 | --- | --- | --- |
-| System persona | `You are a helpful software engineer assistant.` | unchanged |
-| User history | Original task, including Pi-native images | unchanged |
-| Provider-visible tools | `bash`, `str_replace_editor` | Pi's complete current catalog, including plugin tools |
-| Provider payload | DSH Minimal shape; Pi cache fields omitted | Pi-native encoding and ordering; cache follows provider configuration |
-The extension never calls `setActiveTools` and never overrides Pi's native
-`bash`, `read`, `edit`, or `write`. It registers one executable
-`str_replace_editor` only when a fresh target session arms. From request #2,
-tools contributed by other packages appear in the complete catalog.
-Provider errors and aborted responses do not consume the bootstrap. A small Pi
-custom entry persists the phase, and durable assistant/tool history repairs a
-crash-stale state on resume.
-## Offline verification
-TypeScript typechecking and all 13 automated tests pass. Twelve cover package
-behavior and its manifest; one verifies the session-statistics helper. Package
-behavior coverage includes:
-- original task, persona, field order, cache omission, and two-tool schemas in
-  request #1;
-- Pi-native payload, complete catalog, and plugin-tool restoration in request
-  #2;
-- images, API-error retry, text promotion, session resume, and crash-stale
-  recovery;
-- existing-conversation isolation, both providers, and non-target models;
-- editor create, view, replace, insert, and ambiguous-replacement rejection.
-OpenCode Go bash-first and editor-first offline loopbacks also pass through Pi's
-real package loader and provider path with `realModelCalls=0`. Request #2 carries
-a real tool result and restores `read/bash/edit/write/str_replace_editor`. After
-normalizing the user task, the new request #1 matches the historical 98-point
-capture in messages, key order, schemas, `strict:false`, and serialized
-structure.
+| Persona | `You are a helpful software engineer assistant.` | unchanged |
+| User history | Original task, including Pi images | unchanged |
+| Tools | `bash`, `str_replace_editor` | Pi's current full catalog, including plugin tools |
+| Payload | DSH Minimal shape | Pi-native encoding and ordering |
+`str_replace_editor` can view, create, and modify absolute paths with the Pi
+process's filesystem permissions. The task, context, and tool results are sent
+to the provider selected by the user. The extension does not read or store API
+keys. See [SECURITY.md](SECURITY.md) for the full boundary.
 ## Development
@@ -142,17 +95,7 @@ npm run check
 npm run pack:check
 ```
-## Security, cost, and sources
-This package runs with the Pi process's filesystem permissions;
-`str_replace_editor` can create and modify files. The task, context, and tool
-results are sent to the selected DeepSeek or OpenCode provider. The package
-does not read, store, log, or transmit API keys and adds no model round. See
-[SECURITY.md](SECURITY.md).
-The Minimal persona and two tool-protocol texts come from DeepSeek Harness's
+The Minimal persona and two tool protocols come from DeepSeek Harness's
 [public Minimal protocol](https://github.com/deepseek-ai/deepseek-harness). See
-[LICENSE](LICENSE) and [NOTICE](NOTICE). The current implementation is based on
-that public protocol, request captures made by this project, and the Project2
-experiments. It is not affiliated with or endorsed by Pi, DeepSeek, OpenCode,
-or OpenAI.
+[LICENSE](LICENSE) and [NOTICE](NOTICE). This project is not affiliated with or
+endorsed by Pi, DeepSeek, OpenCode, or OpenAI.

package/README.zh-CN.md CHANGED Viewed

@@ -1,60 +1,41 @@
-[仓库索引](../../README.md) · [English](README.md) · [实验与设计](docs/advanced.zh-CN.md) · [Project2 证据账本](docs/project2-evidence.md)
+[仓库索引](../../README.md) · [English](README.md) ·
+[实验与设计](docs/advanced.zh-CN.md) · [Project2 证据账本](docs/project2-evidence.md)
 # pi-dsh-mimic
-`pi-dsh-mimic` 在 [Pi](https://github.com/earendil-works/pi) 的第一次模型请求中复现
-DeepSeek Harness Minimal 环境，让 DeepSeek V4 Pro 从已验证的高能力轨迹起步；第一次
-有效响应后，它立即回到 Pi 原生执行，恢复完整工具目录和用户安装的其他插件。
+`pi-dsh-mimic` 只修改 DeepSeek V4 Pro 在 [Pi](https://github.com/earendil-works/pi)
+中的第一次模型请求。真实任务先进入 DSH Minimal 的 persona 与 `bash`、
+`str_replace_editor` 两个工具；第一次有效响应后，后续请求恢复 Pi 原生格式和完整工具
+目录。
-它把两件事放进同一个 session：
-- DSH Minimal 首请求带来的 V4 Pro 工程能力；
-- Pi 成熟的工具、session 管理和插件生态。
-用户无需安装或运行完整 DSH harness，也不必长期停留在两个工具的 Minimal 环境中。
+它不需要安装完整 DSH harness，也不会增加额外模型轮次。
 ## 工作方式
-新建目标 session 的真实任务直接成为第一次模型请求：
-1. 请求 #1 使用 Minimal persona，只暴露 DSH 风格的 `bash` 与
-   `str_replace_editor`；
-2. 第一个成功 assistant response 或 durable tool call 后，请求 #2 恢复 Pi 原生
-   provider payload 和当下完整工具目录；
-3. Minimal persona 在整个 session 保持，Pi 较长的自动 system prompt 不会作为额外
-   user message 重放。
+1. 新建目标 session 后，原始任务直接成为 Minimal 请求；
+2. 第一次成功的 assistant response 或实际 tool call 结束 bootstrap；
+3. 后续请求继续使用 Minimal persona，但 payload、工具排序和插件工具由 Pi 接管。
-扩展不增加身份 warm-up 或模型轮次，不复制原任务，不注入 `We need`，也不代理 API。
+Provider error 或 aborted response 不消耗 bootstrap。阶段会写入一个小型 Pi custom entry，
+因此 session resume 后仍能恢复；如果进程在响应完成后、阶段写入前崩溃，durable
+assistant/tool 历史会把状态修正到执行阶段。
-## Project2 结果
+## 实验结果
-Project2 V4.1b 是一个个人、自托管的长程代码维护评测。模型需要修复一个多模块 Python
-后端与 ESP32-S3 固件仓库，覆盖鉴权与 session 隐私、数据库迁移、跨模块功能、兼容性、
-Wi-Fi/MQTT/NVS/协议与 ESP-IDF 契约，以及交付说明。它不是通用 benchmark；这里的分数
-只用于比较同一冻结任务下的工程完成度。
+在一个冻结的 Project2 V4.1b 长程代码维护任务中，默认 Pi 得到 92；使用相同 one-shot
+流程的四次最终结果为 98、96、96、98。这个对照支持当前首请求设计，但不能直接外推到
+其他项目、模型版本或评测。
-默认 Pi 得到 92。相同 one-shot 请求流程的四次最终结果为 **98、96、96、98**，均保持
-F3 16/16：
-| 运行 | Provider | 分数 | 关键分项 |
-| --- | --- | ---: | --- |
-| 默认 Pi baseline | DeepSeek 官方 API | 92 | F3 11，F6 10，F8 6 |
-| 早期 Minimal 模拟原型 | DeepSeek 官方 API | **98** | F3 16，F6 10，F8 7 |
-| 同流程复现实验 | DeepSeek 官方 API | 96 | F3 16，F6 10，F8 5 |
-| 首次 package 化实现 | DeepSeek 官方 API | 96 | F3 16，F6 8，F8 7 |
-| 当前独立实现 | OpenCode Go | **98** | F3 16，F6 10，F8 7 |
-这些结果表明：DSH Minimal 首请求可以在 Pi 中稳定建立高能力轨迹，而恢复 Pi 完整工具
-目录不会破坏它。实验过程、被否决的设计和每项实现选择的依据见
-[实验与设计](docs/advanced.zh-CN.md)；完整 evaluator IDs 与来源见
-[Project2 证据账本](docs/project2-evidence.md)。
+实验条件、负结果和实现取舍见[实验与设计](docs/advanced.zh-CN.md)，完整运行与 evaluator
+来源见 [Project2 证据账本](docs/project2-evidence.md)。
 ## 安装和使用
-要求：Node.js 22.19 或更新版本、Pi 0.84.2 或更新版本，并已配置 DeepSeek 官方 API 或
-OpenCode Go。Pi 0.84.2 已内置两条 provider 路径。
+要求：Node.js 22.19 或更新版本、Pi 0.84.2 或更新版本，并已在 Pi 中配置模型标识包含
+`deepseek-v4-pro` 的 provider。DeepSeek 官方 API 与 OpenCode Go 是本仓库已验证的路径；
+第三方 provider 也会激活扩展，其兼容性、数据边界和计费由用户选择的 provider 决定。
-从 npm 安装到当前用户：
+安装到当前用户：
 ```bash
 pi install npm:pi-dsh-mimic
@@ -74,43 +55,25 @@ pi -e ./packages/pi-dsh-mimic \
   --model deepseek-v4-pro
 ```
-使用 OpenCode Go 时，把 key 配置在 Pi 期望的 `OPENCODE_API_KEY` 环境变量中，并把
-provider 改为 `opencode-go`。Package 已发布到 npm，并带有 Pi gallery 要求的
-`pi-package` keyword，可由 [Pi Package Catalog](https://pi.dev/packages) 索引。
+OpenCode Go 使用 Pi 预期的 `OPENCODE_API_KEY` 环境变量，并将 provider 设为
+`opencode-go`。
-先选择 V4 Pro，再新建 session。在已有对话中途切换到 V4 Pro 不会伪造新的 bootstrap。
+请先选择 V4 Pro，再新建 session。已有对话中途切换到 V4 Pro 不会补造 bootstrap。
+扩展在目标 session 中注册 `str_replace_editor`；如果在同一个 session 里再切换到其他
+模型，这个工具可能继续留在当前工具目录。需要干净的非目标模型环境时，新建 session。
-## 请求生命周期
+## 请求变化
-| | Bootstrap 请求 | 执行阶段请求 |
+| | 第一次请求 | 后续请求 |
 | --- | --- | --- |
-| System persona | `You are a helpful software engineer assistant.` | 保持不变 |
-| User 历史 | 原始任务，包括 Pi 原生图片 | 不变 |
-| Provider 可见工具 | `bash`、`str_replace_editor` | Pi 当下完整目录，包括其他插件工具 |
-| Provider payload | DSH Minimal 形状；移除 Pi cache 字段 | Pi 原生编码与排序；cache 随 provider 配置 |
-扩展不调用 `setActiveTools`，也不覆盖 Pi 原生 `bash`、`read`、`edit` 或 `write`。目标
-新 session 武装时才注册一个可执行 `str_replace_editor`；请求 #2 起，其他 package
-提供的工具会自然出现在完整目录中。
+| Persona | `You are a helpful software engineer assistant.` | 保持不变 |
+| User 历史 | 原始任务，包括 Pi 图片 | 保持不变 |
+| 工具 | `bash`、`str_replace_editor` | Pi 当前完整目录，包括其他插件工具 |
+| Payload | DSH Minimal 形状 | Pi 原生编码与排序 |
-Provider error 或 aborted response 不消耗 bootstrap。阶段通过小型 Pi custom entry
-持久化，恢复时也能根据 durable assistant/tool 历史修正 crash-stale 状态。
-## 离线验证
-TypeScript typecheck 已通过，13 项自动化测试全部通过。其中 12 项覆盖 package 行为与
-manifest，1 项验证 session 统计工具。Package 行为测试覆盖：
-- 首请求原任务、persona、字段顺序、cache 移除和两工具 schema；
-- 请求 #2 恢复 Pi 原生 payload、完整目录和其他插件工具；
-- 图片、API error 重试、文本回答晋升、session resume 和 crash-stale 恢复；
-- 已有对话隔离、DeepSeek/OpenCode 双 provider 与非目标模型隔离；
-- editor 的 create、view、replace、insert 和歧义替换拒绝。
-OpenCode Go bash-first 与 editor-first 离线回环还通过 Pi 的真实 package loader 和 provider
-路径验证了两个请求，`realModelCalls=0`。请求 #2 携带真实工具结果，并恢复
-`read/bash/edit/write/str_replace_editor`。归一 user task 后，新请求 #1 与历史 98 分
-capture 在消息、字段顺序、schema、`strict:false` 和序列化结构上逐项相等。
+`str_replace_editor` 可以查看、创建和修改绝对路径文件，并继承 Pi 进程的文件系统权限。
+任务、上下文和工具结果会发送给用户选择的 provider。扩展不读取或保存 API key；完整
+边界见 [SECURITY.md](SECURITY.md)。
 ## 开发
@@ -121,15 +84,7 @@ npm run check
 npm run pack:check
 ```
-## 安全、费用与来源
-本 package 以 Pi 进程的文件系统权限运行；`str_replace_editor` 可以创建和修改文件。
-任务、上下文和工具结果会发送给所选 DeepSeek 或 OpenCode provider。package 不读取、
-保存、记录或传输 API key，也不增加额外模型轮次。完整说明见
-[SECURITY.md](SECURITY.md)。
-Minimal persona 与两项工具协议文本来自
-[DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 的公开 Minimal 协议；
-对应许可声明见 [LICENSE](LICENSE) 和 [NOTICE](NOTICE)。当前实现依据该公开协议、本项目
-捕获的请求和 Project2 实验完成，与 Pi、DeepSeek、OpenCode 或 OpenAI 均无隶属或官方
-背书关系。
+Minimal persona 与两项工具协议来自 DeepSeek Harness 的
+[公开 Minimal 协议](https://github.com/deepseek-ai/deepseek-harness)，许可见
+[LICENSE](LICENSE) 和 [NOTICE](NOTICE)。本项目与 Pi、DeepSeek、OpenCode 或 OpenAI
+均无隶属或官方背书关系。

package/SECURITY.md CHANGED Viewed

@@ -4,8 +4,8 @@
 `pi-dsh-mimic` does not read, save, log, or transmit API keys. Provider
 credentials remain under Pi and the selected provider's configuration. Never
-put a DeepSeek or OpenCode key in a prompt, repository file, issue, screenshot,
-or captured request.
+put a provider credential in a prompt, repository file, issue, screenshot, or
+captured request.
 If a credential has been exposed, revoke or rotate it with the provider before
 continuing.
@@ -13,10 +13,13 @@ continuing.
 ## Provider data boundary
 For target sessions, the task, conversation messages, tool schemas, and later
-tool results are sent through either `deepseek/deepseek-v4-pro` or
-`opencode-go/deepseek-v4-pro`. The extension changes the first request's
-persona and tool surface, but it is not an API proxy and does not create a
-confidential channel.
+tool results are sent through the provider selected in Pi. A model id containing
+`deepseek-v4-pro` activates the extension regardless of provider name. The
+repository-qualified routes are `deepseek/deepseek-v4-pro` and
+`opencode-go/deepseek-v4-pro`; third-party provider compatibility and data
+handling remain the user's responsibility. The extension changes the first
+request's persona and tool surface, but it is not an API proxy and does not
+create a confidential channel.
 The package adds no model round. The user's ordinary first task is the
 bootstrap request and is billed normally by the selected provider.

package/docs/advanced.md CHANGED Viewed

@@ -117,7 +117,7 @@ establishes a DSH Minimal first request, while Pi remains the execution runtime.
 | Current behavior | Main evidence |
 | --- | --- |
-| Arm only fresh sessions on the target provider/model pairs | An existing conversation cannot reproduce a real bootstrap; isolation tests cover target and non-target models |
+| Arm only fresh sessions whose model id contains `deepseek-v4-pro` | Provider names do not gate activation; an existing conversation cannot reproduce a real bootstrap; isolation tests cover target and non-target models |
 | Put the original task in request #1 | Early prototype 98; Whoami 93 |
 | Use the Minimal persona and DSH schemas in request #1 | Pi-native `bash/read` 93; approximate Minimal 93 |
 | Return to Pi-native execution after the first valid response | One-shot 96–98; persistent DSH wire 94 |
@@ -143,10 +143,11 @@ without injecting them into the prompt.
 ## Implementation verification
-TypeScript typechecking and all 13 automated tests pass. Twelve cover both
-providers, images, error retry, text promotion, session resume, crash-stale
-recovery, existing-conversation isolation, and non-target model isolation; one
-verifies the session-statistics helper. Editor tests cover create, view, unique
+TypeScript typechecking and all 14 automated tests pass. Thirteen cover both
+qualified providers, namespaced model ids on third-party providers, images,
+error retry, text promotion, session resume, crash-stale recovery,
+existing-conversation isolation, and non-target model isolation; one verifies
+the session-statistics helper. Editor tests cover create, view, unique
 replacement, insertion, relative-path rejection, and ambiguous-replacement
 rejection.

package/docs/advanced.zh-CN.md CHANGED Viewed

@@ -99,7 +99,7 @@ provider payload 和 active catalog，其他 package 的工具会自然出现。
 | 当前行为 | 主要证据 |
 | --- | --- |
-| 只武装目标 provider/model 的新 session | 已有对话无法还原真实 bootstrap；隔离测试覆盖目标与非目标模型 |
+| 只武装模型标识包含 `deepseek-v4-pro` 的新 session | provider 名称不限制激活；已有对话无法还原真实 bootstrap；隔离测试覆盖目标与非目标模型 |
 | 原任务直接进入请求 #1 | 早期原型 98；Whoami 93 |
 | 请求 #1 使用 Minimal persona 与 DSH 两项 schema | Pi 原生 `bash/read` 93；近似 Minimal 93 |
 | 第一次有效响应后恢复 Pi 原生执行 | one-shot 96–98；持续 DSH wire 94 |
@@ -122,9 +122,9 @@ wire 调用 225 次工具只得到 94，早期原型调用 148 次得到 98；
 ## 实现验证
-TypeScript typecheck 已通过，13 项自动化测试全部通过：12 项覆盖两个 provider、图片、
-错误重试、文本晋升、session resume、crash-stale 恢复、已有对话隔离和非目标模型隔离；
-另 1 项验证 session 统计工具。
+TypeScript typecheck 已通过，14 项自动化测试全部通过：13 项覆盖两个已验证 provider、
+第三方 provider 的命名空间模型标识、图片、错误重试、文本晋升、session resume、
+crash-stale 恢复、已有对话隔离和非目标模型隔离；另 1 项验证 session 统计工具。
 Editor 测试覆盖 create、view、unique replace、insert、相对路径拒绝和歧义替换拒绝。
 OpenCode Go bash-first 与 editor-first 离线回环通过 Pi 的真实 package loader 和 provider

package/docs/project2-evidence.md CHANGED Viewed

@@ -219,9 +219,11 @@ evaluator。
 ## 当前决定
 - 产品名为 `pi-dsh-mimic`。`0.1.0` 是首次公开实现；`0.1.1` 只补充 Project2 语境和
-  已发布安装说明，运行时代码不变。
+  已发布安装说明，运行时代码不变；`0.1.2` 将激活条件改为模型标识包含
+  `deepseek-v4-pro`，不再按 provider 名称限制。
 - 默认流程固定为 task-bearing one-shot：请求 #1 模拟 DSH Minimal，请求 #2 恢复 Pi。
-- 同时支持 Pi 的 `deepseek` 与 `opencode-go` provider。
+- DeepSeek 官方 API 与 OpenCode Go 是本文已有运行和离线回环证据的 provider；第三方
+  provider 可以激活扩展，但不属于本文已经验证的实验范围。
 - Minimal persona 保持；完整 Pi system context 不重放。
 - Project2 同一请求流程已有四次 96–98，不继续重复付费运行。
 - 新任务、模型或服务版本变化、provider payload 实质变化，或新的完整任务结果可以重开

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "pi-dsh-mimic",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Unlock DeepSeek V4 Pro's DSH Minimal capability in Pi while keeping Pi's full plugin ecosystem",
   "type": "module",
   "main": "./src/index.ts",

package/src/constants.ts CHANGED Viewed

@@ -1,7 +1,5 @@
 export const TARGET_MODEL_ID = "deepseek-v4-pro";
-export const TARGET_PROVIDERS = ["deepseek", "opencode-go"] as const;
 export const MINIMAL_PERSONA = "You are a helpful software engineer assistant.";
 export const STATE_ENTRY_TYPE = "pi-dsh-mimic/session-stage";

package/src/index.ts CHANGED Viewed

@@ -12,7 +12,6 @@ import {
   MINIMAL_PERSONA,
   STATE_ENTRY_TYPE,
   TARGET_MODEL_ID,
-  TARGET_PROVIDERS,
 } from "./constants.js";
 import { executeEditor, type EditorArgs } from "./editor.js";
 import {
@@ -184,5 +183,4 @@ export {
   MINIMAL_PERSONA,
   STATE_ENTRY_TYPE,
   TARGET_MODEL_ID,
-  TARGET_PROVIDERS,
 };

package/src/session-stage.ts CHANGED Viewed

@@ -1,7 +1,6 @@
 import {
   STATE_ENTRY_TYPE,
   TARGET_MODEL_ID,
-  TARGET_PROVIDERS,
 } from "./constants.js";
 import { isJsonObject } from "./protocol.js";
@@ -21,9 +20,7 @@ export function supportedRoute(model: { provider?: unknown; id?: unknown } | und
   if (typeof model?.provider !== "string" || typeof model.id !== "string") return undefined;
   const provider = model.provider.toLowerCase();
   const modelId = model.id.toLowerCase();
-  if (modelId !== TARGET_MODEL_ID || !TARGET_PROVIDERS.some((candidate) => candidate === provider)) {
-    return undefined;
-  }
+  if (!modelId.includes(TARGET_MODEL_ID)) return undefined;
   return `${provider}/${modelId}`;
 }