@guilz-dev/belay 0.9.2 → 0.9.3

package/dist/version.js

@@ -1,2 +1,2 @@
 // Generated by scripts/sync-version.mjs — do not edit.
-export const PACKAGE_VERSION = '0.9.2';
+export const PACKAGE_VERSION = '0.9.3';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@guilz-dev/belay",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "description": "Belay-style approval and audit gating for agent runtimes.",
   "type": "module",
   "license": "MIT",
@@ -57,10 +57,13 @@
     "typecheck": "tsc --noEmit",
     "test": "pnpm build && vitest run",
     "test:structural": "pnpm build && vitest run src/__tests__/verdict/structural-suite.test.ts",
-    "test:docker": "pnpm build && vitest run src/__tests__/capability/boundary-container-isolation.test.ts src/__tests__/capability/boundary-driver-container.test.ts",
+    "test:docker": "pnpm build && vitest run --config vitest.live.config.ts src/__tests__/capability/boundary-container-isolation.test.ts src/__tests__/capability/boundary-container-workspace-mount.test.ts src/__tests__/capability/boundary-driver-container.test.ts src/__tests__/contained-execution-docker.integration.test.ts",
+    "test:llm": "pnpm build && vitest run --config vitest.live.config.ts src/__tests__/verdict/llm/judge-accuracy.test.ts",
     "test:stable": "pnpm build && vitest run && vitest run && vitest run",
     "corpus": "pnpm build && node scripts/corpus.mjs",
     "probe:adversarial": "pnpm build && node scripts/adversarial-probe.mjs",
+    "probe:cursor-shell-rewrite": "node scripts/cursor-shell-rewrite-probe.mjs",
+    "probe:native-seatbelt-boundary": "node scripts/native-seatbelt-boundary-probe.mjs --live",
     "probe:coverage": "pnpm build && node scripts/coverage-probe.mjs",
     "probe:coverage:repeat": "pnpm build && node scripts/coverage-probe.mjs --repeat 3",
     "corpus:ratchet": "pnpm build && node scripts/corpus-ratchet.mjs"

package/skills/belay/SKILL.md

@@ -54,6 +54,11 @@ To restore the legacy two-step UX (approve, then always retry manually), set
 For why it was blocked, use `/belay why <command>` or `belay explain --command "<command>"`.
 For the latest pending ask, use `/belay explain` or `belay explain`.
 
+If `belay status` or `belay report` shows `Host denied after Belay allow`, the denial came from
+the editor/agent host after Belay returned allow. There is no Belay approval ID to approve. Keep
+host protection in Belay audit mode and approve only the exact host prompt when execution is
+intended.
+
 **Do not use command allowlists** (`overrides.allow`) or legacy standing-allow records
 (shell, tool, or subagent) to fix blocks; none of them change runtime authorization.
 Improve EffectPlan semantics, approve once with `/belay-approve`, or use an exact

package/skills/belay/belay-report.md

@@ -1,7 +1,10 @@
-Show audit visibility: ask/flag/allow counts, silent-pass rate, and recent asks.
+Show audit visibility: ask/flag/allow counts, silent-pass rate, recent asks, and host
+`permission_denied` failures correlated to a preceding Belay allow.
 
 ```bash
 belay report
 ```
 
 For full install health plus audit summary, use `belay status`.
+
+`Host denied after Belay allow` is host-policy telemetry, not a pending Belay approval.