Restore rolls back to a backup; a session can only file issues in another project #220

Merged
bvandeusen merged 15 commits from dev into main 2026-11-05 09:29:55 -05:00
2 changed files with 7 additions and 11 deletions
Showing only changes of commit 49b5ceee41 - Show all commits
+1 -1
View File
@@ -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.11.05.0252",
"version": "2026.11.05.0301",
"author": {
"name": "Bryan Van Deusen"
},
+6 -10
View File
@@ -277,16 +277,12 @@ bound — confine the session to it:
- **Pass that `project_id` to every read** (`search`, `list_tasks`,
`list_notes`). An unscoped read bleeds every other project's work into your
context.
- **Only reference or offer work on the in-scope project.** Don't surface,
suggest, or start work on other projects unless the operator explicitly widens
scope.
- **Toward another project, the one change to make is filing an issue**:
`create_task(project_id=<theirs>, kind="issue")`, carrying how you found it
and the evidence. Editing its files, committing or pushing in its repo, and
changing its other records are the operator's call, and the plugin asks them
before any of those runs. Reading anything there is fine.
- If the work itself belongs to a *different* project, say so and **ask before
switching** — never silently operate cross-project.
- **Only reference or offer work on the in-scope project**, unless the
operator explicitly widens scope; work that belongs elsewhere, say so and ask.
- **Cross-project, the one change to make is filing an issue**:
`create_task(project_id=<theirs>, kind="issue")` with how you found it and the
evidence. Reading there is fine; editing its files, committing or pushing in
its repo, or changing its records is the operator's call, and the plugin asks.
## Read these when the moment comes