witan-code 0.14.0__tar.gz → 0.15.0__tar.gz

{witan_code-0.14.0 → witan_code-0.15.0}/CHANGELOG.md

@@ -6,6 +6,27 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/) (pre-1.0:
 a MINOR bump may include breaking changes).
 
+## [0.15.0] - 2026-08-21
+
+### Changed
+
+- **Raised the `witan-core` floor to `>=0.32` — a RUNTIME floor.** `setup` now
+  calls `install_omnigraph(dry_run, strict=False)` to keep the old
+  keep-going-on-a-refusal behaviour, which witan-core 0.32.0 made opt-in when
+  it started raising `OmnigraphInstallFailed` by default (see witan-core's
+  CHANGELOG for why the CI callers needed that default). Anything below 0.32
+  has no `strict` parameter, so resolving below it is a `TypeError` **when
+  setup runs** — the module imports fine and every test passes, which is
+  exactly the case `just check-core-floor` documents itself as unable to catch.
+
+  No behaviour change for anyone: `setup` keeps going on a refused binary and
+  keeps printing the reason, as before.
+
+  0.32, not the 0.31 this branch was authored against: agent-kit#276 took
+  0.31.0 while this was open. This floor has now moved twice on rebase and the
+  pyproject line auto-merged silently both times, since both sides named the
+  same number — re-check it by hand on every rebase.
+
 ## [0.14.0] - 2026-08-21
 
 ### Fixed

{witan_code-0.14.0 → witan_code-0.15.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: witan-code
-Version: 0.14.0
+Version: 0.15.0
 Summary: witan-code — tree-sitter code graph + cross-repo bridge (mounts under `witan code`)
 Project-URL: Homepage, https://github.com/mitodl/agent-kit/tree/main/mcp/servers/witan-code
 Project-URL: Repository, https://github.com/mitodl/agent-kit
@@ -26,7 +26,7 @@ Requires-Dist: tree-sitter-sql<0.4,>=0.3
 Requires-Dist: tree-sitter-typescript<0.24,>=0.23
 Requires-Dist: tree-sitter-yaml<0.8,>=0.7
 Requires-Dist: tree-sitter<0.26,>=0.25
-Requires-Dist: witan-core[cli,observability,remote,sentry]<1,>=0.31
+Requires-Dist: witan-core[cli,observability,remote,sentry]<1,>=0.32
 Provides-Extra: tasks
 Requires-Dist: fastmcp-tasks<5,>=4.0.0b1; extra == 'tasks'
 Description-Content-Type: text/markdown

{witan_code-0.14.0 → witan_code-0.15.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "witan-code"
-version = "0.14.0"
+version = "0.15.0"
 description = "witan-code — tree-sitter code graph + cross-repo bridge (mounts under `witan code`)"
 readme = "README.md"
 license = "BSD-3-Clause"
@@ -108,15 +108,20 @@ dependencies = [
     # self-describing failure and delivers half of one is the quiet wrongness
     # the two floors above were raised to avoid.
     #
-    # ★ THE NUMBER MOVED 0.30 -> 0.31 ON REBASE, and that is the whole hazard
-    # this note exists to flag. agent-kit#280 took 0.30.0 for unrelated work
-    # while this branch was open, so the release carrying the diagnostics is
-    # 0.31.0 — and a floor left at >=0.30 would resolve #280's release instead
-    # and quietly deliver the half-message described above. `just
-    # check-core-floor` cannot catch it: nothing new is imported, so the
-    # clean-install import check passes at either number. Re-check this line by
-    # hand whenever this branch is rebased.
-    "witan-core[cli,remote,observability,sentry]>=0.31,<1",
+    # ★ >=0.32 IS THE FOURTH NON-IMPORT FLOOR, and the first RUNTIME one — a
+    # worked example of what `just check-core-floor` cannot see. `cli.setup`
+    # calls `install_omnigraph(dry_run, strict=False)`; anything below 0.32 has
+    # no `strict` parameter, so that is a TypeError raised WHEN SETUP RUNS — the
+    # module imports fine, every test passes, and the clean-install import check
+    # is green. Nothing catches this but the pin, which is why the pin says so.
+    # It subsumes the diagnostics reason above, which needed only >=0.31.
+    #
+    # ★ THIS NUMBER HAS MOVED TWICE ON REBASE — 0.30 -> 0.31 -> 0.32 — because
+    # agent-kit#280 then #276 each took the next witan-core release while these
+    # branches were open. Both times the pyproject line auto-merged without a
+    # conflict, since both sides named the same number. Re-check it by hand on
+    # every rebase; a floor one release low here is silent.
+    "witan-core[cli,remote,observability,sentry]>=0.32,<1",
     "fastmcp>=3.4.2,<5",
     "cyclopts>=4,<5",
     # [targets.<name>] override models (config.py) — also transitively pulled
@@ -200,7 +205,7 @@ testpaths = ["tests"]
 packages = ["witan_code"]
 
 [tool.bumpversion]
-current_version = "0.14.0"
+current_version = "0.15.0"
 allow_dirty = true
 
 [[tool.bumpversion.files]]

{witan_code-0.14.0 → witan_code-0.15.0}/tests/test_setup.py

@@ -101,3 +101,33 @@ def test_witan_code_bundle_includes_bundled_skills(tmp_path):
     bundle = setup.witan_code_bundle(pkg_dir, "tester")
 
     assert any(s.name == "witan-code" for s in bundle.skills)
+
+
+def test_setup_does_not_abort_on_a_refused_omnigraph_binary(tmp_path, monkeypatch):
+    """★ Same contract as `witan setup`, and worth asserting separately.
+
+    The installer raises by default as of witan-core 0.30.0, which is right for
+    the workflow steps calling it through `python -c` — they used to swallow a
+    checksum refusal and exit 0. It is wrong for an interactive command that
+    also installs the agent bundles: aborting would cost the user those over a
+    binary they can install separately, and the refusal is printed either way.
+
+    `cli.setup` imports `install_omnigraph` inside the function body, so the
+    patch target is witan_core's own attribute rather than a module-level name
+    in cli.
+    """
+    import witan_core
+
+    from witan_code import cli
+
+    calls: list[dict] = []
+    monkeypatch.setattr(
+        witan_core,
+        "install_omnigraph",
+        lambda dry_run, **kwargs: calls.append({"dry_run": dry_run, **kwargs}),
+    )
+    monkeypatch.setattr(Path, "home", lambda: tmp_path)
+
+    cli.setup(agent="claude", author="tester")
+
+    assert calls == [{"dry_run": False, "strict": False}]

{witan_code-0.14.0 → witan_code-0.15.0}/witan_code/cli.py

@@ -733,7 +733,10 @@ def setup(
     author = resolve_author(author)
 
     print("omnigraph binary")
-    install_omnigraph(dry_run)
+    # strict=False, same reasoning as `witan setup`: a refused binary must not
+    # cost the user the agent bundles this command also installs. The installer
+    # prints the refusal regardless.
+    install_omnigraph(dry_run, strict=False)
 
     bundle = witan_code_bundle(pkg_dir, author)