witan-code 0.22.0__tar.gz → 0.24.0__tar.gz

{witan_code-0.22.0 → witan_code-0.24.0}/CHANGELOG.md

@@ -8,6 +8,83 @@ a MINOR bump may include breaking changes).
 
 <!-- scriv-insert-here -->
 
+## [0.24.0] - 2026-10-02
+
+### Added
+
+- `witan-code setup --force` replaces a symlink or non-directory occupying an install destination (e.g. a stale symlink under `~/.pi/agent/extensions`). Without it, `witan-code setup` now exits 2 with the conflicting path instead of a `FileNotFoundError` traceback.
+
+- `witan-code inject-context --client pi-builtin` renders the code-tool
+  discovery line for Pi's built-in MCP: a `codemode` script that finds the
+  `mcp__<server>__code_*` name with `searchTools()` and calls it as
+  `tools.<name>()`. The Pi extension passes it unless pi-mcp-adapter's `mcp`
+  tool is registered, in which case it still passes `--client pi`, whose
+  output is unchanged.
+
+### Changed
+
+- The `witan-code` skill describes calling the `code_*` tools under Pi's
+  built-in MCP as well as under pi-mcp-adapter, and `witan-code setup --agent
+  pi` no longer warns that pi-mcp-adapter is missing when Pi's built-in MCP
+  will read the witan-code entry.
+- Requires `agent-config-kit>=0.12`, which has that check; with an older one,
+  `witan-code setup --agent pi` still printed the pi-mcp-adapter warning.
+
+### Fixed
+
+- `witan-code checkpoint`'s background `optimize` now also runs `cleanup --older-than 30d` at most once per `WITAN_CODE_CLEANUP_INTERVAL` (default weekly; `0` disables). On omnigraph 0.11 `optimize` no longer reclaims the storage of branches deleted by `branches --prune` or `reap-views --apply`, and nothing ran `cleanup` unless done by hand. `witan-code optimize` gains `--cleanup-older-than` to run both in one process.
+
+## [0.23.0] - 2026-09-28
+
+### Added
+
+- **Python package providers.** A `pyproject.toml` whose directory holds a
+  `mitol/<pkg>/__init__.py` namespace child now provides `mitol.<pkg>`, so
+  `mitol.*` imports join to ol-django. Previously only `@mitodl/*` npm
+  packages had a provider extractor and no Python import could form an edge.
+  An existing graph gains these providers on ol-django's next full-repo
+  `witan-code index` (the provider files are not source files, so the
+  unchanged-file skip does not apply to them); `witan-code reindex` on it
+  works too.
+
+- **Repo-level provider files that stop producing bindings lose their old
+  rows.** A `pyproject.toml`, `package.json`, Pulumi config or OpenAPI spec
+  that emitted nothing on this run was never purged, so on a run that could
+  not purge by the collected file list (e.g. indexing outside a repository
+  root) its previous bindings stayed. Every such file scanned is now purged
+  before its fresh bindings are written.
+
+### Changed
+
+- Allow cyclopts 5 (`cyclopts>=4,<6`). Under cyclopts 5, `--help` shows a
+  value placeholder after each option (e.g. `--target STR`), and a usage error
+  such as an unknown option exits with code 2 instead of 1.
+
+### Fixed
+
+- **`witan code` listings emit `rows: []` on an empty result under
+  `--output-format`.** `symbols`, `stitch`, `stitch --unresolved` and `repos`
+  each returned early with a Rich sentence on stdout before the format was
+  consulted, so an empty result was not JSON/TOML/YAML. `_render_table` now
+  takes the empty message and prints it in `txt` mode only. `branches` never
+  consulted the format at all and now dumps `{repo, views, error}` rows, with
+  `--prune`'s progress lines on stderr under a structured format; the `repos`
+  unreadable-store warning and `doctor`'s summary and error lines move to
+  stderr there too.
+- **Table titles and cells are escaped for Rich.** A symbol, path or title
+  containing `[...]` was read as markup and lost from the rendered table.
+
+- **Endpoint bindings form cross-repo edges again.** Every endpoint consumer
+  scored 0.0 because the extractor only matches relative paths and the
+  `relative_url` heuristic subtracted 0.5 from the 0.5 baseline, so
+  `code_repo_dependencies` and the other heuristic-tier views filtered every
+  one out at their 0.5 cutoff. The `relative_url` penalty, its unreachable
+  `explicit_hostname` boost, and the `generated_file` penalty are removed. A
+  generated client for a repo's own API is still suppressed by
+  `self_provided_key`. Stored confidences are computed at index time, so
+  existing graphs need `witan-code reindex` (not `index`, which skips
+  unchanged files) on the consumer repos before these edges appear.
+
 ## [0.22.0] - 2026-09-25
 
 ### Added
@@ -302,7 +379,6 @@ a MINOR bump may include breaking changes).
   write threw". Deliberately still non-fatal — the per-repo index succeeds and
   is worth keeping — but "non-fatal" and "unreported" are different claims.
 
-
 - **The test suite no longer asserts an environment.** Four tests
   (`test_branches.py`'s three branch-view assertions and
   `test_graph.py::test_a_shared_branch_view_needs_an_identity_to_own_it`)

{witan_code-0.22.0 → witan_code-0.24.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: witan-code
-Version: 0.22.0
+Version: 0.24.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
@@ -10,8 +10,8 @@ License-Expression: BSD-3-Clause
 Keywords: agent,code-graph,coding-agent,mcp,static-analysis,tree-sitter
 Classifier: Programming Language :: Python :: 3
 Requires-Python: >=3.11
-Requires-Dist: agent-config-kit<1,>=0.10
-Requires-Dist: cyclopts<5,>=4
+Requires-Dist: agent-config-kit<1,>=0.12
+Requires-Dist: cyclopts<6,>=4
 Requires-Dist: fastmcp<5,>=4
 Requires-Dist: joserfc<2,>=1.0
 Requires-Dist: pydantic<3,>=2
@@ -82,7 +82,7 @@ arbitration applies. See [`docs/BRANCH_INDEXING.md`](docs/BRANCH_INDEXING.md).
 The two layers compose through **soft symbol-ID references**. A Layer-1 node
 (e.g. a `lesson` or `agent_context`) can record symbol ids of the form:
 
-```
+```text
 repo#relative/path.py::QualifiedName
 e.g. https://github.com/mitodl/ol-django#app/svc.py::Service.run
 ```
@@ -136,7 +136,7 @@ edges):
 |---|---|---|---|
 | `env_var` | Pulumi `<app>:env_vars` keys in `Pulumi.*.yaml` | `get_string("NAME",…)` / `os.environ` / `process.env.X` / `env("NAME")` | the `UPPER_SNAKE` name |
 | `endpoint` | drf-spectacular OpenAPI spec (`paths.<path>.<method>`) | `/api/…` path literals in TS (generated client / fetch) | normalized path (params → `{}`) |
-| `package` | a repo whose `package.json` name is `@mitodl/*` | `from mitol.*` / `include("mitol.*")` / `@mitodl/*` imports | the package name |
+| `package` | a repo whose `package.json` name is `@mitodl/*`, or a `pyproject.toml` next to a `mitol/<pkg>/__init__.py` namespace child (provides `mitol.<pkg>`) | `from mitol.*` / `include("mitol.*")` / `@mitodl/*` imports | the package name |
 | `service` | `applications/<svc>/__main__.py` (repo / image / service name) | the deployed repo itself (key_norm = its canonical URI) | `repo:<uri>` / `image:…` / `name:…` |
 
 Generic env names (`DEBUG`, `PORT`, `SECRET_KEY`, …) are flagged `generic` and
@@ -146,7 +146,7 @@ every repo.
 The bridge is written in a **separate phase after the per-repo store write**, so
 the two stores' advisory write locks never nest (no deadlock) and a bridge
 failure never corrupts a per-repo store. A full-repo index runs the repo-level
-provider extractors (OpenAPI / Pulumi / service / `package.json`) and clears
+provider extractors (OpenAPI / Pulumi / service / `package.json` / `pyproject.toml`) and clears
 bindings for files deleted from disk; all purging is per-file, so unchanged
 (skipped) files — and, for a narrow target like the reindex hook, sibling
 files — keep their bindings.
@@ -299,11 +299,12 @@ witan-code setup --dry-run          # preview without writing
 witan-code setup --author "Jane Doe"  # attribution (default: git config user.name)
 ```
 
-On Pi, the MCP server entry (`~/.pi/agent/mcp.json`) is read only by the
-third-party pi-mcp-adapter Pi package, since Pi core has no MCP support:
-install it with `pi install npm:pi-mcp-adapter`, restart Pi, and confirm it
-in `pi list`. `witan-code setup --agent pi` warns when it cannot find the
-package declared in Pi's settings.
+On Pi, the MCP server entry (`~/.pi/agent/mcp.json`) is read by Pi's
+built-in MCP support (Pi 0.99 and later), or by the pi-mcp-adapter Pi
+package when that is installed; confirm with `pi mcp list` or `/mcp` inside
+Pi. `witan-code setup --agent pi` warns when Pi's settings show neither one
+would load it (the built-in turned off with `-builtin:mcp`, or a Pi older
+than 0.99, and no adapter declared).
 
 If `witan` is *also* installed and witan-code is importable in that same
 environment (e.g. via the `--with` in the `uv tool install`/MCP server's
@@ -354,6 +355,7 @@ symlink alternative:
 | `WITAN_AUTHOR` / `USER` | `unknown` | attribution string |
 | `WITAN_REPO` | — | override the detected repo slug |
 | `WITAN_CODE_OPTIMIZE_INTERVAL` | `86400` (daily) | throttle window (seconds) for `checkpoint`'s opportunistic store compaction; `0` disables it |
+| `WITAN_CODE_CLEANUP_INTERVAL` | `604800` (weekly) | throttle window (seconds) for the `cleanup --older-than 30d` that rides a `checkpoint` compaction; `0` disables it |
 | `WITAN_CODE_INDEX_ROLE` | `client` | `ci` designates this process the writer of a shared graph's default-branch view. Only meaningful against a shared cluster graph; local stores are unaffected. See [Branch indexing](docs/BRANCH_INDEXING.md#who-may-write-the-shared-default-branch-view) |
 | `WITAN_ACTOR` | derived from the `witan login` session | the identity that owns the branch views this process writes; an `act-…` id or a raw OIDC `sub`. For a non-interactive writer (CI, a maintenance job). See [Branch indexing](docs/BRANCH_INDEXING.md#per-writer-branch-views) |
 | `WITAN_CONFIG` | `~/.config/witan/config.toml` | config file path (see below) |
@@ -640,12 +642,18 @@ mechanisms keep this in check, mirroring that module (deliberately duplicated
 - **Opportunistic**: the `witan-code checkpoint` Stop hook spawns a
   throttled, detached `witan-code optimize` for the current repo's store and
   the shared bridge store, at most once per `WITAN_CODE_OPTIMIZE_INTERVAL`
-  (default daily; `0` disables) each — see [Hooks](#hooks).
-- **Scheduled**: `witan-code optimize [--store PATH | --bridge]` /
-  `witan-code cleanup --yes` for cron/systemd-timer driven maintenance on a
-  busy store. `optimize` is non-destructive and safe to run repeatedly;
-  `cleanup` GCs old Lance versions to reclaim disk and is destructive, so it
-  requires `--yes`.
+  (default daily; `0` disables) each — see [Hooks](#hooks). At most once per
+  `WITAN_CODE_CLEANUP_INTERVAL` (default weekly) the run also cleans up
+  versions older than 30 days. On omnigraph 0.11 that is the only thing that
+  reclaims the storage of branches deleted by `branches --prune` or
+  `reap-views --apply`; `optimize` no longer does.
+- **Scheduled**: `witan-code optimize [--store PATH | --bridge]
+  [--cleanup-older-than DURATION]` / `witan-code cleanup --yes` for
+  cron/systemd-timer driven maintenance on a busy store. `optimize` alone is
+  non-destructive and safe to run repeatedly. `cleanup` GCs old Lance versions
+  to reclaim disk and is destructive, so it requires `--yes`.
+  `--cleanup-older-than` makes `optimize` run that destructive cleanup
+  afterwards with no `--yes` prompt, which is how the Stop hook calls it.
 
 ## Rebuilding an unreadable store
 
@@ -721,10 +729,13 @@ A Pi equivalent of all four lives in one extension,
   can tell "no cross-repo consumers" from "no cross-repo data"), and the
   `ToolSearch` call that makes the `code_*` tools callable when the harness
   delivers them deferred — followed by a `code_find_definition` →
-  `code_callers`/`code_impact` call template. `--client pi` (what the Pi
-  extension passes) swaps the `ToolSearch` step for pi-mcp-adapter's `mcp`
-  proxy: `mcp({ search: ... })` for the exact server-prefixed name, then
-  `mcp({ tool: ..., args: {...} })`. The default stays Claude's.
+  `code_callers`/`code_impact` call template. The Pi extension swaps the
+  `ToolSearch` step for Pi's calling convention: `--client pi-builtin`, for
+  Pi's built-in MCP, gives a `codemode` script (`searchTools(...)` for the
+  exact `mcp__<server>__` name, then `tools.<name>({...})`), and
+  `--client pi`, which it passes when pi-mcp-adapter's `mcp` tool is
+  registered, gives the adapter's proxy (`mcp({ search: ... })`, then
+  `mcp({ tool: ..., args: {...} })`). The default stays Claude's.
   Independent of `witan`'s own `inject-context` hook (no cross-package
   coupling) — register it alone for a witan-code-only install. Prints
   nothing when the repo has neither a store nor an index in flight.

{witan_code-0.22.0 → witan_code-0.24.0}/README.md

@@ -49,7 +49,7 @@ arbitration applies. See [`docs/BRANCH_INDEXING.md`](docs/BRANCH_INDEXING.md).
 The two layers compose through **soft symbol-ID references**. A Layer-1 node
 (e.g. a `lesson` or `agent_context`) can record symbol ids of the form:
 
-```
+```text
 repo#relative/path.py::QualifiedName
 e.g. https://github.com/mitodl/ol-django#app/svc.py::Service.run
 ```
@@ -103,7 +103,7 @@ edges):
 |---|---|---|---|
 | `env_var` | Pulumi `<app>:env_vars` keys in `Pulumi.*.yaml` | `get_string("NAME",…)` / `os.environ` / `process.env.X` / `env("NAME")` | the `UPPER_SNAKE` name |
 | `endpoint` | drf-spectacular OpenAPI spec (`paths.<path>.<method>`) | `/api/…` path literals in TS (generated client / fetch) | normalized path (params → `{}`) |
-| `package` | a repo whose `package.json` name is `@mitodl/*` | `from mitol.*` / `include("mitol.*")` / `@mitodl/*` imports | the package name |
+| `package` | a repo whose `package.json` name is `@mitodl/*`, or a `pyproject.toml` next to a `mitol/<pkg>/__init__.py` namespace child (provides `mitol.<pkg>`) | `from mitol.*` / `include("mitol.*")` / `@mitodl/*` imports | the package name |
 | `service` | `applications/<svc>/__main__.py` (repo / image / service name) | the deployed repo itself (key_norm = its canonical URI) | `repo:<uri>` / `image:…` / `name:…` |
 
 Generic env names (`DEBUG`, `PORT`, `SECRET_KEY`, …) are flagged `generic` and
@@ -113,7 +113,7 @@ every repo.
 The bridge is written in a **separate phase after the per-repo store write**, so
 the two stores' advisory write locks never nest (no deadlock) and a bridge
 failure never corrupts a per-repo store. A full-repo index runs the repo-level
-provider extractors (OpenAPI / Pulumi / service / `package.json`) and clears
+provider extractors (OpenAPI / Pulumi / service / `package.json` / `pyproject.toml`) and clears
 bindings for files deleted from disk; all purging is per-file, so unchanged
 (skipped) files — and, for a narrow target like the reindex hook, sibling
 files — keep their bindings.
@@ -266,11 +266,12 @@ witan-code setup --dry-run          # preview without writing
 witan-code setup --author "Jane Doe"  # attribution (default: git config user.name)
 ```
 
-On Pi, the MCP server entry (`~/.pi/agent/mcp.json`) is read only by the
-third-party pi-mcp-adapter Pi package, since Pi core has no MCP support:
-install it with `pi install npm:pi-mcp-adapter`, restart Pi, and confirm it
-in `pi list`. `witan-code setup --agent pi` warns when it cannot find the
-package declared in Pi's settings.
+On Pi, the MCP server entry (`~/.pi/agent/mcp.json`) is read by Pi's
+built-in MCP support (Pi 0.99 and later), or by the pi-mcp-adapter Pi
+package when that is installed; confirm with `pi mcp list` or `/mcp` inside
+Pi. `witan-code setup --agent pi` warns when Pi's settings show neither one
+would load it (the built-in turned off with `-builtin:mcp`, or a Pi older
+than 0.99, and no adapter declared).
 
 If `witan` is *also* installed and witan-code is importable in that same
 environment (e.g. via the `--with` in the `uv tool install`/MCP server's
@@ -321,6 +322,7 @@ symlink alternative:
 | `WITAN_AUTHOR` / `USER` | `unknown` | attribution string |
 | `WITAN_REPO` | — | override the detected repo slug |
 | `WITAN_CODE_OPTIMIZE_INTERVAL` | `86400` (daily) | throttle window (seconds) for `checkpoint`'s opportunistic store compaction; `0` disables it |
+| `WITAN_CODE_CLEANUP_INTERVAL` | `604800` (weekly) | throttle window (seconds) for the `cleanup --older-than 30d` that rides a `checkpoint` compaction; `0` disables it |
 | `WITAN_CODE_INDEX_ROLE` | `client` | `ci` designates this process the writer of a shared graph's default-branch view. Only meaningful against a shared cluster graph; local stores are unaffected. See [Branch indexing](docs/BRANCH_INDEXING.md#who-may-write-the-shared-default-branch-view) |
 | `WITAN_ACTOR` | derived from the `witan login` session | the identity that owns the branch views this process writes; an `act-…` id or a raw OIDC `sub`. For a non-interactive writer (CI, a maintenance job). See [Branch indexing](docs/BRANCH_INDEXING.md#per-writer-branch-views) |
 | `WITAN_CONFIG` | `~/.config/witan/config.toml` | config file path (see below) |
@@ -607,12 +609,18 @@ mechanisms keep this in check, mirroring that module (deliberately duplicated
 - **Opportunistic**: the `witan-code checkpoint` Stop hook spawns a
   throttled, detached `witan-code optimize` for the current repo's store and
   the shared bridge store, at most once per `WITAN_CODE_OPTIMIZE_INTERVAL`
-  (default daily; `0` disables) each — see [Hooks](#hooks).
-- **Scheduled**: `witan-code optimize [--store PATH | --bridge]` /
-  `witan-code cleanup --yes` for cron/systemd-timer driven maintenance on a
-  busy store. `optimize` is non-destructive and safe to run repeatedly;
-  `cleanup` GCs old Lance versions to reclaim disk and is destructive, so it
-  requires `--yes`.
+  (default daily; `0` disables) each — see [Hooks](#hooks). At most once per
+  `WITAN_CODE_CLEANUP_INTERVAL` (default weekly) the run also cleans up
+  versions older than 30 days. On omnigraph 0.11 that is the only thing that
+  reclaims the storage of branches deleted by `branches --prune` or
+  `reap-views --apply`; `optimize` no longer does.
+- **Scheduled**: `witan-code optimize [--store PATH | --bridge]
+  [--cleanup-older-than DURATION]` / `witan-code cleanup --yes` for
+  cron/systemd-timer driven maintenance on a busy store. `optimize` alone is
+  non-destructive and safe to run repeatedly. `cleanup` GCs old Lance versions
+  to reclaim disk and is destructive, so it requires `--yes`.
+  `--cleanup-older-than` makes `optimize` run that destructive cleanup
+  afterwards with no `--yes` prompt, which is how the Stop hook calls it.
 
 ## Rebuilding an unreadable store
 
@@ -688,10 +696,13 @@ A Pi equivalent of all four lives in one extension,
   can tell "no cross-repo consumers" from "no cross-repo data"), and the
   `ToolSearch` call that makes the `code_*` tools callable when the harness
   delivers them deferred — followed by a `code_find_definition` →
-  `code_callers`/`code_impact` call template. `--client pi` (what the Pi
-  extension passes) swaps the `ToolSearch` step for pi-mcp-adapter's `mcp`
-  proxy: `mcp({ search: ... })` for the exact server-prefixed name, then
-  `mcp({ tool: ..., args: {...} })`. The default stays Claude's.
+  `code_callers`/`code_impact` call template. The Pi extension swaps the
+  `ToolSearch` step for Pi's calling convention: `--client pi-builtin`, for
+  Pi's built-in MCP, gives a `codemode` script (`searchTools(...)` for the
+  exact `mcp__<server>__` name, then `tools.<name>({...})`), and
+  `--client pi`, which it passes when pi-mcp-adapter's `mcp` tool is
+  registered, gives the adapter's proxy (`mcp({ search: ... })`, then
+  `mcp({ tool: ..., args: {...} })`). The default stays Claude's.
   Independent of `witan`'s own `inject-context` hook (no cross-package
   coupling) — register it alone for a witan-code-only install. Prints
   nothing when the repo has neither a store nor an index in flight.

{witan_code-0.22.0 → witan_code-0.24.0}/conftest.py

@@ -23,4 +23,4 @@ sys.path.insert(0, str(Path(__file__).resolve().parents[3]))
 
 # The import is the point: `testsupport.hermetic` redirects the environment at
 # module scope. The hook re-export is what lets this conftest report a leak.
-from testsupport.hermetic import pytest_sessionfinish  # noqa: E402,F401
+from testsupport.hermetic import pytest_sessionfinish  # noqa: F401

{witan_code-0.22.0 → witan_code-0.24.0}/docs/EDGE_PRECISION_TIERS.md

@@ -35,12 +35,14 @@ up twice at two different trust levels.
 
 ```python
 TypedEdge(
-    precision,           # "precise" | "heuristic" | "fuzzy"
-    consumer_repo, provider_repo,
-    kind, key_norm,
-    canonical_symbol,     # consumer's symbol string; precise tier only, else None
-    confidence,           # 1.0 for precise; the heuristic tier's score otherwise
-    evidence,             # tuple[dict] of {repo, file, line} — see below
+    precision,  # "precise" | "heuristic" | "fuzzy"
+    consumer_repo,
+    provider_repo,
+    kind,
+    key_norm,
+    canonical_symbol,  # consumer's symbol string; precise tier only, else None
+    confidence,  # 1.0 for precise; the heuristic tier's score otherwise
+    evidence,  # tuple[dict] of {repo, file, line} — see below
 )
 ```
 

{witan_code-0.22.0 → witan_code-0.24.0}/docs/PACKAGE_MAP.md

@@ -80,7 +80,7 @@ only makes it authoritative.
 One `PackageMap` node per repo in the bridge store, keyed on the repo URI and
 overwritten on every full-repo index (merge-by-slug):
 
-```
+```text
 node PackageMap {
     slug: String @key      // canonical repo URI
     repo: String @index

{witan_code-0.22.0 → witan_code-0.24.0}/docs/STAGE2_STITCHING.md

@@ -45,10 +45,15 @@ way a written edge could.
 
 ```python
 PreciseEdge(
-    consumer_repo, consumer_symbol,
-    provider_repo, provider_symbol,
-    kind, scheme,
-    match_count, preferred, ambiguous_version,
+    consumer_repo,
+    consumer_symbol,
+    provider_repo,
+    provider_symbol,
+    kind,
+    scheme,
+    match_count,
+    preferred,
+    ambiguous_version,
 )
 ```
 

{witan_code-0.22.0 → witan_code-0.24.0}/docs/SYMBOL_FORMAT.md

@@ -13,7 +13,7 @@ the `:CALLS/heuristic` fallback.
 
 ## Format
 
-```
+```text
 {scheme}:{manager}:{package}:{version}:{descriptor}
 ```
 
@@ -35,7 +35,7 @@ never encoded (they are terminal).
 
 ### `endpoint` → scheme `http`
 
-```
+```text
 {METHOD} {normalized-path}
 ```
 
@@ -49,7 +49,7 @@ never encoded (they are terminal).
   representation, not the resource, and no consumer/provider pair would agree
   on them syntactically.
 
-```
+```text
 provider:  http:pypi:mit-learn:main:GET /api/v0/users/me
 consumer:  http:.:.:.:* /api/v0/users/me
 ```
@@ -58,7 +58,7 @@ consumer:  http:.:.:.:* /api/v0/users/me
 
 Descriptor is the variable name, verbatim.
 
-```
+```text
 provider:  env:.:mit-learn:main:MITOL_APP_BASE_URL
 consumer:  env:.:.:.:MITOL_APP_BASE_URL
 ```
@@ -69,7 +69,7 @@ The symbol identifies the package itself; the descriptor is `.`. Manager and
 package name come from the import site (consumer) or the publishing repo's
 package map / `package.json` (provider).
 
-```
+```text
 provider:  pkg:npm:@mitodl/course-search-utils:main:.
 consumer:  pkg:npm:@mitodl/course-search-utils:.:.
 ```
@@ -78,7 +78,7 @@ consumer:  pkg:npm:@mitodl/course-search-utils:.:.
 
 Descriptor is `{sub_kind}/{key_norm}` (sub_kind: `repo` | `image` | `name`).
 
-```
+```text
 provider:  svc:.:ol-infrastructure:main:repo/https://github.com/mitodl/mit-learn
 ```
 

{witan_code-0.22.0 → witan_code-0.24.0}/docs/SYMBOL_TABLE.md

@@ -93,7 +93,7 @@ bridge store predates `RepoSymbol` — the write is never blocked on it.
 
 ## Inspecting
 
-```
+```text
 witan code symbols [--repo URI] [--role exported|external] [--scheme http]
 witan code stitch [--repo URI] [--unresolved]
 ```

{witan_code-0.22.0 → witan_code-0.24.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "witan-code"
-version = "0.22.0"
+version = "0.24.0"
 description = "witan-code — tree-sitter code graph + cross-repo bridge (mounts under `witan code`)"
 readme = "README.md"
 license = "BSD-3-Clause"
@@ -18,10 +18,19 @@ dependencies = [
     # agent-config-kit by path — except there is NO `check-core-floor`
     # equivalent for this dependency, so this line is the only guard.
     # >=0.10: `witan-code setup`'s install report promises a warning when Pi
-    # lacks pi-mcp-adapter, which comes from `InstallResult.prerequisites`,
+    # cannot load MCP servers, which comes from `InstallResult.prerequisites`,
     # added in 0.10.0. witan_core's `report_install` reads it with getattr, so
     # an older resolution does not fail — it just silently drops the warning.
-    "agent-config-kit>=0.10,<1",
+    # >=0.11.1: `setup --force` passes `force` through to apply(), whose
+    # symlink guard (ConflictingPathError instead of FileNotFoundError) is
+    # new in 0.11.1. Older resolutions accept the flag but still crash on a
+    # dangling symlink. The workspace resolves by path, so no test here
+    # catches a stale floor.
+    # >=0.12: `witan-code setup --agent pi` only stops warning that
+    # pi-mcp-adapter is missing when Pi's built-in MCP will load the entry
+    # from 0.12.0. Older resolutions import and run, and print the false
+    # warning.
+    "agent-config-kit>=0.12,<1",
     # `remote`: the ADR-0005 client stack (OIDC device grant + MCP-client
     # proxy) behind `witan-code login` and the read commands' remote mode.
     # Costs nothing extra in practice — fastmcp is already required here and
@@ -157,13 +166,13 @@ dependencies = [
     # 0.38 its text never reaches the `mcp.tool_call` log line.
     #
     # ★ >=0.40 IS A BEHAVIOUR FLOOR too: `witan-code setup --agent pi` promises
-    # a warning when Pi lacks pi-mcp-adapter, and
+    # a warning when Pi cannot load MCP servers, and
     # `witan_core.cli.report_install` only prints `InstallResult.prerequisites`
     # from 0.40.0. It reads the field with getattr, so 0.39 imports and runs —
     # and silently drops the warning.
     "witan-core[cli,remote,observability,sentry]>=0.40,<1",
     "fastmcp>=4,<5",
-    "cyclopts>=4,<5",
+    "cyclopts>=4,<6",
     # [targets.<name>] override models (config.py) — also transitively pulled
     # in by fastmcp, declared explicitly since config.py imports it directly.
     "pydantic>=2,<3",
@@ -244,7 +253,7 @@ testpaths = ["tests"]
 packages = ["witan_code"]
 
 [tool.bumpversion]
-current_version = "0.22.0"
+current_version = "0.24.0"
 allow_dirty = true
 
 [[tool.bumpversion.files]]

{witan_code-0.22.0 → witan_code-0.24.0}/tests/test_branches.py

@@ -6,9 +6,8 @@ import subprocess
 
 import pytest
 
-from witan_core.omnigraph import OmnigraphConflict
-
 from witan_code import repo as repo_module
+from witan_core.omnigraph import OmnigraphConflict
 
 from .conftest import SAMPLE, requires_stack