From a5ad761f5f5e2eb9809ff16f0dc3646585476290 Mon Sep 17 00:00:00 2001 From: garrytan Date: Sat, 31 Oct 2026 20:30:08 +0000 Subject: [PATCH] docs(freeze): describe full-path resolution and fail-closed cases (#3623) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- freeze/SKILL.md | 8 +++++--- freeze/SKILL.md.tmpl | 8 +++++--- 2 files changed, 10 insertions(+), 6 deletions(-) diff --git a/freeze/SKILL.md b/freeze/SKILL.md index 02f85237b..39230fbb5 100644 --- a/freeze/SKILL.md +++ b/freeze/SKILL.md @@ -76,9 +76,11 @@ operation (nested under `hookSpecificOutput` — Claude Code ignores a top-level Polarity is fail-closed: a tool payload the hook cannot parse is DENIED, not allowed — a boundary that fails open is not a boundary. A payload that parses but has neither path field (a non-file tool) is allowed. A deny names the -tool, the path field, the boundary and `/unfreeze`. Symlinks are resolved -through their FINAL component, so an in-boundary symlink pointing outside the -boundary is checked against its target. +tool, the path field, the boundary and `/unfreeze`. The path is resolved before +the check: `~`, `..` and relative paths, and symlinks at every depth, even +through folders that do not exist yet. A path the hook cannot place (a symlink +loop, a line break, a Windows drive-relative path, over 4096 characters) is +denied. The freeze boundary persists until explicitly removed via the state file. The hook script reads it on every Edit/Write/NotebookEdit invocation. Boundaries containing spaces diff --git a/freeze/SKILL.md.tmpl b/freeze/SKILL.md.tmpl index 4b95fd3e4..6f2f9847e 100644 --- a/freeze/SKILL.md.tmpl +++ b/freeze/SKILL.md.tmpl @@ -80,9 +80,11 @@ operation (nested under `hookSpecificOutput` — Claude Code ignores a top-level Polarity is fail-closed: a tool payload the hook cannot parse is DENIED, not allowed — a boundary that fails open is not a boundary. A payload that parses but has neither path field (a non-file tool) is allowed. A deny names the -tool, the path field, the boundary and `/unfreeze`. Symlinks are resolved -through their FINAL component, so an in-boundary symlink pointing outside the -boundary is checked against its target. +tool, the path field, the boundary and `/unfreeze`. The path is resolved before +the check: `~`, `..` and relative paths, and symlinks at every depth, even +through folders that do not exist yet. A path the hook cannot place (a symlink +loop, a line break, a Windows drive-relative path, over 4096 characters) is +denied. The freeze boundary persists until explicitly removed via the state file. The hook script reads it on every Edit/Write/NotebookEdit invocation. Boundaries containing spaces