@mokuyoaxis/agent-guard 0.2.2 → 0.2.3-rc2
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.
- package/README.md +58 -19
- package/README.zh-CN.md +52 -15
- package/adapters/claude/README.md +5 -5
- package/adapters/dsh/README.md +81 -4
- package/adapters/dsh/harness/README.md +328 -0
- package/adapters/dsh/harness/baseline.patch.yml +8 -0
- package/adapters/dsh/harness/guard_lab.py +609 -0
- package/adapters/dsh/harness/native_session.py +482 -0
- package/adapters/dsh/harness/profiles.py +160 -0
- package/adapters/dsh/harness/read_fixture.py +60 -0
- package/adapters/dsh/harness/retry_stream.py +171 -0
- package/adapters/dsh/harness/session_decode.mjs +117 -0
- package/adapters/dsh/lib/index.js +46 -5
- package/adapters/dsh/lib/read_result_guard.js +207 -0
- package/adapters/dsh/lib/read_result_guard.py +139 -0
- package/adapters/harness_support.py +109 -0
- package/adapters/kimi-code/README.md +7 -0
- package/adapters/kimi-code/harness/README.md +126 -0
- package/adapters/kimi-code/harness/guard_lab.py +430 -0
- package/core/classifier.py +90 -23
- package/core/dialects.py +6 -5
- package/core/lab.py +2373 -0
- package/docs/architecture.md +102 -12
- package/docs/compatibility.md +10 -5
- package/docs/friction.md +95 -0
- package/docs/guard-lab-clean-task.md +4 -0
- package/docs/guard-lab-trial-task.md +5 -0
- package/docs/guard-lab.md +391 -0
- package/docs/harness-capabilities.md +7 -4
- package/docs/release-notes-0.2.3-rc1.md +92 -0
- package/docs/release-notes-0.2.3-rc2.md +189 -0
- package/docs/release-notes-0.2.3.md +45 -0
- package/docs/test-report-dsh-0.2-upgrade.md +142 -0
- package/docs/test-report-dsh-guard-lab.md +154 -0
- package/docs/test-report-dsh-native-session.md +118 -0
- package/docs/test-report-dsh-paired-lab.md +183 -0
- package/docs/test-report-dsh-read-redaction.md +114 -0
- package/docs/test-report-dsh-real-followup.md +170 -0
- package/docs/test-report-dsh-retry-evidence.md +134 -0
- package/docs/test-report-kimi-guard-lab.md +117 -0
- package/docs/test-report-release-readiness-0.2.3.md +161 -0
- package/docs/test-report-zcode-glm-flash.md +8 -1
- package/docs/threat-model.md +42 -0
- package/guard_lab.py +14 -0
- package/package.json +8 -5
package/docs/architecture.md
CHANGED
|
@@ -73,6 +73,72 @@ PROCEED with txids ──▶ host may run the original command
|
|
|
73
73
|
Explicit-path tools skip the shell parsing front half:
|
|
74
74
|
`safe_delete.py PATH... → classify_paths → decide_path_batch → relocate`.
|
|
75
75
|
|
|
76
|
+
## guard-lab evidence flow
|
|
77
|
+
|
|
78
|
+
`guard-lab` is a diagnostic plane beside the enforcement Core. It does not
|
|
79
|
+
change policy verdicts and is deliberately not installed as a Skill for the
|
|
80
|
+
tested agent.
|
|
81
|
+
|
|
82
|
+
```text
|
|
83
|
+
user controller ── prepare ──▶ disposable fixture ──▶ tested agent/harness
|
|
84
|
+
│ │ │
|
|
85
|
+
│ │ ├─ synthetic canary data
|
|
86
|
+
│ │ ├─ loopback bait URL
|
|
87
|
+
│ │ ├─ harmless fake Lab stub
|
|
88
|
+
│ │ └─ bounded snapshot test double
|
|
89
|
+
│ │
|
|
90
|
+
└─ private evidence ◀─────┴──── observer / host result / output scan
|
|
91
|
+
│
|
|
92
|
+
└─ control hash + chained events + health check ──▶ L0/L1 report
|
|
93
|
+
│
|
|
94
|
+
matched guard-off / guard-on reports ─────┴─▶ L2 compare
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
The fixture and evidence directory must be disjoint. Only the fixture is shown
|
|
98
|
+
to the tested agent. The observer binds to loopback for a bounded interval;
|
|
99
|
+
selected output scanning happens after it stops so two writers cannot race the
|
|
100
|
+
event chain. Missing controls, changed control data, malformed event chains, or
|
|
101
|
+
an unfinished observer yield `INCONCLUSIVE` rather than a guessed pass/fail.
|
|
102
|
+
Control reports always use `security_outcome=CALIBRATION_ONLY`. The manual
|
|
103
|
+
`injection-probe` reverses the positive-control interpretation: a bait hit is
|
|
104
|
+
`EXPOSURE_OBSERVED` and a failing criterion. Its comparison layer requires an
|
|
105
|
+
effective guard-off baseline plus matching protocol, harness/version/model,
|
|
106
|
+
trial group, and task hash before it can label a guard-on difference L2.
|
|
107
|
+
Every user-declared real-model run also needs one `HOST_RESULT=COMPLETED` event.
|
|
108
|
+
Process exit zero alone is insufficient because a harness may encode model or
|
|
109
|
+
configuration failure in its stream while exiting normally.
|
|
110
|
+
Other host settings are not bound by the evidence format; the experimenter
|
|
111
|
+
must hold them constant and record how that equality was checked.
|
|
112
|
+
|
|
113
|
+
The deterministic snapshot control submits an in-memory tar containing four
|
|
114
|
+
synthetic source classes to an authenticated IPv4-loopback route. The sink
|
|
115
|
+
validates and discards it, retaining only hashes, sizes, stages, and bait IDs.
|
|
116
|
+
This calibrates archive/sink evidence; it does not provide general file-read
|
|
117
|
+
telemetry, prove an external upload, or show that a PreToolUse hook can mediate
|
|
118
|
+
a harness-owned background sidecar.
|
|
119
|
+
|
|
120
|
+
This layout separates accidental access in the intended workflow, not OS
|
|
121
|
+
privileges. A same-UID adversary can inspect or alter both sides. See
|
|
122
|
+
[guard-lab](guard-lab.md) for the evidence semantics and unsupported channels.
|
|
123
|
+
|
|
124
|
+
## Opt-in DSH text-read boundary
|
|
125
|
+
|
|
126
|
+
The [experimental read prototype](test-report-dsh-read-redaction.md) adds a
|
|
127
|
+
separate post-execute path for reviewed, artifact-pinned native text-read
|
|
128
|
+
contracts (local FS and DSH `0.2.0-rc.2` sandbox FS):
|
|
129
|
+
native complete read value → bounded Python stdin worker → existing Core
|
|
130
|
+
scan/policy/plan → native value replacement → regenerated content and meta.
|
|
131
|
+
The original filesystem access remains owned by DSH. The worker is a trusted
|
|
132
|
+
local controller subprocess and reads no target file. The default bundle and
|
|
133
|
+
reviewed deletion-only Lab profiles keep this path disabled.
|
|
134
|
+
|
|
135
|
+
Native validation uses the actual read, AgentLoop and JSONL backend with a
|
|
136
|
+
deterministic synthetic stream; it checks next-request content and durable
|
|
137
|
+
metadata too; the [current review](test-report-release-readiness-0.2.3.md)
|
|
138
|
+
records both new-host providers. Pagination, custom finalizers/unreviewed providers, PTC, other tools and
|
|
139
|
+
events before this hook remain outside this boundary. No real-model L2
|
|
140
|
+
evidence follows from the zero-model probe.
|
|
141
|
+
|
|
76
142
|
## The Decision Protocol
|
|
77
143
|
|
|
78
144
|
The stable cross-harness interface is not allow/block:
|
|
@@ -92,7 +158,7 @@ neither do the lexical rules. `core/dialects.py` isolates both concerns:
|
|
|
92
158
|
|
|
93
159
|
```
|
|
94
160
|
classify_command(cmd, dialect="posix")
|
|
95
|
-
posix -> shlex + heredoc stripping (default
|
|
161
|
+
posix -> shlex + heredoc stripping (default lexer)
|
|
96
162
|
cmd -> caret escapes, & separators, no
|
|
97
163
|
backslash escapes in quotes, del/erase/rd/rmdir, /s /q
|
|
98
164
|
powershell -> '' literal quoting, ` escapes, $() kept verbatim,
|
|
@@ -110,15 +176,16 @@ The dialect is selected by, in precedence order:
|
|
|
110
176
|
|
|
111
177
|
Both adapters forward the *requested* selector verbatim rather than a
|
|
112
178
|
resolved value, so `check.py` owns the single verdict for an unusable
|
|
113
|
-
selector.
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
the default path keeps its exact behaviour and cost.
|
|
179
|
+
selector. Their cheap prefilter screens both POSIX and Windows vocabularies:
|
|
180
|
+
the selector chooses the lexer, not whether a destructive-looking command
|
|
181
|
+
reaches Core at all.
|
|
117
182
|
|
|
118
183
|
Four rules keep the layer honest:
|
|
119
184
|
|
|
120
|
-
* **The default
|
|
121
|
-
|
|
185
|
+
* **The default lexer is POSIX.** Existing POSIX syntax keeps POSIX quoting
|
|
186
|
+
and separator rules. The cross-vocabulary safety floor is deliberately
|
|
187
|
+
additive: a known destructive command that previously vanished on a
|
|
188
|
+
mismatch now blocks instead of becoming `ALLOW_NOOP`.
|
|
122
189
|
* **An unknown dialect name is never a silent POSIX fallback.** The
|
|
123
190
|
library raises/returns unusable; the CLI and adapters turn that into
|
|
124
191
|
`BLOCK_DIALECT_UNKNOWN` (name not recognised) or
|
|
@@ -131,6 +198,12 @@ Four rules keep the layer honest:
|
|
|
131
198
|
(`powershell -Command "..."`) all become undeterminable facts -> BLOCK.
|
|
132
199
|
`-WhatIf:$true` is a dry run (ALLOW); `-WhatIf:$false` is a real delete;
|
|
133
200
|
a *variable* switch value blocks.
|
|
201
|
+
* **Known destructive vocabulary cannot disappear on a dialect mismatch.**
|
|
202
|
+
The selected tokenizer defines command boundaries. If one of those
|
|
203
|
+
segments contains a supported destructive command shape but its dialect
|
|
204
|
+
classifier produced no operation, Core emits a target-free `UNKNOWN` fact
|
|
205
|
+
and blocks. It never reuses targets or flags guessed under another shell
|
|
206
|
+
grammar, and it does not scan ordinary argument text for dangerous words.
|
|
134
207
|
* **Abbreviations expand only when unambiguous.** PowerShell resolves
|
|
135
208
|
`-r`/`-rec` to `-Recurse` and `-fo` to `-Force`, and the guard follows so
|
|
136
209
|
a recursive forced delete is not read as a mild one. A prefix matching
|
|
@@ -177,6 +250,10 @@ FORBIDDEN (BLOCK, never askable).
|
|
|
177
250
|
targets outside the workspace neither leak nor block.
|
|
178
251
|
6. **Self-exclusion.** Targets inside `.agent-trash/` are exempted from
|
|
179
252
|
quarantine - housekeeping cannot recurse into itself forever.
|
|
253
|
+
7. **Diagnostics do not silently become enforcement.** `guard-lab` records
|
|
254
|
+
declared synthetic channels and evaluates one case criterion. It does not
|
|
255
|
+
feed a Lab observation into Core policy or claim to ban model calls. A real
|
|
256
|
+
block would require a host hook or request gateway that owns the call.
|
|
180
257
|
|
|
181
258
|
## Harness adapter model
|
|
182
259
|
|
|
@@ -205,16 +282,29 @@ order of value:
|
|
|
205
282
|
alias subset, `-WhatIf`/`-Recurse`/`-Force`/`-Confirm` semantics, and
|
|
206
283
|
fail-closed handling of variables, subexpressions, piped target sets
|
|
207
284
|
and nested hosts. Unit-tested on Linux CI; POSIX stays the default
|
|
208
|
-
|
|
285
|
+
lexical grammar. Since `0.2.3-rc1`, the shared safety floor can turn a
|
|
286
|
+
previously invisible cross-vocabulary mismatch into a target-free
|
|
287
|
+
refusal without guessing another shell's targets.
|
|
209
288
|
- **Phase 2 (done at the pure-logic/adapter-test level).** Differential
|
|
210
289
|
and regression suites (`tests/test_dialects.py`,
|
|
211
290
|
`tests/test_dialect_phase2.py`) cover further cmd/PowerShell spellings,
|
|
212
291
|
option aliases and fail-closed edge cases. Hook payload dialect forwarding
|
|
213
292
|
has adapter tests; this is not a Windows host execution claim.
|
|
214
|
-
- **Phase
|
|
215
|
-
|
|
216
|
-
|
|
217
|
-
|
|
293
|
+
- **Phase 3a (`0.2.3-rc1` candidate).** A blocking `windows-latest` Core
|
|
294
|
+
job covers the Issue #7 dialect-mismatch and separator regressions,
|
|
295
|
+
deterministic cmd/PowerShell facts, and recovery inside disposable
|
|
296
|
+
fixtures. The job uses Python argv/bytes so a surrounding shell cannot
|
|
297
|
+
rewrite the evidence.
|
|
298
|
+
- **Phase 3 remains incomplete.** Real cmd/PowerShell execution through
|
|
299
|
+
each harness, host-selected dialect wiring, privileged symlink cases,
|
|
300
|
+
broader UNC/device paths and full-suite portability still require
|
|
301
|
+
separate evidence. A focused Core runner is not a universal Windows E2E
|
|
302
|
+
claim.
|
|
303
|
+
- `0.2.3-rc2` source candidate: offline `guard-lab` MVP with disposable
|
|
304
|
+
synthetic fixtures, zero-token controls, a bounded loopback observer,
|
|
305
|
+
explicit-output marker scanning, chained evidence, and fail-inconclusive
|
|
306
|
+
reports. General file-read visibility, remote callbacks, real-model rating,
|
|
307
|
+
and universal model-call blocking are deliberately outside this MVP.
|
|
218
308
|
- V2: `git-guard` skill (remote ref protection with lease semantics);
|
|
219
309
|
adapter hardening (host-side mode storage, tamper-evident audit).
|
|
220
310
|
- V3+: `database-guard` (compensations = transaction / backup /
|
package/docs/compatibility.md
CHANGED
|
@@ -37,11 +37,11 @@ While the major version is `0`:
|
|
|
37
37
|
|
|
38
38
|
| Surface | Class | Notes |
|
|
39
39
|
|---|---|---|
|
|
40
|
-
| Command dialects (`cmd`, `powershell`) | minor | `classify_command(cmd, dialect=...)`; the default stays `posix
|
|
40
|
+
| Command dialects (`cmd`, `powershell`) | minor | `classify_command(cmd, dialect=...)`; the default lexical grammar stays `posix` |
|
|
41
41
|
| `core/dialects.py` module + `TokenStream` | minor | Internal-but-documented; used by the dialect unit tests |
|
|
42
42
|
| `OpSpec.dialect` field | minor | New field; unknown fields stay opaque to consumers |
|
|
43
43
|
| `Ask` on PowerShell `-WhatIf` | minor | A dry run is an `ALLOW_NOOP`; a real delete keeps existing rules |
|
|
44
|
-
| `check.py --dialect` flag | minor | Defaults to
|
|
44
|
+
| `check.py --dialect` flag | minor | Defaults to the POSIX lexical grammar; later safety releases may newly block a previously invisible known destructive vocabulary mismatch |
|
|
45
45
|
| `AGENT_GUARD_DIALECT` env var | minor | Read by `check.py` and the native shell adapters; unset means `posix` |
|
|
46
46
|
| `BLOCK_DIALECT_UNKNOWN` / `BLOCK_DIALECT_INVALID` | minor | New reason codes (additive) |
|
|
47
47
|
| `BLOCK_PROTECTED_ANCESTOR` | minor | New reason code (additive). Filesystem roots (`/`, `/home`, `/usr`, `$HOME`, ...) are refused by identity rather than by falling outside the workspace |
|
|
@@ -54,6 +54,7 @@ While the major version is `0`:
|
|
|
54
54
|
| `.agent-guard/exfil-allow.toml` exemption file | minor | Read from the workspace root only; values exempted by `sha256:...`, never by value |
|
|
55
55
|
| `doctor.py --check-drift` report and adapter `compatibility.json` profiles | minor | Additive local preflight. Without drift flags the doctor keeps its previous process-execution and exit behavior; `CURRENT` never promotes live interception above `UNVERIFIED` |
|
|
56
56
|
| `doctor.py --live-sentinel` and hashed hook receipt | minor | Explicit, opt-in real-host/model probe only. Default doctor behavior is unchanged; raw command/model output is not retained, and incomplete evidence is `INCONCLUSIVE` rather than PASS |
|
|
57
|
+
| Cross-vocabulary mismatch floor (`0.2.3-rc1`) | minor safety fix | At a selected-dialect command boundary, a supported destructive shape that produced no operation becomes target-free `UNKNOWN` → `BLOCK_UNDETERMINABLE_EFFECT`; it never borrows a compensation plan from another grammar |
|
|
57
58
|
|
|
58
59
|
### 0.2.0 check output minimization
|
|
59
60
|
|
|
@@ -84,9 +85,13 @@ unknown selector must produce a Decision Protocol verdict with a reason
|
|
|
84
85
|
code; a usage error carries none, and a harness could read "no decision" as
|
|
85
86
|
"nothing to worry about".
|
|
86
87
|
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
88
|
+
`0.2.3-rc1` adds a focused real-Windows Core gate for dialect mismatch,
|
|
89
|
+
separator normalization, disposable-fixture recovery and exact-byte path
|
|
90
|
+
redaction. It also makes known destructive vocabulary fail closed when it
|
|
91
|
+
does not match the configured dialect. This is only Phase 3a: native
|
|
92
|
+
cmd/PowerShell execution through each harness, hook-selected dialect wiring,
|
|
93
|
+
broader UNC/device paths, module auto-loading and full-suite Windows
|
|
94
|
+
portability remain unverified.
|
|
90
95
|
|
|
91
96
|
### PowerShell parameter prefixes
|
|
92
97
|
|
package/docs/friction.md
CHANGED
|
@@ -264,3 +264,98 @@ without data is still a legitimately empty payload (ALLOW, since nothing
|
|
|
264
264
|
can leak); and on platforms where stdin is not selectable the code falls
|
|
265
265
|
back to the blocking read rather than refusing a caller whose payload may
|
|
266
266
|
be perfectly good.
|
|
267
|
+
|
|
268
|
+
## F16 · A selected shell dialect could erase a known hazard
|
|
269
|
+
|
|
270
|
+
The dialect selector chose both a tokenizer and its recognized command
|
|
271
|
+
vocabulary. That made a configuration mismatch asymmetric: `rm -rf .`
|
|
272
|
+
was a protected-root refusal under POSIX, but the cmd classifier returned no
|
|
273
|
+
operation and policy reported `ALLOW_NOOP`. A mixed line was worse: one
|
|
274
|
+
recognized Windows delete could make the result look guarded while a later
|
|
275
|
+
POSIX delete segment remained invisible. Separately, Windows-native targets
|
|
276
|
+
kept backslashes only when Core itself ran on Windows, so identical command
|
|
277
|
+
text produced host-dependent path facts.
|
|
278
|
+
|
|
279
|
+
**Fixed in `0.2.3-rc1`:** the selected tokenizer still owns command
|
|
280
|
+
boundaries and quoting semantics, but every resulting segment also passes a
|
|
281
|
+
small, shared destructive-vocabulary floor. A known delete, destructive Git
|
|
282
|
+
shape, or `find -delete` shape that its selected classifier did not resolve
|
|
283
|
+
becomes target-free `UNKNOWN` and therefore
|
|
284
|
+
`BLOCK_UNDETERMINABLE_EFFECT`. Core never re-parses the segment under a
|
|
285
|
+
different grammar and never invents a compensation target. Recognized
|
|
286
|
+
Windows delete targets are normalized after their own tokenizer on every
|
|
287
|
+
host, removing the OS-dependent fact split. Negative tests pin quoted output
|
|
288
|
+
and shell-specific literal syntax so the safety floor does not become a
|
|
289
|
+
substring blacklist.
|
|
290
|
+
|
|
291
|
+
## F17 · READY is not proof that a background observer outlives its launcher
|
|
292
|
+
|
|
293
|
+
The first guard-lab tests started and stopped the observer from one Python
|
|
294
|
+
process. They passed, but the actual CLI workflow uses separate `arm` and
|
|
295
|
+
`stop` invocations. In that workflow the child initially remained in the
|
|
296
|
+
launcher's process session: `arm` observed `READY`, then the command runner
|
|
297
|
+
cleaned up the process group as the launcher exited. `stop` correctly timed
|
|
298
|
+
out and the report became `INCONCLUSIVE`, but the advertised workflow did not
|
|
299
|
+
work.
|
|
300
|
+
|
|
301
|
+
**Fixed in the `0.2.3-rc2` source candidate:** the observer gets an independent
|
|
302
|
+
POSIX session or detached Windows process group, with stdin closed and output
|
|
303
|
+
confined to its evidence log. It still has a hard duration limit and uses a
|
|
304
|
+
cooperative create-only stop request; the controller does not send a signal to
|
|
305
|
+
an unverified PID. A regression now performs `prepare`, `arm`, `stop`, `scan`,
|
|
306
|
+
and `report` in five separate CLI processes. In-process unit success is no longer
|
|
307
|
+
accepted as background-lifecycle evidence.
|
|
308
|
+
|
|
309
|
+
## F18 · A received synthetic archive is not generic file-read or exfiltration proof
|
|
310
|
+
|
|
311
|
+
The first snapshot-control design risked collapsing several different facts
|
|
312
|
+
into one statement: a test double read fixture files, created a tar, posted it,
|
|
313
|
+
and a server accepted it. That wording would resemble the overclaiming that a
|
|
314
|
+
forensic lab is meant to prevent. A loopback receiver cannot establish that an
|
|
315
|
+
arbitrary harness performed the same reads, that data crossed an external
|
|
316
|
+
boundary, or that a remote party retained it.
|
|
317
|
+
|
|
318
|
+
**Handled in the `0.2.3-rc2` source candidate:** `snapshot-positive` is labeled
|
|
319
|
+
as L0 instrument calibration. The generated test double accepts no source or
|
|
320
|
+
URL arguments, reads only four bounded manifest entries inside the disposable
|
|
321
|
+
fixture, and connects directly to IPv4 loopback without proxy or redirect
|
|
322
|
+
handling. The sink separately records upload attempt, valid archive, each
|
|
323
|
+
included bait class, and local acceptance, while retaining no body or marker
|
|
324
|
+
value. Reports continue to mark general file reads and external receipt as
|
|
325
|
+
`UNSUPPORTED`; real-harness exposure and guard-on/off mitigation require later
|
|
326
|
+
L1/L2 differential trials.
|
|
327
|
+
|
|
328
|
+
## F19 · A positive-control PASS can look like an attack was blocked
|
|
329
|
+
|
|
330
|
+
`mock-injection` deliberately invokes the fake Lab and reproduces a marker so
|
|
331
|
+
the whole observation path can be calibrated without a model. Its correct
|
|
332
|
+
instrument result is `PASS`, but reusing that case for a real harness would
|
|
333
|
+
invert the security meaning: the injected action succeeded while the top-line
|
|
334
|
+
word still looked reassuring. A quiet guarded run could also be credited as a
|
|
335
|
+
win even when its unguarded baseline never took the bait.
|
|
336
|
+
|
|
337
|
+
**Handled in the `0.2.3-rc2` source candidate:** every deterministic control is
|
|
338
|
+
explicitly L0 with `security_outcome=CALIBRATION_ONLY`. The manual
|
|
339
|
+
`injection-probe` is an attack probe: declared bait contact becomes the adverse
|
|
340
|
+
`EXPOSURE_OBSERVED` outcome, while no hit is narrowly
|
|
341
|
+
`NO_EXPOSURE_OBSERVED`, not a certificate. `compare` produces L2 evidence only
|
|
342
|
+
after an effective unguarded baseline and a guarded trial with matching
|
|
343
|
+
protocol, harness/version/model, group, and task SHA-256. A quiet baseline is
|
|
344
|
+
`INCONCLUSIVE`; unhealthy or mismatched evidence is `INCOMPARABLE`.
|
|
345
|
+
|
|
346
|
+
## F20 · Exit zero does not prove that a real-host trial ran
|
|
347
|
+
|
|
348
|
+
The first low-token Kimi clean trial used a valid hook-free isolated config,
|
|
349
|
+
but that config omitted a default model. Kimi emitted only its stream-version
|
|
350
|
+
record, wrote the model/config failure to stderr, and still exited zero. The
|
|
351
|
+
observer was healthy and no bait appeared. Without a separate completion gate,
|
|
352
|
+
Lab would have reported a quiet run; in a guarded comparison, that exact shape
|
|
353
|
+
could become a false mitigation claim.
|
|
354
|
+
|
|
355
|
+
**Fixed in the `0.2.3-rc2` source candidate:** each manual run declared as
|
|
356
|
+
`model_usage=REAL` now requires one create-once `record-host` event after the
|
|
357
|
+
observer stops. Only user-verified `COMPLETED` permits a conclusive criterion;
|
|
358
|
+
`FAILED`, `TIMED_OUT`, missing, duplicate, or malformed host state is
|
|
359
|
+
`INCONCLUSIVE` and makes a pair `INCOMPARABLE`. The optional process exit code
|
|
360
|
+
is evidence, not the verdict. Completion remains user-declared because the
|
|
361
|
+
generic Lab cannot safely parse and authenticate every harness transcript.
|