Skip to content

fix(mcp): prune cached projects with missing roots - #2100

Open
lorenzozanee wants to merge 2 commits into
DeusData:mainfrom
lorenzozanee:fix/prune-inactive-projects
Open

fix(mcp): prune cached projects with missing roots#2100
lorenzozanee wants to merge 2 commits into
DeusData:mainfrom
lorenzozanee:fix/prune-inactive-projects

Conversation

@lorenzozanee

Copy link
Copy Markdown

What does this PR do?

Cached project indexes from disconnected sessions remain after their worktrees disappear because they are no longer registered with the watcher. This adds a dry-run-by-default prune_projects MCP tool that identifies confirmed missing roots and removes the database and sidecars only after coordination.

Closes #1431

Checklist

  • Every commit is signed off (git commit -s) — required, CI rejects
    unsigned commits (DCO, see CONTRIBUTING.md)
  • Tests pass locally (make -f Makefile.cbm test)
  • Lint passes (make -f Makefile.cbm lint-ci)
  • New behavior is covered by a test (reproduce-first for bug fixes)

Signed-off-by: lorenzozanee <wyz0707@proton.me>
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown

Thanks for opening this — it has been seen, and it is queued.

This note is automated, but it is not a brush-off: it exists so you know where your PR stands instead of having to guess from silence.

Current review status: working through a backlog. 0.9.1-rc.1 is out, so the release freeze that held reviews is over — but it left a large queue of open pull requests behind it, and we are reading through them oldest-first. The background is in discussion #1144.

What that means for this PR, concretely:

  • It will not be closed for inactivity. No stale bot touches pull requests here.
  • It may still sit a while before a human reads it. That is on us, not on you.
  • Older PRs are read first, so a recent one is not being skipped — it is behind a queue.

Things that will genuinely speed it up whenever review does happen:

  • Keep it rebased on main — the tree is moving quickly right now, and a conflicting branch cannot be reviewed as the diff you intended.
  • Get CI green, or say which failures you believe are pre-existing.
  • Keep the change to one claim. Bundled features and refactors get split before they get merged, which costs you a round trip.
  • Every commit needs a sign-off (git commit -s) — CI enforces DCO.

If this fixes a bug, a reproduction we can run is worth more than a description of the symptom.

Thanks for contributing, and sorry in advance for the wait.

Signed-off-by: lorenzozanee <wyz0707@proton.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stale project indexes from inactive sessions are never pruned

1 participant