npm - pi-patch-keeper - Versions diffs - 1.1.1 → 1.2.0 - Mend

pi-patch-keeper 1.1.1 → 1.2.0

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 (3) hide show

package/README.en.md CHANGED Viewed

@@ -1,44 +1,57 @@
-# pi-patch-keeper — patch self-healing and status checks (pi extension)
+# pi-patch-keeper — pi configuration guards (pi extension)
-Turns "patches to other people's packages must be re-applied after every upgrade" into startup self-healing with an explicit report.
+> Requires pi >= 0.74 · Node >= 20 · MIT · no runtime dependencies · no PiDeck or third-party patching
-## What it heals
+Checks three classes of hazards in pi's own configuration at session start: what can be fixed is fixed, the rest is reported clearly.
-| Target | Action |
-| --- | --- |
-| pi-lens wordindex patch (symbol_search stuck on "building") | fixes in place at startup; stops when upstream ships the fix (warm_cache_adopted) |
-| pi-memory exit summary / section precedence | fixes in place, backup first |
-| pi-tactician section precedence | fixes in place, backup first |
-| PiDeck builtin extensions (5, dual copies) | restores from the snapshot copy when a release overwrites them |
-| PiDeck app.asar (3 patches) | detect only (file locked while PiDeck runs) |
-| force-typed extension order | auto-moves known force-typed packages to the end, backup first |
-| manual version vs injected version | warns once per mismatch pair |
+## Features
+- **codemode single-source check**: disabling `builtin:codemode` and installing `pi-codemode-guard` must agree.
+- **force-order guard**: force-type extensions (e.g. rtk / cache-optimizer) must sit last in `packages`, otherwise later section writes are silently dropped; wrong order is fixed automatically (with a backup).
+- **Environment fingerprint drift**: notifies when `settings.json` packages / defaultTools / enabledModels / extensions / codemode change, since manuals or prior verification may be stale.
+- **Injection alignment**: compares the injected `APPEND_SYSTEM.md` version with the on-disk version and, on mismatch, tells the model to trust disk.
+- Commands `/patch-keeper` (status) and `/patch-keeper fix` (repair force order).
 ## Install
-    pi install npm:pi-patch-keeper
-    pi install ./pi-patch-keeper
+```bash
+pi install npm:pi-patch-keeper
+pi install ./pi-patch-keeper
+```
+## Configuration
-Reload or restart the session after installing.
+**No config file**: the package only reads `settings.json` and the manual.
-## Commands
+| Item | Path | Description |
+| --- | --- | --- |
+| Fingerprint | `~/.pi/patch-keeper.json` | Settings snapshot from the previous start, used for drift detection (self-maintained) |
+| Manual sentinel | `~/.pi/patch-keeper-manual.json` | Manual version / content signature, catches "content changed without a version bump" |
+| Fix backup | `~/.pi/agent/settings.json.bak-force-order-*` | Backup created before repairing force order |
-| Command | Effect |
+### Commands
+| Command | Purpose |
 | --- | --- |
-| /patch-keeper | status of every patch face |
-| /patch-keeper fix | heal what can be healed now |
+| `/patch-keeper` | Show codemode / force / fingerprint / injection-alignment status |
+| `/patch-keeper fix` | Repair force order in `packages` (with backup) |
+### Not included (local-only module)
+PiDeck builtin patch restoration, read-only asar checks, pi-lens / pi-memory / pi-tactician source patches, local snapshot restore — all depend on the PiDeck install directory, third-party internals or local paths, so they are **not shipped** with this package. They live in a local module `patch-keeper-local` (`/patch-keeper-local`).
-## Discipline
+## How it works
-- Never returns systemPrompt; only notifies.
-- Any failure is reported as a hint, never thrown.
-- All paths derive from the home directory, so it survives machine, username and drive changes.
+- On factory startup it compares fingerprints and self-checks force order; failures only notify, never throw or disturb the session.
+- Injection alignment compares versions in `before_agent_start` and only writes its own notification and trailing message; it **never returns systemPrompt** (which would replace the whole prompt and drop other sections).
+- All writes are atomic (temp file + rename).
-## Limits
+## Limitations
-- asar patches cannot be applied while PiDeck is running; the extension only reports them.
-- Upstream patches are detected by marker strings; a substantially rewritten upstream file is reported as unknown instead of being patched.
+- Covers pi's own configuration only, not third-party plugin behaviour.
+- Force-order repair targets a built-in list of known force-type packages.
+- Fingerprint drift reports what changed, not whether the new value is correct.
 ## License
-MIT.
+MIT

package/README.md CHANGED Viewed

@@ -1,63 +1,57 @@
-# pi-patch-keeper —— 补丁自愈与状态检测（pi 扩展）
+# pi-patch-keeper —— pi 配置守卫（pi 扩展）
-## 安装
-npm 发布版：`pi install npm:pi-patch-keeper`
-本地目录：`pi install <path/to/patch-keeper>`
-安装后 `/reload` 或重启会话生效（扩展源码改动需重启）。
+> 适用 pi ≥ 0.74 · Node ≥ 20 · MIT · 无运行时依赖 · 不含 PiDeck / 第三方补丁
-**是什么**：把「对别人的东西」的改动（**12 个面**：PiDeck builtin ×5 双份 · npm 包 ×4 · app.asar ×3）从「升级后手工重跑」变成**启动自愈 + 明确报告**——外置、模块化、抗上游升级。全量清单由本机补丁登记表维护（PATCH-REGISTRY，随快照包分发）。
+在每次会话启动时检查 pi 自身配置的三类隐患，能修的直接修，不能修的明确报出来。
-## 来源与借鉴
+## 功能
-原创，无上游实现。设计灵感来自本机长期维护 PiDeck / pi 补丁的实践：补丁会被升级覆盖，故需要启动时自检与自愈。
+- **codemode 单点一致性**：禁 `builtin:codemode` 与安装 `pi-codemode-guard` 必须同时成立。
+- **force 顺序守卫**：force 型扩展（如 rtk / cache-optimizer）必须排在 `packages` 末尾，否则其后的 section 写入会被静默丢弃；发现乱序自动修复（先备份）。
+- **环境指纹漂移**：`settings.json` 的 packages / defaultTools / enabledModels / extensions / codemode 变化时提示「手册或上轮验证结论可能过期」。
+- **注入对齐**：比对注入的 `APPEND_SYSTEM.md` 版本与磁盘版本，不一致时提示「以磁盘版为准」，并同步回灌模型。
+- 命令 `/patch-keeper` 查看全部状态，`/patch-keeper fix` 修复 force 顺序。
-## 机制（源码级）
-1. **session_start 自检**（每次 pi 启动）：
-   - **pi-lens wordindex 补丁：能修的直接修**——本扩展是 user 扩展（加载 rank 2），先于 pi-lens 的 package rank 4；factory 内同步改 `dist/index.js`，pi-lens 随后 import 到的即打过补丁的内容（**当轮生效**）；半打状态先还原再重打（幂等）。**上游发版后停手**：dist 出现 `warm_cache_adopted`（#4583 / PR #4586）即视为 A 已修复——跳过 A、只补 B（B 上游未修），`/patch-keeper` 显示「上游已修复 #4583」。
-   - **pi-memory exit summary 空行规范化：能修的直接修**——改 npm pi-memory 的 `index.ts`（render 侧规范块级空行；幂等；写前留 `.bak-exitsummary-<stamp>` 备份）。
-   - **PiDeck asar 三补丁：只检测不修**——PiDeck 运行中文件被锁、插件无权碰 Electron 主进程；检测到未打补丁时提示跑 `launch-pideck.cmd`（启动前自动重打）或快照 `05-脚本补丁/` 下脚本。
-2. **before_agent_start 注入对齐检测**：比对「本轮注入的手册版本」vs「磁盘版」——不一致提示**一次**（同 pair 去重）；方向不限（注入滞后 / 磁盘回滚都可能）。
-3. **环境漂移指纹**：`~/.pi/patch-keeper.json` 记录 settings 关键字段（packages / defaultTools 等）——支撑漂移检测。
-4. **force 顺序守卫（自动修复）**：packages 中条件 force 型（pi-rtk-optimizer / pi-cache-optimizer）须在末尾——启动与 /patch-keeper fix 时自动移到末尾（先备份 settings.json.bak-force-order-*），修复幂等；其后 section 写入不会被静默丢弃。
-5. **force 型扩展扫描（疑似）**：扫描 packages 入口源码中的 return { systemPrompt } / forceSystemPrompt，报告疑似无条件 force 的包（会覆盖 system、使其后 section 静默丢失）；位于中间者启动时提示。先写 section、只有旧宿主才 force 的归为「兼容兜底」，不计入疑似。
-## 自我回灌（条件触发型）
+## 安装
-与 caveman / ptc-meter / think-anchor 的「每轮回灌」不同：**常态零注入**，只在异常时出声一次——
+```bash
+pi install npm:pi-patch-keeper
+pi install ./pi-patch-keeper
+```
-- 每轮 before_agent_start 比对「本轮实际注入的手册版本」vs「磁盘版本」；
-- 不一致（注入滞后 / 磁盘回滚均可能）→ 一次 notify 提示「以磁盘为准、先读回全文」（同 pair 去重，不重复打扰）；
-- notify 用户 + 回灌模型（nextTurn，四律②：用户侧收到后模型也须知道，否则「以磁盘为准」停在用户侧）；检测失败静默。
+## 配置
-## 纪律（回灌四律实践）
+**无配置文件**：本包只读 `settings.json` 与手册，不引入自己的配置项。
-- **绝不返回 systemPrompt**——只 notify；任何失败静默（检测不该影响会话，绝不抛错）。
-- 路径全部从 home / `%LOCALAPPDATA%` 推导——换机、换用户名、复刻包到别机均可用。
+| 项 | 路径 | 说明 |
+| --- | --- | --- |
+| 环境指纹 | `~/.pi/patch-keeper.json` | 上次启动时的配置快照，用于漂移对比（自动维护） |
+| 手册哨兵 | `~/.pi/patch-keeper-manual.json` | 手册版本 / 内容签名，用于检测「改了内容没升版本」 |
+| 自动修复备份 | `~/.pi/agent/settings.json.bak-force-order-*` | 修复 force 顺序前的备份 |
-## 配置与命令
+### 命令
-| 项 | 值 |
+| 命令 | 作用 |
 | --- | --- |
-| 指纹文件 | `~/.pi/patch-keeper.json`（随 settings 变化同步） |
-| 命令 | `/patch-keeper`（状态）· `/patch-keeper fix`（能修的立即修） |
+| `/patch-keeper` | 输出 codemode / force / 指纹 / 注入对齐状态 |
+| `/patch-keeper fix` | 修复 `packages` 的 force 顺序（带备份） |
-## 生效与回滚
+### 不包含（本机专用模块）
-- 生效：装上即用（每次会话启动自检）；代码改动 `/reload` 或重启。
-- 回滚：删本目录；已打补丁保持原样（回退用 `05-脚本补丁/` 下脚本各自的 rollback）。
+PiDeck builtin 补丁双份恢复、asar 只读检测、pi-lens / pi-memory / pi-tactician 源码补丁、本机快照恢复 —— 这些依赖 PiDeck 安装目录、第三方包内部实现与本机路径，**不随本包发布**，由本机模块 `patch-keeper-local` 提供，命令 `/patch-keeper-local`。
-## 测试
+## 机制
-源码仓库内的隔离自测覆盖：force 顺序三例、命令注册、版本不一致告警一次的 pair 去重、一致静默、空 event 不抛、session_start 失败静默、自建扩展被覆盖后从快照恢复、上游已修标记（A 停打 / 仅补 B）。
+- 启动时（factory）执行指纹对比与 force 自检；失败只提示，绝不抛错、不影响会话。
+- 注入对齐在 `before_agent_start` 比较版本，只写自己的通知与尾部消息，**绝不返回 systemPrompt**（避免覆盖式替换丢掉其他 section）。
+- 所有写盘走「临时文件 + rename」原子写。
-## 环境依赖与降级
+## 限制
-补丁目标（npm 包与 PiDeck builtin）不存在时对应项跳过并只报状态，不报错；本机快照目录（备份与恢复来源）缺失时，恢复类动作跳过，自愈仍然工作。适配任意用户名与安装路径。
+- 只覆盖 pi 自身配置；不检查第三方插件行为。
+- force 顺序修复只对已知的 force 型包生效（列表内置，随版本更新）。
+- 指纹对比只报「变了什么」，不判断新值是否正确。
 ## License
-MIT.
+MIT

package/package.json CHANGED Viewed

@@ -1,7 +1,7 @@
 {
   "name": "pi-patch-keeper",
-  "version": "1.1.1",
-  "description": "Startup self-healing for pi/pi-lens/pi-memory/PiDeck patches, plus force-typed extension order guard and status report.",
+  "version": "1.2.0",
+  "description": "pi config guards: codemode single-source check, force-order guard (auto-fix), settings fingerprint drift, injected-manual alignment. (PiDeck / third-party source patches are a local-only module, not bundled.)",
   "type": "module",
   "license": "MIT",
   "keywords": [