feat(6243): move_path carries a moved path's snippets with its shapes
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 17s
CI & Build / TypeScript typecheck (push) Successful in 54s
CI & Build / integration (push) Successful in 1m9s
CI & Build / Python tests (push) Successful in 2m12s
CI & Build / Build & push image (push) Successful in 31s
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 17s
CI & Build / TypeScript typecheck (push) Successful in 54s
CI & Build / integration (push) Successful in 1m9s
CI & Build / Python tests (push) Successful in 2m12s
CI & Build / Build & push image (push) Successful in 31s
Snippet locations are keyed by path too, so a snippet recorded under a moved directory reads `missing` at its next check. The tool is now move_path(project_id, from_path, to_path). It moves the ledger rows as before, and re-paths the project's snippet locations under from_path through update_snippet, so each body and its indexed mirror stay one record. A snippet the caller can only read is listed in snippets_read_only. The tool refuses only when nothing at all is recorded under from_path. The path test is the one snippets already uses (_path_touches), and the plugin version is minted for the skill edit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "grimoire",
|
||||
"description": "Grimoire for Claude Code: connects the grimoire MCP server, adds the hooks that deliver live project state and relevant records at the right moment, ships the shared client-neutral Grimoire skills (using-grimoire, writing-plans, reporting-back, systematic-debugging, verification, brainstorming, reusing-code, shape-accounting, family-canon), and syncs your saved Grimoire Processes as skills (/grimoire:sync).",
|
||||
"version": "2026.10.21.2344",
|
||||
"version": "2026.10.22.1907",
|
||||
"author": {
|
||||
"name": "Bryan Van Deusen"
|
||||
},
|
||||
|
||||
@@ -42,8 +42,9 @@ row carries a status:
|
||||
detail cannot be sorted, queried, or diffed.
|
||||
|
||||
Rows are keyed by repo and path, so a move in the tree is a move in the
|
||||
ledger. When a file or directory moves, run `move_shapes(project_id,
|
||||
from_path, to_path)` before the next refresh. For a repo renamed on its
|
||||
ledger. When a file or directory moves, run `move_path(project_id,
|
||||
from_path, to_path)` before the next refresh; it carries the snippets
|
||||
recorded there too. For a repo renamed on its
|
||||
forge, run `bind_repo(new_url, project_id, moved_from=old_url)`. Otherwise
|
||||
the refresh marks every judged row vanished and lists the same shapes again,
|
||||
unjudged.
|
||||
|
||||
Reference in New Issue
Block a user