willchen96 stops documents from wandering into the wrong matter

A boundary check now makes sure a folder actually belongs to the project before anyone moves, deletes, or reassigns inside it.

securityknowledge-management

Mike lets you organise documents into folders inside a project. Until now, the actions that rearrange that structure - moving a folder, deleting one, or reassigning a document - didn't confirm the folder you named was really part of the project you named. If folder IDs happened to collide across projects, a request could quietly act on the wrong one, and a document could end up detached from the wrong matter.

The fix is small but pointed: every one of those actions now verifies the folder lives in the referenced project first, and refuses cleanly if it doesn't. A request pointing at a folder in someone else's project, or at nothing at all, gets turned away instead of silently proceeding on bad data.

So what Anyone running multiple matters in one Mike instance should care - this is the kind of quiet cross-matter mix-up that's hard to notice and embarrassing to explain.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from willchen96/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
7062a300 fix project folder boundary checks Eli Fayerman 2026-05-04 ↗ GitHub
e5a3d6f2 Merge pull request #28 from fayerman-source/codex/validate-project-folders cosimoastrada 2026-05-08 ↗ GitHub
fix(projects): validate folder ownership before folder mutations

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-480.md from inside the repo you want the changes in.

⬇ Download capture-thread-480.md