bantamkit 0.34.2__tar.gz → 0.34.3__tar.gz

{bantamkit-0.34.2 → bantamkit-0.34.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: bantamkit
-Version: 0.34.2
+Version: 0.34.3
 Summary: Memory MCP server for Claude Code, Cursor, VS Code Copilot and Claude Desktop, plus a Python library that lifts small-model agents. Install once, run offline.
 Project-URL: Homepage, https://github.com/Ink01101011/bantamkit
 Project-URL: Repository, https://github.com/Ink01101011/bantamkit
@@ -96,9 +96,9 @@ CPU architecture and Python minor version** (some wheels, such as `pydantic_core
 one platform only), copy `wheels/` across, and install from it:
 
 ```bash
-python -m pip download "bantamkit[mcp]==0.34.2" -d wheels
+python -m pip download "bantamkit[mcp]==0.34.3" -d wheels
 python -m venv <env>
-<env>/bin/pip install --no-index --find-links wheels "bantamkit[mcp]==0.34.2"
+<env>/bin/pip install --no-index --find-links wheels "bantamkit[mcp]==0.34.3"
 <env>/bin/bantamkit-mcp --install cursor
 ```
 
@@ -247,10 +247,10 @@ pipx upgrade bantamkit                 # pipx
 uv tool upgrade bantamkit              # uv
 ```
 
-`--update` (`check the package index and update this install if it differs, then exit`) is the
-only network access here. An editable install, a local file or a source tree is refused with
-exit 1 and a sentence naming the manual route (for a clone, `git pull`). For a wheelhouse, repeat
-the download and install.
+`--update` (`check the package index and update this install if it differs, then exit`) upgrades
+an install from PyPI with this interpreter's pip; it is the only network access here. An editable
+install, a local file or a source tree is refused with exit 1 and a sentence naming the manual
+route (for a clone, `git pull`). For a wheelhouse, repeat the download and install.
 
 **Then restart the server in the host** (`/mcp` → reconnect in Claude Code; fully restart Claude
 Desktop). `bantamkit_status` prints the version **and the `build_id` of the code answering
@@ -288,7 +288,7 @@ you**; a new version with an old `build_id` means an old process.
 | `shiftwork_status` | report the open cursor |
 | `token_ledger` | what a session cost, read off the host's transcripts |
 | `bantamkit_status` | report store health against its budget |
-| `build_identity` | report the fingerprint of the source on disk, not the executing code |
+| `build_identity` | report the fingerprint of the source on disk, not the executing code — useful when a machine carries two installs under one name |
 
 The document reader `bantamkit_read` left the served tools in job50 (2026-09-12) and stays in the
 library as `bantamkit.docread`.
@@ -303,7 +303,7 @@ under the `[mcp]` extra.
 Contracts, schemas, eval tasks, rubrics and tool manifests ship inside the package.
 `bantamkit-mcp --assets-root` prints the resolved directory and its file count, and
 `BANTAMKIT_ASSETS` overrides it. A build that cannot find the pack fails instead of shipping
-without it.
+without it — deliberately, because the silent version shipped once.
 
 ## The operator CLI: `python -m bantamkit.memory`
 
@@ -342,7 +342,7 @@ git clone https://github.com/Ink01101011/bantamkit
 cd bantamkit
 python -m venv .venv && .venv/bin/pip install -e "runtime-py[dev,mcp]"
 .venv/bin/python -m pytest runtime-py/tests -q
-.venv/bin/ruff check runtime-py
+.venv/bin/ruff check runtime-py tools
 ```
 
 The cross-runtime gate needs Node:

{bantamkit-0.34.2 → bantamkit-0.34.3}/README.md

@@ -68,9 +68,9 @@ CPU architecture and Python minor version** (some wheels, such as `pydantic_core
 one platform only), copy `wheels/` across, and install from it:
 
 ```bash
-python -m pip download "bantamkit[mcp]==0.34.2" -d wheels
+python -m pip download "bantamkit[mcp]==0.34.3" -d wheels
 python -m venv <env>
-<env>/bin/pip install --no-index --find-links wheels "bantamkit[mcp]==0.34.2"
+<env>/bin/pip install --no-index --find-links wheels "bantamkit[mcp]==0.34.3"
 <env>/bin/bantamkit-mcp --install cursor
 ```
 
@@ -219,10 +219,10 @@ pipx upgrade bantamkit                 # pipx
 uv tool upgrade bantamkit              # uv
 ```
 
-`--update` (`check the package index and update this install if it differs, then exit`) is the
-only network access here. An editable install, a local file or a source tree is refused with
-exit 1 and a sentence naming the manual route (for a clone, `git pull`). For a wheelhouse, repeat
-the download and install.
+`--update` (`check the package index and update this install if it differs, then exit`) upgrades
+an install from PyPI with this interpreter's pip; it is the only network access here. An editable
+install, a local file or a source tree is refused with exit 1 and a sentence naming the manual
+route (for a clone, `git pull`). For a wheelhouse, repeat the download and install.
 
 **Then restart the server in the host** (`/mcp` → reconnect in Claude Code; fully restart Claude
 Desktop). `bantamkit_status` prints the version **and the `build_id` of the code answering
@@ -260,7 +260,7 @@ you**; a new version with an old `build_id` means an old process.
 | `shiftwork_status` | report the open cursor |
 | `token_ledger` | what a session cost, read off the host's transcripts |
 | `bantamkit_status` | report store health against its budget |
-| `build_identity` | report the fingerprint of the source on disk, not the executing code |
+| `build_identity` | report the fingerprint of the source on disk, not the executing code — useful when a machine carries two installs under one name |
 
 The document reader `bantamkit_read` left the served tools in job50 (2026-09-12) and stays in the
 library as `bantamkit.docread`.
@@ -275,7 +275,7 @@ under the `[mcp]` extra.
 Contracts, schemas, eval tasks, rubrics and tool manifests ship inside the package.
 `bantamkit-mcp --assets-root` prints the resolved directory and its file count, and
 `BANTAMKIT_ASSETS` overrides it. A build that cannot find the pack fails instead of shipping
-without it.
+without it — deliberately, because the silent version shipped once.
 
 ## The operator CLI: `python -m bantamkit.memory`
 
@@ -314,7 +314,7 @@ git clone https://github.com/Ink01101011/bantamkit
 cd bantamkit
 python -m venv .venv && .venv/bin/pip install -e "runtime-py[dev,mcp]"
 .venv/bin/python -m pytest runtime-py/tests -q
-.venv/bin/ruff check runtime-py
+.venv/bin/ruff check runtime-py tools
 ```
 
 The cross-runtime gate needs Node:

{bantamkit-0.34.2 → bantamkit-0.34.3}/src/bantamkit/__init__.py

@@ -29,4 +29,4 @@ from bantamkit.structured import StructuredOutputError, extract_json, structured
 # file as its dynamic version source, so the wheel's metadata and the string the MCP
 # server advertises are the same committed bytes, and neither is a function of when
 # someone last ran `pip`.
-__version__ = "0.34.2"
+__version__ = "0.34.3"

{bantamkit-0.34.2 → bantamkit-0.34.3}/src/bantamkit/eventlog.py

@@ -69,7 +69,7 @@ from datetime import UTC, datetime, timedelta
 from pathlib import Path
 from typing import Any
 
-from bantamkit.memory.store import ensure_bantamkit_gitignore
+from bantamkit.memory.store import bantamkit_dir_for, ensure_bantamkit_gitignore
 
 #: Environment switch. Unset or `off`/`0`/`false`/`no`/empty -> disabled. `on`/`1`/
 #: `true`/`yes` -> the default file inside the memory store. Anything else is taken as
@@ -289,11 +289,12 @@ class EventLog:
         # USER RULING #2 (J51-8a): the ignore file is written only when THIS call is what
         # creates `.bantamkit`, so existence has to be checked BEFORE the mkdir below --
         # after it, the directory unconditionally exists and the question is unanswerable.
-        bantamkit_dir = None
-        for parent in self.path.parents:
-            if parent.name == ".bantamkit":
-                bantamkit_dir = parent
-                break
+        #
+        # J54-3: the walk moved into `bantamkit_dir_for` beside the writer it feeds, so the
+        # two creators in this runtime ask the same question in the same words rather than
+        # keeping a copy each. The answer here is unchanged -- a log file is never itself
+        # named `.bantamkit`, so self-or-ancestors and ancestors give the same directory.
+        bantamkit_dir = bantamkit_dir_for(self.path)
         bantamkit_dir_existed_before = bantamkit_dir is not None and bantamkit_dir.exists()
         self.path.parent.mkdir(parents=True, exist_ok=True)
         if bantamkit_dir is not None:

{bantamkit-0.34.2 → bantamkit-0.34.3}/src/bantamkit/memory/store.py

@@ -286,6 +286,14 @@ def ensure_bantamkit_gitignore(directory: Path, *, created: bool) -> None:
     would leave a `.bantamkit` that git can see (or ignore one it should not), which is
     the whole bug this closes.
 
+    THE CREATORS, ENUMERATED (J54-3), because "anything else" is how one got missed: in
+    THIS runtime there are exactly two -- `MemoryStore._ensure_dirs` and `EventLog._append`
+    -- and both now ask `bantamkit_dir_for` which directory the decision is about, rather
+    than assuming the root's parent is it. `runtime-ts` has a THIRD, `hostinstall`'s
+    `thisCommand`, where npm creates `~/.bantamkit/mcp` for `--install`; there is no npm
+    install path in this runtime (the offline install is Node-only by user ruling), which
+    is why that creator has no counterpart here. `docs/porting.md` carries the row.
+
     NEVER REWRITES. A `.gitignore` that already exists -- whatever its bytes -- is left
     exactly as it is, kept as a second guard even when `created` is `True`: an operator
     who deleted it to commit the directory keeps that decision, and this never diffs its
@@ -313,6 +321,34 @@ def ensure_bantamkit_gitignore(directory: Path, *, created: bool) -> None:
         pass
 
 
+def bantamkit_dir_for(path: Path) -> Path | None:
+    """The `.bantamkit` directory a `mkdir(parents=True)` of `path` would create or fill,
+    or `None` when there is none: `path` itself if it is named `.bantamkit`, otherwise its
+    nearest ancestor that is.
+
+    WHY A WALK AND NOT `path.parent` (J54-3). Every creator has to hand
+    `ensure_bantamkit_gitignore` the directory the decision is ABOUT, and `parent` is the
+    right answer for exactly one shape of path, `<x>/.bantamkit/memory`. A store rooted AT
+    the `.bantamkit` directory (`--store ~/.bantamkit`) or nested deeper under it
+    (`<x>/.bantamkit/memory/extra`) creates a `.bantamkit` whose gitignore decision was
+    taken about the wrong directory -- so no decision was taken at all, and git could see
+    the whole tree. MEASURED, not hypothetical: `~/.bantamkit` on the machine this was
+    found on holds an empty `facts/` and `archive/` beside `memory/`, left by a store once
+    rooted at it, and no `.gitignore`.
+
+    NEAREST AND NOT OUTERMOST, which is the choice `EventLog._append` already made and this
+    function now carries for both creators: under a `<x>/.bantamkit/y/.bantamkit/z` the
+    directory a reader would expect to be ignored is the one the store is actually in.
+
+    READ-ONLY. It looks at names, never at the filesystem, so it is equally valid before or
+    after the mkdir -- but `created` is answered by checking THIS path's existence BEFORE.
+    """
+    for candidate in (path, *path.parents):
+        if candidate.name == ".bantamkit":
+            return candidate
+    return None
+
+
 class MemoryStore:
     def __init__(
         self,
@@ -405,8 +441,16 @@ class MemoryStore:
         # Checked BEFORE the mkdir, per user ruling #2: this is the one moment that can
         # tell whether `.bantamkit` already existed. After the mkdir it unconditionally
         # exists either way, so the answer has to be captured now or not at all.
-        bantamkit_dir = self.root.parent
-        bantamkit_dir_existed_before = bantamkit_dir.exists()
+        #
+        # J54-3: `bantamkit_dir_for`, not `self.root.parent`. The mkdir below is
+        # `parents=True`, so it creates every missing component of `self.root` -- a root
+        # that IS the `.bantamkit` directory, or one nested deeper under it, brought a
+        # `.bantamkit` into existence while the decision was being taken about some other
+        # directory, which meant no decision at all.
+        bantamkit_dir = bantamkit_dir_for(self.root)
+        bantamkit_dir_existed_before = (
+            bantamkit_dir is not None and bantamkit_dir.exists()
+        )
         try:
             (self.root / "facts").mkdir(parents=True, exist_ok=True)
             (self.root / "archive").mkdir(parents=True, exist_ok=True)
@@ -415,7 +459,10 @@ class MemoryStore:
                 f"memory store could not be created: {self.root}; the directory is not"
                 " there and this filesystem would not make it, so nothing was written"
             ) from e
-        ensure_bantamkit_gitignore(bantamkit_dir, created=not bantamkit_dir_existed_before)
+        if bantamkit_dir is not None:
+            ensure_bantamkit_gitignore(
+                bantamkit_dir, created=not bantamkit_dir_existed_before
+            )
 
     # ---- ops ----
 

{bantamkit-0.34.2 → bantamkit-0.34.3}/tests/test_bantamkit_gitignore.py

@@ -234,3 +234,67 @@ def test_eventlog_path_unrelated_to_dot_bantamkit_writes_no_gitignore(tmp_path):
 
     assert log.write_failed is False
     assert not list(tmp_path.glob("**/.gitignore"))
+
+
+# ---------------------------------------------------------------------- J54-3 (2026-09-18)
+#
+# THE SECOND CREATOR THE PROPERTY MISSED, and it is not hypothetical: on the machine this
+# was found on, `~/.bantamkit` holds an empty `facts/` and `archive/` beside `memory/` --
+# a `MemoryStore` was once rooted AT the `.bantamkit` directory itself (`--store
+# ~/.bantamkit`), its `mkdir(parents=True)` brought `~/.bantamkit` into existence, and the
+# gitignore decision was taken about `~` instead, because `_ensure_dirs` looked at
+# `self.root.parent` and nothing else.
+#
+# `self.root.parent` is the right directory for exactly one shape of root,
+# `<x>/.bantamkit/memory`. A root that IS the `.bantamkit` directory, or one nested deeper
+# under it, creates a `.bantamkit` that no call ever decides about -- the hole the
+# docstring names as "a second creator that skipped this call, or that got `created`
+# wrong". `EventLog._append` already walks the ancestors to find the `.bantamkit` among
+# them; this is that same walk, in the other creator.
+
+
+def test_j54_3_a_store_rooted_at_the_bantamkit_directory_itself_gets_the_gitignore(tmp_path):
+    root = tmp_path / ".bantamkit"
+    assert not root.exists()
+
+    MemoryStore(root)
+
+    gitignore = root / ".gitignore"
+    assert gitignore.exists()
+    assert gitignore.read_bytes() == BANTAMKIT_GITIGNORE_TEXT.encode("utf-8")
+
+
+def test_j54_3_a_store_nested_deeper_under_bantamkit_gets_the_gitignore(tmp_path):
+    root = tmp_path / ".bantamkit" / "memory" / "extra"
+    assert not (tmp_path / ".bantamkit").exists()
+
+    MemoryStore(root)
+
+    gitignore = tmp_path / ".bantamkit" / ".gitignore"
+    assert gitignore.exists()
+    assert gitignore.read_text(encoding="utf-8") == BANTAMKIT_GITIGNORE_TEXT
+
+
+def test_j54_3_ruling_2_holds_for_a_store_rooted_at_an_existing_bantamkit(tmp_path):
+    """The fix must not over-fire: a `.bantamkit` that predates this call never gets one,
+    whichever creator is looking at it."""
+    root = tmp_path / ".bantamkit"
+    root.mkdir()
+
+    store = MemoryStore(root)
+    store.save("project", "widget-cache", "one line", "body", ())
+
+    assert not (root / ".gitignore").exists()
+
+
+def test_j54_3_deleting_the_gitignore_under_a_nested_root_stays_deleted(tmp_path):
+    root = tmp_path / ".bantamkit" / "memory" / "extra"
+    gitignore = tmp_path / ".bantamkit" / ".gitignore"
+
+    store = MemoryStore(root)
+    assert gitignore.exists()
+
+    gitignore.unlink()
+    store.save("project", "widget-cache", "one line", "body", ())
+
+    assert not gitignore.exists()