Project folder boundary promoted to enforced security control

easterbrooka is treating the project folder as an enforced isolation boundary. For a legal-AI tool where each matter holds privileged documents, a UI grouping alone is not enough.

The branch name is the clearest signal: claude/security-project-folder-boundary. The PR body was left blank and only a single commit landed, so there's no diff-level detail to read - but the intent is explicit in the naming. Project scope is being promoted from an organisational convention to an enforced constraint.

In practice, hardening this boundary means closing three classes of escape: path-traversal bugs that let a file read or write land outside the active project directory, cross-project leakage when multiple matters are open simultaneously, and any tool-invocation path that could accidentally touch a sibling folder belonging to a different client.

easterbrooka merged this into their own fork's main seconds after opening it. That's consistent with landing in-progress work on a personal line rather than soliciting review - the code exists, the intent is clear, and the author moved on.