@mokuyoaxis/agent-guard 0.2.5 → 0.2.7

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 (52) hide show
  1. package/README.md +61 -23
  2. package/README.zh-CN.md +51 -22
  3. package/adapters/INTEGRATION.md +90 -10
  4. package/adapters/claude/README.md +6 -0
  5. package/adapters/dsh/README.md +19 -8
  6. package/adapters/dsh/compatibility.json +14 -0
  7. package/adapters/dsh/harness/README.md +11 -0
  8. package/adapters/dsh/harness/guard_lab.py +42 -14
  9. package/adapters/kimi-code/README.md +154 -14
  10. package/adapters/kimi-code/compatibility.json +1 -1
  11. package/adapters/kimi-code/config.example.toml +18 -6
  12. package/adapters/kimi-code/hook_bridge.sh +19 -4
  13. package/adapters/kimi-code/pre_tool_use.py +1 -1
  14. package/adapters/kimi-code/stop_feedback.py +237 -0
  15. package/adapters/mcp/__init__.py +1 -0
  16. package/adapters/mcp/operations.py +174 -0
  17. package/adapters/mcp/requirements.txt +3 -0
  18. package/adapters/mcp/server.py +126 -0
  19. package/core/admission.py +388 -0
  20. package/core/audit.py +1 -1
  21. package/core/classifier.py +2 -1
  22. package/core/cleanup.py +297 -0
  23. package/core/delete_config.py +153 -0
  24. package/core/policy.py +35 -7
  25. package/core/recovery.py +10 -0
  26. package/docs/README.md +25 -7
  27. package/docs/design/architecture.md +16 -4
  28. package/docs/design/compatibility.md +230 -6
  29. package/docs/design/dsh-compatibility.md +65 -0
  30. package/docs/design/threat-model.md +53 -1
  31. package/docs/guides/cleanup-plan.md +227 -0
  32. package/docs/guides/deletion-limits.md +150 -0
  33. package/docs/guides/getting-started.md +72 -11
  34. package/docs/guides/harness-capabilities.md +37 -4
  35. package/docs/guides/host-drift.md +32 -0
  36. package/docs/guides/mcp.md +293 -0
  37. package/docs/guides/recovery-feedback.md +29 -1
  38. package/docs/history/friction.md +99 -1
  39. package/docs/releases/release-notes-0.2.6.md +167 -0
  40. package/docs/releases/release-notes-0.2.7.md +217 -0
  41. package/docs/releases/unreleased.md +275 -0
  42. package/docs/reports/test-report-dsh-alpha4.md +102 -0
  43. package/docs/reports/test-report-dsh-paired-lab.md +1 -1
  44. package/docs/reports/test-report-kimi-code-block.md +120 -7
  45. package/doctor.py +175 -28
  46. package/package.json +13 -2
  47. package/skills/delete-guard/SKILL.md +69 -1
  48. package/skills/delete-guard/references/policy.md +66 -3
  49. package/skills/delete-guard/scripts/check.py +39 -9
  50. package/skills/delete-guard/scripts/cleanup.py +164 -0
  51. package/skills/delete-guard/scripts/safe_delete.py +22 -4
  52. package/skills/delete-guard/scripts/status.py +77 -1
@@ -0,0 +1,167 @@
1
+ # 0.2.6 — Kimi feedback, diagnostics and host compatibility
2
+
3
+ Released 2026-10-22 as the stable maintenance release on npm `latest`.
4
+ Use the exact [GitHub release](https://github.com/mokuyoaxis/agent-guard/releases/tag/0.2.6)
5
+ and [npm version](https://www.npmjs.com/package/@mokuyoaxis/agent-guard/v/0.2.6)
6
+ to identify the package. RC and hotfix channels keep their existing versions.
7
+ See [getting started](https://github.com/mokuyoaxis/agent-guard/blob/0.2.6/docs/guides/getting-started.md) for installation and setup.
8
+
9
+ 本版补齐 Kimi 恢复信息的反馈出口与本地诊断,细分 DSH Lab 预检失败原因,
10
+ 并为默认删除适配增加 DSH `0.2.1-alpha.4`、为 Kimi Bash profile 增加精确版本 `2.3.0`。
11
+ 已有安装需要升级;Kimi Stop 仍需显式配置,并在新会话中加载。
12
+
13
+ ## Kimi recovery feedback
14
+
15
+ In the sampled Kimi 0.42.0, 2.1.1 and 2.3.0 success-hook paths, the recovery
16
+ explanation did not enter the next model request. A successful Bash result
17
+ therefore did not tell the model that files had moved to quarantine.
18
+
19
+ The optional POSIX Stop hook supplies actual transaction IDs, inspection and
20
+ restore commands, retained-storage guidance and complete GC commands. It asks
21
+ for an additional response after new compensation records. Existing
22
+ PreToolUse-only installations keep their behavior; Stop must be explicitly
23
+ configured and read by a new Kimi session.
24
+
25
+ The initial answer appears first and may be inaccurate. Stop adds a model
26
+ generation and cannot repair the earlier tool result. Emission cursors suppress
27
+ repeated notices in the tested scope; they are not model acknowledgements.
28
+ Cancellation, exhausted budgets and shared-session actors retain their limits.
29
+ The hook executes no restore or GC. Restoring files moves them back without
30
+ freeing total disk space; permanent GC removes recovery copies.
31
+
32
+ The example recommends PreToolUse 120 seconds around the unchanged internal
33
+ 90-second check, and Stop 30 seconds. Missing or timed-out hooks can still
34
+ allow tools in the sampled hosts. The outer timeout margin does not change
35
+ that behavior. See [setup and limits](https://github.com/mokuyoaxis/agent-guard/blob/0.2.6/adapters/kimi-code/README.md#optional-recovery-feedback-unreleased-checkout-addition)
36
+ and the [bounded host report](https://github.com/mokuyoaxis/agent-guard/blob/0.2.6/docs/reports/test-report-kimi-code-block.md).
37
+
38
+ ## Kimi 2.3.0 Bash compatibility
39
+
40
+ The Kimi compatibility profile now lists exact versions `0.42.0`, `2.1.1`
41
+ and `2.3.0`. The new version has eight actual prompt-CLI and eight ACP trials
42
+ with fixed loopback responses: allow, BLOCK, ASK hard refusal, Python startup
43
+ failure, hook absence, recovery, partial compensation and optional Stop
44
+ delivery. ACP hook process/payload cwd matched the session workspace even
45
+ when the service started in another directory. No external model calls were
46
+ made. See the [bounded report](https://github.com/mokuyoaxis/agent-guard/blob/0.2.6/docs/reports/test-report-kimi-code-block.md#kimi-230-acceptance).
47
+
48
+ Core and bridge behavior are unchanged. A valid 2.3.0 local preflight can
49
+ be `CURRENT`, while unlisted versions remain `STALE`. Existing baselines may
50
+ be `DRIFTED` because the profile fingerprint changed; they are not overwritten.
51
+ This does not add subagent, background, other-tool or real-model guarantees.
52
+ Web checks covered startup/status/shutdown, not Web tool calls. The separate
53
+ Kimi Lab capture helper remains pinned to 2.1.1. Published 0.2.5 retains its
54
+ recorded list; upgrade that installation to obtain the new profile.
55
+
56
+ ## Separate Stop doctor results
57
+
58
+ `doctor.py kimi --probe --json` retains the existing top-level PreToolUse
59
+ results and adds `feedback` for optional Stop:
60
+
61
+ - Absent Stop is `NOT_CONFIGURED` and does not fail the CLI. An unreadable or
62
+ invalid configuration is `UNVERIFIED`, rather than a claim that Stop is off.
63
+ - Checks cover the event, absolute shell/bridge/Python command, option,
64
+ matcher, timeout, duplicate definitions and helper presence.
65
+ - A requested local probe runs synthetic records in its own temporary
66
+ home/workspace/trash. It checks feedback content and repeat suppression
67
+ without touching existing recovery records or calling a model. PreToolUse
68
+ probes also isolate inherited recovery locations.
69
+ - A configured Stop that fails configuration or a requested local probe makes
70
+ the CLI exit 1 and drift `BROKEN`, prevents writing a passing baseline and
71
+ stops the live sentinel before it can call a model.
72
+ - Configured Stop fields and helper bytes join drift fingerprints. Runtime
73
+ fingerprints include `package.json`, so the version change itself can
74
+ produce `DRIFTED` against an older baseline. Review the change before
75
+ creating a new baseline at a new path.
76
+
77
+ `feedback.model_delivery` always remains `UNVERIFIED`, including after a
78
+ Bash live sentinel. Local success does not prove a live host loaded Stop or
79
+ a model received its feedback. The importable `check_kimi()` wrapper remains
80
+ PreToolUse-only; Claude output retains its existing contract.
81
+ See the [doctor fields](https://github.com/mokuyoaxis/agent-guard/blob/0.2.6/adapters/kimi-code/README.md#stop-doctor-checks-unreleased).
82
+
83
+ ## DSH Lab preflight diagnostics
84
+
85
+ Version/config checks distinguish `START_FAILED`, `TIMEOUT`, `OUTPUT_LIMIT`,
86
+ `NONZERO_EXIT`, `EMPTY_STDOUT` and `UNSUPPORTED_VERSION`. Errors retain their
87
+ stage text and add JSON with the child exit code, capture flags,
88
+ elapsed/deadline seconds and captured byte counts. Raw configuration, stderr,
89
+ command arguments and environment values are omitted.
90
+
91
+ The Lab CLI still exits 1 on failure. Its 10/15-second budgets and admitted
92
+ DSH versions remain unchanged, without automatic retry. Consumers should
93
+ inspect diagnostic fields rather than match the whole old error sentence.
94
+ This concerns the Lab controller, not production deletion policy.
95
+ See the [Lab runner guide](https://github.com/mokuyoaxis/agent-guard/blob/0.2.6/adapters/dsh/harness/README.md).
96
+
97
+ ## Upgrade scope
98
+
99
+ The default DSH deletion adapter now admits `0.2.1-alpha.4` alongside
100
+ `0.1.5-rc.1` and `0.2.0-rc.2`. The top-level engines, optional DSH peer and
101
+ nested bundle declaration match the exact list. This corrects the loader
102
+ metadata: the nested field alone was not an admission gate. Reviewed loaders
103
+ now reject tested unlisted hosts without exemptions. The optional peer does
104
+ not install DSH. See [compatibility](https://github.com/mokuyoaxis/agent-guard/blob/0.2.6/docs/design/dsh-compatibility.md) and
105
+ [native validation](https://github.com/mokuyoaxis/agent-guard/blob/0.2.6/docs/reports/test-report-dsh-alpha4.md).
106
+
107
+ Optional read protection and Lab retain their two-version boundaries.
108
+
109
+ Core decisions, rm wildcard refusal, command recognition, workspace boundaries,
110
+ recovery formats and manual GC retain their contracts. No production
111
+ dependency or storage/configuration migration is introduced. Stop is opt-in;
112
+ the local doctor exit behavior for an invalid configured Stop is
113
+ upgrade-visible. Earlier RC and hotfix artifacts retain their separate scope.
114
+
115
+ The maintainer selected 0.2.6 for this feedback/diagnostic maintenance. The
116
+ [compatibility contract](https://github.com/mokuyoaxis/agent-guard/blob/0.2.6/docs/design/compatibility.md) records the bounded
117
+ maintenance-version exception for its additive diagnostics. This does not
118
+ authorize unrelated policy changes under the patch versioning rules.
119
+
120
+ ## Validation and limits
121
+
122
+ The implementation checkpoint
123
+ [9295b9a](https://github.com/mokuyoaxis/agent-guard/commit/9295b9a8ccadba1a5a34b71fe049105fd8aefe6b)
124
+ passed [all 13 CI jobs](https://github.com/mokuyoaxis/agent-guard/actions/runs/39804200594)
125
+ on 2026-10-22. Linux and macOS each ran the complete 974-test discovery on
126
+ Python 3.9–3.13. Python 3.9/3.10 each retained 29 conditional skips;
127
+ 3.11–3.13 had none. Both Node groups, 113 DSH native-Lab checks, 92 focused
128
+ Windows Core checks and the end-to-end workspace-root refusal smoke passed.
129
+ Linux's full matrix is pinned to Ubuntu 24.04 because Ubuntu 26.04 lacks the
130
+ Python 3.9 build. No version or test was removed to resolve that setup failure.
131
+ Final publication wording changes only Markdown; runtime, tests and policies
132
+ retain that checkpoint's bytes.
133
+
134
+ The later DSH expansion has separate actual CLI Profile/Boot evidence on all
135
+ three admitted hosts and alpha.4 scripted root/child-agent and native approval
136
+ checks. No external model request was made. Its new manifest/forwarding tests,
137
+ package verification and limits are recorded in the
138
+ [DSH report](https://github.com/mokuyoaxis/agent-guard/blob/0.2.6/docs/reports/test-report-dsh-alpha4.md); the earlier full run below
139
+ does not include this later manifest change. The implementation CI above does.
140
+
141
+ ### Historical local checkpoint
142
+
143
+ Before this version/document alignment, the unchanged implementation passed
144
+ one complete frozen run on 2026-10-21: **974 Python tests and both Node groups**,
145
+ with no failure, error or skip. The same 195-file candidate completed all three
146
+ stages in 1270.573 seconds within the unchanged 1800-second deadline, without
147
+ retry. An internal unittest result collector wrote immediate failures and
148
+ flushed per-test events; the discovery scope matched `npm test`. This was a
149
+ single continuous workflow, not a combination of earlier targeted runs.
150
+
151
+ The local environment was ARM64/PRoot Debian, Python 3.13.5 and Node v22.23.2.
152
+ Earlier full-run errors/timeouts remain historical failures; their original
153
+ causes are not established by this passing run. The version assertion and
154
+ package metadata were aligned separately during preparation. The prior
155
+ 139-file offline package described the pre-version checkpoint, not a
156
+ published or already-validated 0.2.6 artifact.
157
+
158
+ The later Kimi 2.3.0 profile alignment and its bounded host trials also
159
+ postdate the historical full run. They do not turn that run into a complete
160
+ validation of the final candidate. Earlier actual-CLI loopback trials
161
+ covered sampled Kimi 0.42.0/2.1.1 paths;
162
+ one bounded 2.1.1 real-model session received the actual transaction and full
163
+ commands, followed by restoration and repeat-Stop checks. Publishing this
164
+ release adds no new host/model trial or general subagent/background guarantee.
165
+ The historical local run did not execute other Python versions, macOS or
166
+ Windows; the remote CI above supplies separate platform evidence. Passing CI
167
+ does not establish the cause of the earlier local timeouts or failures.
@@ -0,0 +1,217 @@
1
+ # 0.2.7 — Cleanup, deletion limits and local MCP
2
+
3
+ Version 0.2.7 adds Cleanup plans, shared deletion admission and optional local
4
+ MCP tools to [0.2.6](https://github.com/mokuyoaxis/agent-guard/blob/0.2.7/docs/releases/release-notes-0.2.6.md).
5
+ Use the exact [GitHub release](https://github.com/mokuyoaxis/agent-guard/releases/tag/0.2.7)
6
+ and [npm version](https://www.npmjs.com/package/@mokuyoaxis/agent-guard/v/0.2.7)
7
+ to verify availability before installing; a manifest, checkout or local
8
+ tarball alone does not establish publication. This version leaves the
9
+ existing `rc` and `hotfix` channels unchanged. The separate 0.3.0 plan remains
10
+ paused. Local preparation evidence below is dated 2026-10-29.
11
+
12
+ 本版收录 Cleanup Copilot、删除准入加固和可选本地 MCP 工具。新增预算与保护
13
+ 可能拒绝此前可执行的删除。安装前请确认精确版本的发行与包页面可用;下方
14
+ 版本化测试、打包与发布门记录单独保留,不能沿用旧 0.2.6 元数据工件的结论。
15
+
16
+ <a id="candidate-scope"></a>
17
+
18
+ ## Version scope
19
+
20
+ ### Cleanup Copilot
21
+
22
+ `agent-guard-cleanup` proposes workspace candidates with logical sizes,
23
+ reasons and projected effects in four categories: regenerable, explicitly
24
+ caller-declared discarded, uncertain and protected. Age, ignore status or
25
+ being untracked alone does not make a file disposable.
26
+
27
+ Default planning writes no workspace files, guard metadata or audit records.
28
+ Execution requires an unchanged reviewed plan, explicit selection and terminal
29
+ `EXECUTE` confirmation, then delegates to the existing safe_delete path.
30
+ Valuable files retain recovery copies and disk use; only provably regenerable
31
+ artifacts follow the existing physical-delete rules. See
32
+ [the workflow and limits](https://github.com/mokuyoaxis/agent-guard/blob/0.2.7/docs/guides/cleanup-plan.md).
33
+
34
+ ### Shared deletion admission
35
+
36
+ Optional `.agent-guard/delete-policy.json` supplies protected paths and limits.
37
+ Missing configuration uses defaults; malformed configuration or unusable
38
+ admission state refuses covered execution instead of silently disabling it.
39
+ The configuration directory and admission control files are protected.
40
+
41
+ | Default | Value |
42
+ |---|---|
43
+ | Quarantine admission ceiling | 5 GiB / 100000 entries |
44
+ | Cumulative session budget | 1 GiB / 10000 entries |
45
+ | Rolling rate | 60 admissions per 60 seconds |
46
+ | Repeated normalized target set | 5 admissions per window |
47
+ | Batch review threshold | Above 256 MiB or 1000 entries |
48
+
49
+ Measurement, durable debit and guarded mutation share a cross-process lock.
50
+ Unnamed CLI processes use a stable shared budget; failures and later restores
51
+ do not refund admitted bytes/entries. Rate windows expire, while cumulative
52
+ budgets require explicit operator action. A repeated-target-set stop is a
53
+ simple loop signal, not a general anomaly detector.
54
+
55
+ Large covered automated deletions return `BLOCK_DELETE_BATCH_CONFIRM` with
56
+ Cleanup guidance. The shell checker combines supported rm/artifact/Git-clean
57
+ targets across a request before its first compensation. Cleanup confirmation
58
+ creates a ten-minute session/configuration/path/metadata-bound approval,
59
+ consumed once per selected path; it lifts only the batch gate, not protection,
60
+ capacity, budget or rate limits.
61
+
62
+ The additive refusal codes are:
63
+
64
+ - `BLOCK_DELETE_CONFIG_INVALID`
65
+ - `BLOCK_DELETE_PROTECTED`
66
+ - `BLOCK_DELETE_LIMIT`
67
+ - `BLOCK_DELETE_RATE`
68
+ - `BLOCK_DELETE_REPEAT`
69
+ - `BLOCK_DELETE_BATCH_CONFIRM`
70
+ - `BLOCK_DELETE_STATE_INVALID`
71
+
72
+ Existing Decision classes, check.py exit roles and recovery-manifest formats
73
+ retain their contracts. No data/configuration migration or automatic GC is
74
+ introduced. See [defaults, accounting and operator recovery](https://github.com/mokuyoaxis/agent-guard/blob/0.2.7/docs/guides/deletion-limits.md)
75
+ and the [compatibility contract](https://github.com/mokuyoaxis/agent-guard/blob/0.2.7/docs/design/compatibility.md) for the bounded
76
+ maintainer decision to select 0.2.7 for these additions.
77
+
78
+ ### Optional local MCP tools
79
+
80
+ `agent-guard-mcp` exposes safe_delete, ordinary restore, transactions, status
81
+ and GC-plan preview over local stdio. Workspace, local quarantine and stable
82
+ session identity are fixed at trusted startup. Tools cannot supply a new
83
+ workspace/session/environment, force restore, GC execution, budget reset or
84
+ Cleanup approval. Quarantine targets are refused by MCP safe_delete to avoid
85
+ a permanent-GC shortcut.
86
+
87
+ The official MIT-licensed `mcp==2.3.0` SDK is installed separately in an
88
+ optional Python 3.10+ environment. Core/CLI still requires Python 3.9+ and Git
89
+ without third-party Python packages; npm does not install the SDK. No server
90
+ network listener is provided. Follow the [MCP setup guide](https://github.com/mokuyoaxis/agent-guard/blob/0.2.7/docs/guides/mcp.md).
91
+
92
+ MCP is an explicit cooperative tool interface. It does not intercept shell,
93
+ script or editor operations that bypass it. Startup session selection chooses
94
+ the existing CLI authorization mode as well as budget. It does not inherit
95
+ native host restrictions or an in-memory veto without trusted bridging.
96
+
97
+ ## Upgrade and operator notes
98
+
99
+ - Covered automated filesystem compensation, regenerable direct deletion,
100
+ Git-clean compensation and force-restore occupant preservation can newly
101
+ refuse work when limits are reached. An earlier advisory assessment is not
102
+ a capacity grant. A later refusal can follow completed earlier operations;
103
+ inspect returned transaction IDs and the filesystem.
104
+ - Normal restore remains available without a fresh deletion debit. Explicit
105
+ transaction GC and existing unprotected quarantine housekeeping retain
106
+ their exemptions; configuration/control-path protection still precedes
107
+ housekeeping. The existing GC CLI's `--execute` does not require a TTY;
108
+ MCP's preview-only scope does not change that separate interface.
109
+ - Existing compound-command ASK and Git reset/restore/checkout SNAPSHOT paths
110
+ are outside these new admission counters. Git stash storage can still grow.
111
+ Do not describe this release as a limit on every destructive operation.
112
+ - `status.py --reset-delete-budget` requires an interactive terminal and
113
+ `RESET`, after investigation. It resets only the selected bucket and its
114
+ approvals, without deleting recovery copies or altering capacity/limits.
115
+ Agents must not change identity, remove state or manufacture confirmation
116
+ to bypass a refusal.
117
+ - Accounting uses bounded logical lstat inventory, including directory and
118
+ symlink metadata and conservative per-entry hardlink counts. It is not an
119
+ OS disk quota. Audit/manifest metadata and unrelated writers can still grow
120
+ storage; scan/state bounds may refuse before a larger configured limit.
121
+ - Package/Core changes affect doctor fingerprints. An old baseline may become
122
+ `DRIFTED`; it is not silently replaced, and a new local baseline does not
123
+ prove native-hook interception or model receipt of feedback.
124
+
125
+ Existing installations require an explicit upgrade to acquire these additions.
126
+ Installing a separate copy does not upgrade another existing installation;
127
+ host configuration and hook activation remain separate steps.
128
+ Same-UID, concurrency and uncovered-tool
129
+ limitations remain in the [threat model](https://github.com/mokuyoaxis/agent-guard/blob/0.2.7/docs/design/threat-model.md).
130
+
131
+ <a id="evaluate-the-unpublished-candidate"></a>
132
+
133
+ ## Install or evaluate version 0.2.7
134
+
135
+ After confirming that the exact version is available on both publication
136
+ pages above, install it into a chosen, stable prefix:
137
+
138
+ ```sh
139
+ npm install --prefix /absolute/path/to/agent-guard-install @mokuyoaxis/agent-guard@0.2.7
140
+ ```
141
+
142
+ For source review or before publication is available, use a reviewed checkout
143
+ or a tarball produced and checked from that exact source. An already-built
144
+ local tarball can be installed into a disposable prefix:
145
+
146
+ ```sh
147
+ npm install --offline --ignore-scripts --legacy-peer-deps --no-audit --no-fund \
148
+ --prefix /absolute/path/to/agent-guard-review \
149
+ /absolute/path/to/mokuyoaxis-agent-guard-0.2.7.tgz
150
+ ```
151
+
152
+ The optional MCP SDK remains a separate installation. Compare the selected
153
+ package with the release artifact checksum; local packaging and the version
154
+ string alone do not establish registry availability.
155
+
156
+ ## Validation status
157
+
158
+ **Local 0.2.7-versioned validation passed on 2026-10-29.** The explicit
159
+ 219-file public candidate excluded private experiments. All 1129 Python cases
160
+ and both Node groups passed in 1194.265 seconds, with no failures, errors,
161
+ skips, timeouts or automatic retries. The existing diagnostic collector kept
162
+ `npm test`'s scope and original deadlines; npm itself was not invoked.
163
+
164
+ The 155-file 0.2.7 package passed offline installation, all 12 CLI entry-point
165
+ checks and actual installed stdio deletion, restoration, persistent-budget,
166
+ protection and batch-gate checks. MCP `serverInfo.version` matched package
167
+ version `0.2.7`; read-only tools left the workspace unchanged and forbidden
168
+ override/force/reset/GC-execute arguments were refused. A separate final
169
+ package consistency check verifies documentation-only updates against the
170
+ tested runtime and the final source.
171
+
172
+ Six release-gate tests executed the workflow's actual SDK preflight body:
173
+ missing/wrong/broken SDK and disabled/skipped/empty protocol suites were
174
+ refused. The same body also passed against the existing isolated SDK. The tag
175
+ workflow now installs that pinned SDK and requires enabled protocol coverage
176
+ before its unchanged `npm test` step. These are the **2026-10-29 local
177
+ preparation results**: they did not include final-commit remote CI or
178
+ publication checks and made no new real-model requests. Published artifact
179
+ and workflow results must be checked through the exact version links above.
180
+
181
+ Earlier local source evidence is retained with its original checkpoint:
182
+
183
+ | Checkpoint | Observed result |
184
+ |---|---|
185
+ | Cleanup-only | 1012 Python cases and both Node groups passed continuously in 979.997 seconds; 37 Cleanup/9 manifest checks and a 146-file offline package also passed |
186
+ | Deletion hardening | Three independent runs each passed 1090 Python cases and both Node groups in 1061.017 / 1025.315 / 1042.145 seconds; a 149-file offline package and three real Kimi root-Bash scenarios passed |
187
+ | MCP source, first full run | 1123 Python cases, one observer READY-startup error, no skips; 1156.312 seconds; Node did not start |
188
+ | Same MCP source, second full run | 1123 Python cases and both Node groups passed in 1143.435 seconds, without failures, errors, skips, timeouts or automatic retries |
189
+ | MCP source packaging | 154 files / 12 CLI checks, local offline installation and actual installed stdio deletion/recovery/budget/protection checks passed |
190
+
191
+ These source/package checks used 0.2.6 package metadata before selecting
192
+ version 0.2.7. They are not acceptance of a renamed 0.2.7 tarball. The first MCP
193
+ run's observer error remains unresolved; the unchanged case passed separate
194
+ SDK/system-Python checks in 4.409 / 2.979 seconds. The successful second run
195
+ does not establish a general timeout fix. Both full runs used the existing
196
+ diagnostic result collector with npm test's scope and original deadlines,
197
+ without invoking npm itself.
198
+
199
+ At the earlier 0.2.6-metadata MCP checkpoint, three real Kimi Code 2.3.0
200
+ root-agent native MCP trials passed: normal
201
+ deletion/model-driven restore (27.288 seconds), same-session budget refusal
202
+ and model-driven restore (26.121 seconds), and configured protection
203
+ (16.814 seconds). All 19 configured-route requests returned HTTP 200;
204
+ 16 model-generated MCP calls matched native stdio requests, without Bash,
205
+ fixed replies, automatic trial retries or route changes. Restored bytes and
206
+ user configuration/auth fingerprints matched; restored budget remained
207
+ charged. The existing loopback gateway's server-side model identity was not
208
+ independently authenticated.
209
+
210
+ Local evidence is ARM64/PRoot POSIX, Python 3.13.5 and Node 22.23.4.
211
+ Without the optional SDK, seven real-stdio protocol cases skip; the local
212
+ 0.2.7 full run included that SDK, and the release gate refuses skipped
213
+ protocol coverage. New SDK-backed CI declarations are not
214
+ remote-CI results. Protocol evidence exercised the classic 2025-06-18
215
+ handshake, not every extension/client version. Claude/Cursor/Codex examples
216
+ are documentation guidance; no new live-client, subagent, native Windows,
217
+ macOS or shared-Android-storage acceptance is claimed.
@@ -0,0 +1,275 @@
1
+ # 0.2.7 changes and 0.2.6 maintenance history
2
+
3
+ <a id="unreleased-changes-and-026-maintenance-history"></a>
4
+ <a id="027-candidate-changes-and-026-maintenance-history"></a>
5
+
6
+ The maintainer selected **0.2.7** for Cleanup Copilot, deletion admission and
7
+ optional local MCP tools. Check its exact GitHub release and npm version
8
+ through the [version notes](release-notes-0.2.7.md) before installing; a source
9
+ version alone does not establish publication. This path is retained for
10
+ existing links. At the **2026-10-29 local preparation checkpoint**, versioned
11
+ validation passed:
12
+ 1129 Python cases and both Node groups in 1194.265 seconds, with no failures,
13
+ errors, skips, timeouts or automatic retries, plus a 155-file offline package
14
+ and installed MCP identity/operation checks. The diagnostic collector kept
15
+ `npm test` scope/deadlines without invoking npm. Release SDK-gate fault checks
16
+ also passed; that checkpoint did not include final-commit remote CI or
17
+ publication. These results are separate from the historical checkpoints below; this preparation
18
+ made no new real-model requests. See
19
+ [version scope, upgrade effects and validation](release-notes-0.2.7.md).
20
+ The separate 0.3.0 plan remains paused.
21
+
22
+ <a id="local-mcp-tools-unreleased"></a>
23
+ <a id="local-mcp-tools-027-candidate"></a>
24
+
25
+ ## Local MCP tools (0.2.7)
26
+
27
+ The checkout adds an optional local stdio server for explicit safe_delete,
28
+ ordinary restore, transaction/status queries and GC-plan preview. Workspace
29
+ and stable session identity are set at startup; tools cannot override them,
30
+ the environment or quarantine. Operations use the existing CLI without a
31
+ shell and retain deletion protection, budget, audit and recovery semantics.
32
+ Session selection chooses saved CLI authorization mode as well as budget;
33
+ without it, legacy CLI state and the shared default bucket apply. Reusing
34
+ state requires matching workspace/quarantine/session. Native host-session
35
+ restrictions or in-memory veto require trusted bridging and are not inherited
36
+ merely by registering this server.
37
+ No force restore, GC execution, budget reset or Cleanup approval is exposed;
38
+ safe-delete quarantine targets are also refused. The existing GC CLI remains
39
+ separate; preview-only MCP does not add a terminal requirement to that CLI.
40
+
41
+ The official MIT-licensed `mcp==2.3.0` SDK is an optional separate-environment
42
+ dependency, not a new Core/CLI requirement or automatic npm installation.
43
+ MCP tools do not replace native hooks or cover shell/script/editor actions
44
+ that bypass them. For the 2026-10-28 frozen candidate, the first full local
45
+ run finished 1123 Python cases with one observer READY-startup error in
46
+ 1156.312 seconds; Node did not run. The original error remains unresolved.
47
+ The same case passed separate SDK/system-Python checks, and a second complete
48
+ run passed all 1123 Python cases and both Node groups in 1143.435 seconds,
49
+ without failures, errors, skips, timeouts, runtime changes or automatic retries.
50
+ The diagnostic collector preserved `npm test` scope/deadlines; npm itself was
51
+ not invoked. Default Core testing without the optional SDK skips seven
52
+ protocol cases; the two recorded full runs included it. An independent
53
+ SDK CI job is configured; the local preparation checkpoint included no
54
+ remote execution of that job.
55
+
56
+ The 154-file offline install/12 CLI checks and three real Kimi 2.3.0 native-MCP
57
+ trials passed: ordinary delete/restore, same-session budget and configured
58
+ protection. The model made 16 MCP calls across 19 real configured-route HTTP
59
+ 200 requests, without Bash, fixed replies or route changes. Its gateway's
60
+ server-side model identity was not independently verified. Local evidence
61
+ covers ARM64/PRoot Python 3.13.5; there are no new Windows/macOS/shared-storage
62
+ or live Claude/Cursor/Codex tests. Their setup examples remain documentation
63
+ guidance. See [installation, failure history and limits](../guides/mcp.md).
64
+ Published 0.2.6 and its old evidence remain unchanged; 0.3.0 is still paused.
65
+
66
+ <a id="deletion-admission-hardening-unreleased"></a>
67
+ <a id="deletion-admission-hardening-027-candidate"></a>
68
+
69
+ ## Deletion admission hardening (0.2.7)
70
+
71
+ The current checkout adds quarantine capacity admission, persistent session
72
+ byte/entry budgets, short-window rate and repeated-target-set limits, and
73
+ shared protected paths in optional `.agent-guard/delete-policy.json`.
74
+ Cross-process locking covers measurement, durable admission debit and the
75
+ guarded mutation. Failures and restores do not refund session budget; unnamed
76
+ CLI processes share a default bucket. Configuration/state failures block new
77
+ admission instead of silently disabling limits.
78
+
79
+ Large batches require Cleanup's existing terminal review, followed by a
80
+ ten-minute approval bound to paths, metadata, configuration and session and
81
+ consumed once per selected path. Covered automated large-delete checks BLOCK with
82
+ Cleanup guidance; no new host approval/resume protocol is added. Approval
83
+ does not bypass capacity, budgets or protection. Status adds explicit
84
+ terminal-confirmed reset of the current budget only.
85
+ Existing compound-command ASK and Git snapshots remain outside the new
86
+ budget; normal restore, explicit GC and unprotected quarantine housekeeping
87
+ remain exempt. Configuration/control-path protection still applies.
88
+
89
+ Accounting uses logical `lstat` sizes including directory metadata and
90
+ conservative per-entry hardlink counts, not physical disk quotas. Audits,
91
+ metadata and unrelated writers can still grow storage. GC remains explicit;
92
+ capacity refusal never downgrades to permanent deletion. See
93
+ [defaults, reason codes and recovery](../guides/deletion-limits.md).
94
+
95
+ The 2026-10-28 frozen public runtime passed three independent full runs,
96
+ each with 1090 Python cases and both Node groups: 1061.017, 1025.315 and
97
+ 1042.145 seconds, with no failures, errors, skips, timeouts or automatic retries.
98
+ The existing diagnostic collector retained `npm test` scope/deadlines without
99
+ invoking npm itself. An offline 149-file package and three real Kimi 2.3.0
100
+ root-Bash cases passed; nine configured-route model requests returned HTTP 200.
101
+ See the guide for POSIX-only validation, gateway identity and host/tool limits.
102
+ The earlier unexplained npm timeout did not recur; its history is retained.
103
+ The Cleanup-only results below predate these changes. Those earlier checks
104
+ used 0.2.6 package metadata without claiming the additions shipped in that
105
+ release. Subsequent versioned 0.2.7 tests and package checks passed as recorded
106
+ above; the separate 0.3.0 plan remains paused.
107
+
108
+ <a id="cleanup-copilot-unreleased"></a>
109
+ <a id="cleanup-copilot-027-candidate"></a>
110
+
111
+ ## Cleanup Copilot (0.2.7)
112
+
113
+ The current checkout adds a metadata-only cleanup plan and an explicitly
114
+ confirmed CLI execution workflow. It reports regenerable, caller-declared
115
+ discarded, uncertain and protected targets with logical sizes, reasons and
116
+ projected deletion/quarantine effects. Execution still uses safe_delete;
117
+ ordinary quarantined files retain disk usage. The default plan writes no
118
+ workspace or guard metadata. See [usage and limits](../guides/cleanup-plan.md).
119
+
120
+ This initial addition is separate from published 0.2.6 and is included in
121
+ version 0.2.7. At its initial checkpoint it added no native host tool or
122
+ deletion-policy change. Subsequent admission hardening is described above. At the Cleanup-only
123
+ checkpoint, the runtime passed a continuous local ARM64/PRoot POSIX rerun:
124
+ 1012 Python cases and both Node groups in 979.997 seconds, with no failures,
125
+ errors, skips or retries. This used the existing diagnostic result collector
126
+ with the same test scope and deadlines as `npm test`. The earlier literal
127
+ npm command's timeout remains recorded and unexplained; it did not recur
128
+ in this rerun. Focused cleanup/manifest checks and an offline package also passed,
129
+ including terminal confirmation, physical deletion and quarantine/restore.
130
+ See the guide's [validation scope](../guides/cleanup-plan.md#validation-scope)
131
+ for the local platform and host limits.
132
+
133
+ ## Maintenance delivered in 0.2.6 / 0.2.6 维护说明
134
+
135
+ Updated 2026-10-22. The additions previously tracked here now ship in
136
+ [0.2.6](release-notes-0.2.6.md). This path is retained for existing links and
137
+ the preparation history below. The [0.2.5 notes](release-notes-0.2.5.md) retain
138
+ that release's scope. Existing installations need an upgrade; optional Stop
139
+ also needs explicit configuration and a new Kimi session.
140
+
141
+ ## Availability
142
+
143
+ | Addition | Availability and setup |
144
+ |---|---|
145
+ | Kimi recovery feedback | Included in 0.2.6 as `adapters/kimi-code/stop_feedback.py`; requires an explicitly configured Stop hook. Version 0.2.5 lacks this helper. |
146
+ | Kimi configuration guidance | The current example recommends PreToolUse 120 seconds and optional Stop 30 seconds; merge top-level skill directories separately from TOML hook tables. Existing installations can adjust their PreToolUse timeout independently of Stop. |
147
+ | Kimi Stop doctor checks | Included in 0.2.6; `doctor.py kimi --probe --json` reports optional Stop configuration/local execution in a separate `feedback` object. Version 0.2.5 lacks these checks. |
148
+ | Kimi 2.3.0 Bash profile | Added in 0.2.6 after prompt-CLI and ACP root-Bash trials. Version 0.2.5 keeps its earlier list; the separate Kimi Lab helper stays pinned to 2.1.1. |
149
+ | DSH Lab preflight diagnostics | Included in 0.2.6; 0.2.5 retains the older generic error messages. This concerns the Lab controller's version/config checks, not the production deletion policy. |
150
+ | DSH alpha.4 default deletion adapter | Added in 0.2.6. Exact loader declarations include `0.2.1-alpha.4`; optional native read and Lab keep their two-version scope. Version 0.2.5 retains its earlier declaration. |
151
+
152
+ Use the [installation guide](../guides/getting-started.md) to keep the chosen
153
+ checkout or local-package path consistent. Start a new Kimi session after
154
+ changing hooks. The setup remains opt-in; this page does not change user settings.
155
+
156
+ ## Kimi recovery feedback
157
+
158
+ The sampled Kimi 0.42.0, 2.1.1 and 2.3.0 success-hook paths omit the recovery
159
+ explanation from the next model request. The optional POSIX Stop hook asks
160
+ for one additional response after new compensations. It supplies actual
161
+ transaction IDs, state/restore commands, retained-storage guidance and full
162
+ GC commands. Restoring files moves them back without freeing total disk space.
163
+ The hook itself performs no restore or purge.
164
+
165
+ The initial answer appears first and may be inaccurate. Stop cannot repair
166
+ the earlier tool result; the model may still omit details. Emission cursors
167
+ prevent repeated notices in the tested scope but do not prove model receipt.
168
+ Shared-session actors, cancellation and exhausted budgets retain their limits.
169
+ The local doctor checks described below do not prove optional Stop delivery.
170
+
171
+ See [setup and delivery limits](../../adapters/kimi-code/README.md#optional-recovery-feedback-unreleased-checkout-addition)
172
+ and the [bounded host report](../reports/test-report-kimi-code-block.md).
173
+ Missing/timed-out hooks still allow tools in the sampled hosts. The 120-second
174
+ outer timeout gives the internal 90-second check margin; it does not change
175
+ that host behavior.
176
+
177
+ ## Kimi Stop doctor checks
178
+
179
+ The existing top-level results retain PreToolUse scope. A separate `feedback`
180
+ object distinguishes absent Stop (`NOT_CONFIGURED`), invalid configuration
181
+ (`FAIL`), unreadable configuration (`UNVERIFIED`), and requested local probe
182
+ success/failure. An absent optional Stop does not fail the CLI; a configured
183
+ Stop that fails configuration or a requested probe exits 1.
184
+
185
+ The probe checks synthetic recovery guidance, empty/active-Stop silence and
186
+ repeat suppression in its own temporary home/workspace/trash. Existing audit
187
+ records and cursors are left alone; no model, deletion, restore or GC runs.
188
+ PreToolUse probes also isolate inherited `AGENT_GUARD_*` recovery locations.
189
+ Executable/file presence is checked separately from successful execution.
190
+ `feedback.model_delivery` remains `UNVERIFIED`, even after a Bash live sentinel.
191
+
192
+ Configured Stop fields and helper bytes join drift fingerprints. A Stop
193
+ failure prevents writing a passing baseline or proceeding to the live sentinel.
194
+ The importable `check_kimi()` wrapper remains PreToolUse-only; Claude behavior,
195
+ Core policy and rm wildcard rules are unchanged. See the
196
+ [doctor fields and limits](../../adapters/kimi-code/README.md#stop-doctor-checks-unreleased).
197
+
198
+ ## DSH Lab preflight diagnostics
199
+
200
+ Version/config failures distinguish `START_FAILED`, `TIMEOUT`, `OUTPUT_LIMIT`,
201
+ `NONZERO_EXIT`, `EMPTY_STDOUT` and `UNSUPPORTED_VERSION`. Errors include child
202
+ exit code, capture flags, elapsed/deadline seconds and captured byte counts.
203
+ Configuration text, stderr text, command arguments and environment values are
204
+ omitted. Version/config budgets remain 10/15 seconds, with no automatic retry.
205
+ CLI failure still exits 1. See the [Lab runner guide](../../adapters/dsh/harness/README.md).
206
+
207
+ ## Validation and remaining uncertainty
208
+
209
+ The [0.2.6 release notes](release-notes-0.2.6.md#validation-and-limits) record
210
+ the implementation checkpoint's 13/13 CI result, including ten complete
211
+ Python matrix jobs and both Node groups. The dated local checkpoints below
212
+ remain historical records and do not replace that final implementation check.
213
+
214
+ The later [DSH compatibility work](../design/dsh-compatibility.md) adds alpha.4
215
+ to default deletion support. Real CLI Profile/Boot checks covered all three
216
+ admitted hosts, with scripted root/child-agent, policy-forwarding and approval
217
+ checks on alpha.4. The [report](../reports/test-report-dsh-alpha4.md) records
218
+ that separate checkpoint; the historical full run below predates the new
219
+ manifest/forwarding assertions and does not validate those additions.
220
+
221
+ Before the 0.2.6 version/document alignment, the implementation passed a
222
+ complete frozen run on 2026-10-21: **974 Python tests and both Node groups**,
223
+ no failures, errors or skips, in 1270.573 seconds with the original
224
+ 1800-second deadline and no retry. It used an internal unittest result
225
+ collector for immediate failure/event logs, with the same discovery scope
226
+ and sequential Node stages as `npm test`. The 195 public files stayed frozen.
227
+ That preparation aligned only version metadata, the exact-version assertion
228
+ and documentation; it does not reclassify the older failures below as passes.
229
+
230
+ The earlier DSH diagnostics checkpoint passed one complete `npm test` on 2026-10-21:
231
+ **962 Python tests and both Node groups**, on ARM64/PRoot POSIX. A 138-file
232
+ local package was installed offline at a path containing spaces; its CLI
233
+ reported the controlled child exit code correctly without copying payloads.
234
+ Those counts describe that earlier checkpoint, before the Stop doctor
235
+ additions. A later 139-file offline package checked the doctor candidate;
236
+ neither older artifact is a versioned 0.2.6 release.
237
+
238
+ The earlier complete-test attempts included a timeout and one DSH config
239
+ preflight error. Its original result details were not retained. Five bounded
240
+ repetitions of the failing case and the new complete run passed, but the
241
+ historical cause remains unknown. Controlled faults verified the new
242
+ diagnostics; they are separate from reproducing that historical failure.
243
+
244
+ Later Kimi compatibility work adds exact `2.3.0` to the Bash profile after
245
+ sixteen actual-host fixed-loopback trials: eight prompt CLI and eight ACP,
246
+ including allow, BLOCK, ASK refusal, runtime failure, absence controls,
247
+ quarantine/restore and Stop feedback. ACP hooks ran in the session directory
248
+ despite a different server startup cwd. This postdates the historical full
249
+ run above; it changes the version declaration, not Core or the bridge.
250
+ The [2.3.0 report](../reports/test-report-kimi-code-block.md#kimi-230-acceptance)
251
+ keeps root Bash, client-terminal, timeout, model and subagent limits explicit.
252
+ Updating the profile can make an old baseline `DRIFTED`; no baseline is
253
+ automatically rewritten. The Lab helper remains pinned to 2.1.1.
254
+
255
+ Earlier Kimi fixed loopback trials exercised the actual 0.42.0/2.1.1 CLIs.
256
+ A bounded 2.1.1 real-model session received the recorded transaction and full
257
+ commands; restoration and repeat-Stop checks passed. This does not establish
258
+ all-model, subagent, background or long-running behavior. The new DSH
259
+ diagnostic checks made no external model requests.
260
+
261
+ <a id="中文摘要"></a>
262
+
263
+ ## 0.2.6 中文摘要
264
+
265
+ 以下为 0.2.6 历史维护摘要:Kimi 可选 Stop 恢复反馈、120 秒外层超时接入说明,以及
266
+ DSH Lab 版本/配置预检的原因、退出码和计时诊断,及 Kimi Stop 的独立 doctor 检查。
267
+ 后续默认删除适配加入 DSH `0.2.1-alpha.4`,读取脱敏/Lab 不随之扩大。
268
+ Kimi Bash profile 新增精确版本 2.3.0;CLI/ACP 各八项固定响应试次提供有限根代理证据,
269
+ 未调用外部模型,也未扩大 Kimi Lab 的 2.1.1 准入或子代理声明。
270
+ Stop 未配置不报错;配置或本地探针失败退出 1,模型送达始终未验证。已发布 0.2.5 的范围保持原记录;
271
+ 这些功能自 0.2.6 起提供,Stop 另需显式配置;原页面路径为已有链接保留。
272
+
273
+ 版本/文档对齐前,最终实现检查点的 974 项 Python 与两组 Node 已在同一冻结流程通过;
274
+ 此前 962 项检查点和历史失败分别保留,原失败原因仍未确定。
275
+ 上述 0.2.6 维护未改变删除策略、rm 通配符规则、恢复格式或手动 GC。