pullfrog 0.1.82 → 0.1.83

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.
@@ -59,16 +59,16 @@ export declare function buildClaudePretoolGateSource(deniedTools: readonly strin
59
59
  * settings JSON file or a JSON string`), but we use a path so the script
60
60
  * and its config sit side-by-side under `ctx.tmpdir`.
61
61
  *
62
- * `execToolDenyRules` are the native exec tools (Bash/Monitor/REPL/Workflow +
63
- * their `Agent(...)` forms) to deny at a settings-source rule — the
64
- * authoritative, bypass-immune layer. `--disallowedTools` alone (a `cliArg`
65
- * deny) was observed to leak under `--dangerously-skip-permissions`, so the
66
- * deny is carried here too. The single consumer is `buildClaudeSettings`, which
62
+ * `denyRules` are the native tools to deny (`CLAUDE_DENIED_TOOLS` + their
63
+ * `Agent(...)` forms) at a settings-source rule — the authoritative,
64
+ * bypass-immune layer. `--disallowedTools` alone (a `cliArg` deny) was observed
65
+ * to leak under `--dangerously-skip-permissions`, so the deny is carried here
66
+ * too. The single consumer is `buildClaudeSettings`, which
67
67
  * spreads `hooks` and folds `permissions.deny` into its richer deny list; that
68
68
  * one object is then written to BOTH the `--settings` flag and the `/etc`
69
69
  * managed file, which is what keeps the two surfaces from drifting (#1179).
70
70
  */
71
- export declare function buildClaudePretoolGateSettings(scriptAbsolutePath: string, execToolDenyRules: string[]): {
71
+ export declare function buildClaudePretoolGateSettings(scriptAbsolutePath: string, denyRules: string[]): {
72
72
  hooks: {
73
73
  PreToolUse: Array<{
74
74
  matcher: string;