cribsheet 0.21.0.dev3__tar.gz → 0.21.0.dev4__tar.gz

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "cribsheet",
       "source": "./plugins/claude",
       "description": "Persistent markdown memory + a code symbol index (concept/name lookup, call graph, references, learnings) for your AI. Registers the crib MCP server via sharedserver and keeps one warm crib shared across sessions, carries the reach-for-crib instructions, and ships the `/crib` command. Set MCP_COMBINER=1 (or MCP_COMBINER_SERVES_CRIBSHEET) when a combiner already serves crib and it will not register a second copy.",
-      "version": "0.21.0-dev3"
+      "version": "0.21.0-dev4"
     }
   ]
 }

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/CLAUDE.md.example

@@ -146,8 +146,20 @@ passage re-checks exactly what was drawn from it. Extracted decisions land
 `proposed`: they gate work and taint nothing until a human confirms them with
 `design_promote`.
 
-<!-- Project selection for *reads*: code tools act on ONE current project — set it once
-     with `use_project <name>`, or it's inferred from `project_path` on your first code
-     call; reads then need no project args. To read a *different* project you must name it
-     (`project=` / `project_path=`). `project_path` means "which repo I mean" — it is not
-     your shell cwd. -->
+### Project selection for *reads*: name it — every call, never wrong
+
+**Pass `project=<name>` or `project_path=<a path in that repo>` on every read.** Naming
+a project is never wrong, costs nothing, and can't re-home or leak anything: a named
+selector always decides that call, naming a different one changes nothing, and
+`project_path` means "which repo I mean" — not your shell cwd.
+
+**A read with NO project doesn't guess — it may ask or refuse.** If the call is
+unanchored, crib ASKS the user which project to use (a real question, answer it with a
+project name or a repo path — never a placeholder), or refuses with a one-pass
+recovery asking you to name it. Expect that; don't pass `default` to dodge it.
+
+`use_project <name>` (MCP: `project_use`) is optional today and on its way out: it sets
+a per-connection current project so selector-less reads keep working — but the
+convenience does not survive a daemon restart, and a 2026 (stateless) connection never
+has one at all, so the named project is the call. Treat **"name it every call" as the
+rule now**; keep naming it when it matters even if you also used `use_project`.

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: cribsheet
-Version: 0.21.0-dev3
+Version: 0.21.0-dev4
 Summary: Local MCP server: markdown memory with a Chroma embedding index
 Requires-Python: >=3.13
 Requires-Dist: chromadb>=0.5

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/plugins/claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "cribsheet",
-  "version": "0.21.0-dev3",
+  "version": "0.21.0-dev4",
   "description": "Persistent markdown memory + a code symbol index (concept/name lookup, call graph, references, durable learnings) for your AI. Registers the crib MCP server over a sharedserver-managed HTTP backend (one warm crib shared across sessions) and keeps it warm, injects the reach-for-crib instructions, and ships the `/crib` command (recall memory + code index for a topic). Set MCP_COMBINER=1 when a combiner already serves crib and the plugin will not register it — see docs/plugin-mcp-registration.md.",
   "author": {
     "name": "George Harker",

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/plugins/claude/instructions.txt

@@ -146,8 +146,20 @@ passage re-checks exactly what was drawn from it. Extracted decisions land
 `proposed`: they gate work and taint nothing until a human confirms them with
 `design_promote`.
 
-<!-- Project selection for *reads*: code tools act on ONE current project — set it once
-     with `use_project <name>`, or it's inferred from `project_path` on your first code
-     call; reads then need no project args. To read a *different* project you must name it
-     (`project=` / `project_path=`). `project_path` means "which repo I mean" — it is not
-     your shell cwd. -->
+### Project selection for *reads*: name it — every call, never wrong
+
+**Pass `project=<name>` or `project_path=<a path in that repo>` on every read.** Naming
+a project is never wrong, costs nothing, and can't re-home or leak anything: a named
+selector always decides that call, naming a different one changes nothing, and
+`project_path` means "which repo I mean" — not your shell cwd.
+
+**A read with NO project doesn't guess — it may ask or refuse.** If the call is
+unanchored, crib ASKS the user which project to use (a real question, answer it with a
+project name or a repo path — never a placeholder), or refuses with a one-pass
+recovery asking you to name it. Expect that; don't pass `default` to dodge it.
+
+`use_project <name>` (MCP: `project_use`) is optional today and on its way out: it sets
+a per-connection current project so selector-less reads keep working — but the
+convenience does not survive a daemon restart, and a 2026 (stateless) connection never
+has one at all, so the named project is the call. Treat **"name it every call" as the
+rule now**; keep naming it when it matters even if you also used `use_project`.

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/plugins/opencode/instructions.txt

@@ -146,8 +146,20 @@ passage re-checks exactly what was drawn from it. Extracted decisions land
 `proposed`: they gate work and taint nothing until a human confirms them with
 `design_promote`.
 
-<!-- Project selection for *reads*: code tools act on ONE current project — set it once
-     with `use_project <name>`, or it's inferred from `project_path` on your first code
-     call; reads then need no project args. To read a *different* project you must name it
-     (`project=` / `project_path=`). `project_path` means "which repo I mean" — it is not
-     your shell cwd. -->
+### Project selection for *reads*: name it — every call, never wrong
+
+**Pass `project=<name>` or `project_path=<a path in that repo>` on every read.** Naming
+a project is never wrong, costs nothing, and can't re-home or leak anything: a named
+selector always decides that call, naming a different one changes nothing, and
+`project_path` means "which repo I mean" — not your shell cwd.
+
+**A read with NO project doesn't guess — it may ask or refuse.** If the call is
+unanchored, crib ASKS the user which project to use (a real question, answer it with a
+project name or a repo path — never a placeholder), or refuses with a one-pass
+recovery asking you to name it. Expect that; don't pass `default` to dodge it.
+
+`use_project <name>` (MCP: `project_use`) is optional today and on its way out: it sets
+a per-connection current project so selector-less reads keep working — but the
+convenience does not survive a daemon restart, and a 2026 (stateless) connection never
+has one at all, so the named project is the call. Treat **"name it every call" as the
+rule now**; keep naming it when it matters even if you also used `use_project`.

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/plugins/opencode/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@geohar/opencode-cribsheet",
-    "version": "0.21.0-dev3",
+    "version": "0.21.0-dev4",
     "description": "OpenCode plugin: run the crib (cribsheet) memory + code-index MCP server via sharedserver, register its endpoint, inject the reach-for-crib directive, and ship the /crib command. Stands down when a combiner already serves crib.",
     "type": "module",
     "main": "dist/index.js",

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/plugins/pi/instructions.txt

@@ -146,8 +146,20 @@ passage re-checks exactly what was drawn from it. Extracted decisions land
 `proposed`: they gate work and taint nothing until a human confirms them with
 `design_promote`.
 
-<!-- Project selection for *reads*: code tools act on ONE current project — set it once
-     with `use_project <name>`, or it's inferred from `project_path` on your first code
-     call; reads then need no project args. To read a *different* project you must name it
-     (`project=` / `project_path=`). `project_path` means "which repo I mean" — it is not
-     your shell cwd. -->
+### Project selection for *reads*: name it — every call, never wrong
+
+**Pass `project=<name>` or `project_path=<a path in that repo>` on every read.** Naming
+a project is never wrong, costs nothing, and can't re-home or leak anything: a named
+selector always decides that call, naming a different one changes nothing, and
+`project_path` means "which repo I mean" — not your shell cwd.
+
+**A read with NO project doesn't guess — it may ask or refuse.** If the call is
+unanchored, crib ASKS the user which project to use (a real question, answer it with a
+project name or a repo path — never a placeholder), or refuses with a one-pass
+recovery asking you to name it. Expect that; don't pass `default` to dodge it.
+
+`use_project <name>` (MCP: `project_use`) is optional today and on its way out: it sets
+a per-connection current project so selector-less reads keep working — but the
+convenience does not survive a daemon restart, and a 2026 (stateless) connection never
+has one at all, so the named project is the call. Treat **"name it every call" as the
+rule now**; keep naming it when it matters even if you also used `use_project`.

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/plugins/pi/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@geohar/pi-cribsheet",
-    "version": "0.21.0-dev3",
+    "version": "0.21.0-dev4",
     "description": "Pi extension: run the crib (cribsheet) memory + code-index MCP server via sharedserver, inject the reach-for-crib directive, and ship the /crib recall command. Pairs with pi-mcp-adapter.",
     "type": "module",
     "main": "dist/index.js",

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "cribsheet"
-version = "0.21.0-dev3"
+version = "0.21.0-dev4"
 description = "Local MCP server: markdown memory with a Chroma embedding index"
 readme = "README.md"
 requires-python = ">=3.13"

cribsheet-0.21.0.dev4/tests/test_plugin_instructions.py

@@ -0,0 +1,40 @@
+"""The plugin instructions are COPIES of CLAUDE.md.example, never symlinks —
+and never drifted ones.
+
+Why the copy rule is load-bearing (mcp-companion 0.10.x): marketplace installs
+and npm packs copy the plugin subtree out of the repo into a cache with no repo
+root, and neither reliably preserves symlinks — a relative `../..` symlink
+arrives dangling (or worse, dereferenced), so the SessionStart hook silently
+emits no instructions. bump-version.sh re-syncs the copies on every release;
+this test is the belt that fails LOUDLY if a copy goes missing, gets
+symlinked by accident, or drifts from the directive between releases.
+
+The instructions matter more than the MCP face's own "instructions=" text
+through a combiner: the combiner does not forward an upstream's server
+instructions, so for its clients the directive in instructions.txt IS the
+instructions the model sees.
+"""
+
+from pathlib import Path
+
+import pytest
+
+ROOT = Path(__file__).resolve().parent.parent
+EXAMPLE = ROOT / "CLAUDE.md.example"
+PLUGINS = ("claude", "opencode", "pi")
+
+
+@pytest.mark.parametrize("plugin", PLUGINS)
+def test_instructions_txt_is_a_drift_free_copy(plugin: str) -> None:
+    path = ROOT / "plugins" / plugin / "instructions.txt"
+    assert path.is_file(), f"missing: {plugin}/instructions.txt"
+    # regular file, NOT a symlink: pack/instal copies may not preserve them
+    assert not path.is_symlink(), (
+        f"{plugin}/instructions.txt is a SYMLINK — pack/instal copies may arrive "
+        "dangling; keep it a regular copy of CLAUDE.md.example"
+    )
+    assert path.read_text(encoding="utf-8") == EXAMPLE.read_text(encoding="utf-8"), (
+        f"{plugin}/instructions.txt drifted from CLAUDE.md.example — re-sync it "
+        "(scripts/bump-version.sh does this on every release; sync it now to land "
+        "the edit between releases)"
+    )

{cribsheet-0.21.0.dev3 → cribsheet-0.21.0.dev4}/uv.lock

@@ -557,7 +557,7 @@ wheels = [
 
 [[package]]
 name = "cribsheet"
-version = "0.21.0.dev3"
+version = "0.21.0.dev4"
 source = { editable = "." }
 dependencies = [
     { name = "chromadb" },