dsh-refix (dsh-refix)
ckk-09/dsh-refix/packages/dsh-refix
Self-diagnosing, self-repairing watchdog for DSH plugins: 15s health patrol, version-switch repair with observe window and auto rollback, unknown symptoms escalated to human.
インストール
dsh plugin --profile web add github:ckk-09/dsh-refixこのプラグインはリポジトリの packages/dsh-refix サブディレクトリにあります。
README
dsh-refix — 给你的 DSH 插件请一位"全科医生"
一句话：它是一个会自己体检、自己开药、自己记病历的 DSH 插件保姆，别的插件出事了它先发现，能修的它自己修，修不好它会老实告诉你。
中文 | English
它能帮你做什么？
想象你的 DSH 会话里跑着好几个动态插件。突然某个插件罢工了、报错了、页面渲染挂了——以前你要自己盯、自己查、自己修。现在有了 dsh-refix：
| 就像医生会… | dsh-refix 会… | 背后的能力 |
|---|---|---|
| 🩺 定期体检 | 每 15 秒 + 出事瞬间自动巡检所有插件，发现"某某插件停了""某某方法报错了" | F1 诊断 |
| 💊 按方开药 | 每种常见病症都有现成的处理方案，没见过的病症绝不动手，只向你报告 | F2 处方 |
| 🏥 治病留观 | 修复 = 切换到新版本，然后观察 30 秒确认真的好了；没修好自动退回旧版本，绝不越修越坏 | F3 执行 |
| 📒 记住病历 | 同一个毛病第二次犯，直接用上次有效的药方；上次治坏了的方子，它不会再试 | F4 迭代 |
| 📢 提醒复查 | 出现新版本时在对话里提醒你，并附上一步步的升级手册（但绝不擅自升级） | F6 更新提示 |
三条铁律贯穿始终：诊断只看不碰、修复绝不删库（永不 undefine）、牵涉浏览器的操作必须你亲自点头。
三分钟上手
一条命令，装完即用 —— 不需要下载源码，也不需要贴任何话术：
dsh plugin --profile web add https://raw.githubusercontent.com/ckk-09/dsh-refix/main/deploy/static/dist/dsh-refix-1.4.0.tgz
然后正常启动 dsh，插件随启动自动加载。控制台出现这一行就成了：
dsh-refix p3.8 ready; contract OK (兼容性自检通过); baseline plugins: N; patrol every 15000ms
想立刻问一句，就说——
调用 refix_report 给我一份 dsh-refix 的自检报告
看到一坨 JSON？恭喜，医生已经上岗了。（注意：插件自身只有 15s 巡检是自动的；出报告与执行修复要有人调工具——你开口就行。）
完整步骤、动态包装法（要在会话里热切换 / 回退版本时用）与高频故障 → QUICKSTART.md。
工具参数、outcome / phase / reason 全表、哈希核对、回退、五个必踩的坑 → TECHNICAL.md 的「使用者参考」。
选哪个版本？
✅ 稳定版（推荐所有人使用）
静态包（V1.4，默认推荐） —— 一条命令装、装完随 dsh 启动自动加载，全程不需要模型介入：
| 定版号 | 产物 | 一句话说明 |
|---|---|---|
| V1.4 | deploy/static/dist/dsh-refix-1.4.0.tgz | 当前推荐：装它只要一条命令。插件逻辑与 V1.10（p3.8）逐字节相同，随源码带上六项独立审查修复 + Phase 2 四项新能力。 |
| V1.3 | deploy/static/dist/dsh-refix-1.3.0.tgz | 上一版静态包（插件逻辑 = V1.08 / p3.7）。 |
| V1.2 | deploy/static/dist/dsh-refix-1.2.0.tgz | 首个静态包发布——改的是交付形态，不是功能（插件逻辑 = V1.07 / p3.4）。 |
动态包源码（V1.0x 线） —— 需要在会话里热切换 / 一键回退版本时用：
| 定版号 | 文件 | 一句话说明 |
|---|---|---|
| V1.01 | versions/refix-v1.01.js | 最小骨架：体检报告能用 |
| V1.02 | versions/refix-v1.02.js | 加入自动巡检 |
| V1.03 | versions/refix-v1.03.js | 会治病了（观察窗 + 自动回退） |
| V1.04 | versions/refix-v1.04.js | 会记病历（知识库复用） |
| V1.05 | versions/refix-v1.05.js | 第一轮安全大修 |
| V1.06 | versions/refix-v1.06.js | 第二轮复检修复 |
| V1.10 | versions/refix-v1.10.js | Phase 2（当前推荐）：F7 主动告警 + 探针两级化 + 知识库导出/回填 + 同 Team 代修放行，并继承 V1.08 全部修复 —— V1.4 静态包就是它的静态形态 |
| V1.08 | versions/refix-v1.08.js | 独立审查修复版：六项缺陷逐条修复 —— V1.3 静态包就是它的静态形态 |
| V1.07 | versions/refix-v1.07.js | 第三轮复检修复 —— V1.0x 的上一版（V1.2 静态包是它的静态形态） |
⚠️ 前瞻版本（尝鲜专用，慎重选择升级安装）
🚧 警告：以下是 V1.1 的预览版（pre），包含实验性改动与潜在的破坏性变更，随时可能调整甚至回退。 不确定就别用；要试，请先看完 TECHNICAL.md 的「已知边界」一节。稳定永远选 V1.4（静态包）。
另外：更新提示只报稳定线。装了 pre 版不会被自动催升级，想装哪个 pre 版请自己指名文件——这个项目不会把实验版塞给普通用户。
| 定版号 | 文件 | 新增了什么 | 风险提示 |
|---|---|---|---|
| V1.1-pre1 | versions/refix-v1.1-pre1.js | 更新探测 + 对话内更新提示 | 实验性功能，未正式发布 |
| V1.1-pre2 | versions/refix-v1.1-pre2.js | 更新提示附带可执行手册 + 外部文本隔离 | 同上 |
| V1.1-pre3 | versions/refix-v1.1-pre3.js | 稳定线全部能力 + F6 更新探测；由 tools/gen-pre.mjs 从 V1.10 单源生成，勿手改 | 同上 |
| V1.1-pre-updater | versions/refix-updater-v1.1-pre.js | 独立的"自动装新版"助手（默认关闭，每次都需你点批准） | 这是全仓库唯一会"从网络拉代码并执行"的能力，含实验性破坏，慎重启用 |
它不会做什么？（免得你担心）
- ❌ 不会删除任何插件（修复只换版本，旧版本永远留着当后悔药）
- ❌ 不会联网拉代码来执行（唯一的例外是那个默认关闭、每次都要你点"允许一次"的 updater）
- ❌ 不会在你不知情时动你的插件（浏览器半区的操作必须走 DSH 原生审批，你说了算）
- ❌ 不会无中生有编修复方案（没见过的病症只报告，交给人）
- ✅ 重启后"失忆"（病历不落盘）——这是刻意设计：不留任何痕迹在你机器上
想深入了解？
| 想知道… | 去看 |
|---|---|
| 一步步怎么装、报错怎么办 | QUICKSTART.md |
工具参数、返回值全表（outcome/phase/reason）、哈希核对、回退、五个坑 | TECHNICAL.md 的「使用者参考」 |
| 全部技术细节：硬边界 B1~B6、诊断策略表、13/13 验收矩阵、8/8 回归、已知边界 | TECHNICAL.md |
| 每个阶段干了什么、踩过什么坑 | reports/ 目录（P0~P4 + P3R/P3R2/P3R3） |
| 验收怎么跑 | TECHNICAL.md 的「运行验收脚本」 |
License
dsh-refix — a "family doctor" for your DSH plugins
In one sentence: a plugin caretaker that checks health on its own, prescribes its own fixes, and keeps its own medical records. When another plugin goes down, it notices first, fixes what it safely can, and honestly reports what it can't.
中文 | English
What does it do for you?
Imagine several dynamic plugins running inside your DSH session. One crashes, another throws, a third fails to render — previously you had to watch, diagnose and fix everything yourself. With dsh-refix:
| Like a doctor who… | dsh-refix… | Capability |
|---|---|---|
| 🩺 runs regular check-ups | patrols every 15s + instantly on events, spotting "plugin X stopped", "method Y throws" | F1 Diagnose |
| 💊 prescribes from a formulary | has a ready fix for every known symptom; unknown symptoms are never touched, only reported | F2 Prescribe |
| 🏥 treats, then observes | a fix = a version switch followed by a 30s observation window; if it didn't hold, it rolls back automatically | F3 Repair |
| 📒 keeps medical records | a recurring symptom reuses the proven fix; a fix that failed last time is never retried | F4 Iterate |
| 📢 calls for follow-ups | injects an update notice with a step-by-step manual when a new version exists (never upgrades by itself) | F6 Update-check |
Three iron rules throughout: diagnosis is strictly read-only; repair never deletes (never undefine); anything touching the browser requires your explicit approval.
Up and running in 3 minutes
One command, done — no source download, no wording to paste:
dsh plugin --profile web add https://raw.githubusercontent.com/ckk-09/dsh-refix/main/deploy/static/dist/dsh-refix-1.4.0.tgz
Then start dsh as usual; the plugin loads automatically on every boot. When you see this line, it is up:
dsh-refix p3.8 ready; contract OK (兼容性自检通过); baseline plugins: N; patrol every 15000ms
To ask for a check right away:
Call refix_report and show me dsh-refix's self-check report
Seeing a JSON blob? Congratulations — the doctor is on duty. (Note: inside the plugin only the 15 s patrol is automatic; reporting and repair require a tool call — just ask the model.)
Full steps, the dynamic-package mount path (use that one when you want to hot-swap or roll back versions inside a session) and high-frequency failures → QUICKSTART.md.
Tool parameters, the outcome / phase / reason tables, hash verification, rollback and five pitfalls you will hit → the 「使用者参考」 section of TECHNICAL.md.
Which version should I pick?
✅ Stable line (recommended for everyone)
Static bundle (V1.4, the default) — one command to install, loads automatically with dsh on every boot, no model involved at any point:
| Release | Artifact | In one line |
|---|---|---|
| V1.4 | deploy/static/dist/dsh-refix-1.4.0.tgz | current recommendation: a single command to install. Plugin logic is byte-for-byte identical to V1.10 (p3.8) and carries the six independent-review fixes plus the four Phase 2 capabilities. |
| V1.3 | deploy/static/dist/dsh-refix-1.3.0.tgz | previous static release (plugin logic = V1.08 / p3.7). |
| V1.2 | deploy/static/dist/dsh-refix-1.2.0.tgz | first static-bundle release — changes the delivery form, not the features (plugin logic = V1.07 / p3.4). |
Dynamic-package sources (V1.0x line) — use these when you want to hot-swap or roll back versions inside a session:
| Release | File | In one line |
|---|---|---|
| V1.01 | versions/refix-v1.01.js | minimal skeleton: report tool works |
| V1.02 | versions/refix-v1.02.js | adds automatic patrol |
| V1.03 | versions/refix-v1.03.js | can treat (observe window + auto-rollback) |
| V1.04 | versions/refix-v1.04.js | keeps records (knowledge base) |
| V1.05 | versions/refix-v1.05.js | first security hardening pass |
| V1.06 | versions/refix-v1.06.js | second review-fix pass |
| V1.10 | versions/refix-v1.10.js | Phase 2 (current recommendation): F7 proactive alerts + two-level probe + knowledge export/restore + same-team repair — inherits all V1.08 fixes; V1.4 is its static form |
| V1.08 | versions/refix-v1.08.js | independent-review fix pass: six defects fixed — V1.3 is its static form |
| V1.07 | versions/refix-v1.07.js | third review-fix pass — previous release of the V1.0x line (V1.2 is its static form) |
⚠️ Preview line (experimental — upgrade with caution)
🚧 Warning: the V1.1-pre series is a preview of V1.1 with experimental, potentially breaking changes, subject to change or rollback at any time. If unsure, stay on V1.4 (static bundle). If you must try, read the "Known limits" section of TECHNICAL.md first.
Also: update notices only ever report the stable line. Having a pre build installed will never nag you to upgrade, and if you want a specific pre version, name the file yourself — this project does not push experimental builds onto ordinary users.
| Release | File | What's new | Risk note |
|---|---|---|---|
| V1.1-pre1 | versions/refix-v1.1-pre1.js | update probe + in-conversation update notice | experimental, unreleased |
| V1.1-pre2 | versions/refix-v1.1-pre2.js | notice carries a step-by-step manual + external-text isolation | same |
| V1.1-pre3 | versions/refix-v1.1-pre3.js | every capability of the stable line + F6 update probe; generated by tools/gen-pre.mjs from V1.10 — do not hand-edit | same |
| V1.1-pre-updater | versions/refix-updater-v1.1-pre.js | separate "install new version" helper (off by default, asks for approval every time) | the only capability in this repo that fetches code from the network and executes it — experimental, potentially breaking; enable with care |
What it will NOT do (so you can relax)
- ❌ Never deletes a plugin (repair only switches versions; old versions stay as undo points)
- ❌ Never fetches and executes code from the network (the only exception is the off-by-default updater that asks for your explicit "allow once" every time)
- ❌ Never touches your plugins without your consent (browser-side operations go through DSH's native approval flow — you decide)
- ❌ Never invents fixes (unknown symptoms are reported, handled by a human)
- ✅ Forgets everything on restart (records are not persisted) — by design: nothing is left on your machine
Want to dig deeper?
| Looking for… | Go to |
|---|---|
| Step-by-step install and troubleshooting | QUICKSTART.md |
Tool parameters, full return-value tables (outcome/phase/reason), hash verification, rollback, five pitfalls | the 「使用者参考」 section of TECHNICAL.md |
| Full technical detail: boundaries B1~B6, symptom policy table, 13/13 AC matrix, 8/8 regression, known limits | TECHNICAL.md |
| What each stage did and what pitfalls were hit | reports/ (P0~P4 + P3R/P3R2/P3R3) |
| How to run acceptance | Run the acceptance scripts |