[ViperJuice]

Contents since 1.5.1

Prepared minor release index-it-mcp 1.6.0, from main at c2a3451. Full detail is in CHANGELOG ## [1.6.0] - 2026-11-09.

• feat: port to the mcp 2.x SDK; grammar prefetch retries; pilot grammar cache; serverInfo version (#124, #128, #127, #131) #132: port to the mcp 2.x SDK (Port to the mcp 2.x SDK (co-install with pmcp 3) #124), with STDIO initialize reports the mcp library version instead of the package version #128, grammars prefetch: retry transient GitHub download failures (CI failed on 504) #131 and PMCP pilot: pass a prefetched grammar cache to the fixture (offline acceptance blocked) #127:
  • requires mcp>=2.2,<2.4 (locked at 2.3.0) and adds jsonschema as a direct dependency;
  • a repo-owned Tasks runtime replaces the removed SDK Tasks API: task-augmented reindex and write_summaries, plus tasks/get|result|list|cancel;
  • a tools/call validation adapter keeps the 1.x input validation and isError results;
  • serverInfo.version is now the package version (STDIO initialize reports the mcp library version instead of the package version #128);
  • grammars prefetch retries transient download failures (grammars prefetch: retry transient GitHub download failures (CI failed on 504) #131);
  • the PMCP pilot gets a prefetched grammar cache (PMCP pilot: pass a prefetched grammar cache to the fixture (offline acceptance blocked) #127).
• fix(mcp): task retention floor, drop malformed responses, clearer capacity error (#132 re-check nits) #135: re-check fixes for feat: port to the mcp 2.x SDK; grammar prefetch retries; pilot grammar cache; serverInfo version (#124, #128, #127, #131) #132. Task-retention floor and 256-task capacity with a clear refusal message; malformed STDIO lines get JSON-RPC errors and malformed responses are dropped; test isolation fix.
• fix(watcher): sweep only what the indexer stores; ignore non-indexable files in incremental sync (#114, #111) #129: watcher sweep and incremental sync (Watcher sweep treats never-indexed files as drift and triggers a full rebuild every hour #114, Incremental repository sync fails when a commit changes files in a disabled language (e.g. YAML) #111). The sweep, full walk and single-file indexing share one admission predicate, so sweeps no longer force hourly rebuilds. Incremental sync handles non-indexable files. Generation retention is bounded. Plugin worker memory is released.
• fix(storage): keep a generation whose semantic directory survives removal; #114 docs follow-ups #130: generation-retention follow-ups. A generation whose semantic directory survives removal is kept; Watcher sweep treats never-indexed files as drift and triggers a full rebuild every hour #114 retry and failed-generation retention are documented.

This PR:

• bumps the version to 1.6.0 in the same places release: 1.5.0 #118 and release: 1.5.1 (cap mcp<2) #125 did: pyproject.toml, __version__, the project's uv.lock entry (uv lock --check passes), the Release Automation default, both Docker installers, the release docs and the release-gate tests;
• turns [Unreleased] into [1.6.0] - 2026-11-09 (sections Changed / Fixed / Upgrade notes / Known follow-ups, with an empty [Unreleased] kept on top);
• updates README, GETTING_STARTED, MCP_CONFIGURATION, SUPPORT_MATRIX, v13-release.md and public-package-identity.md:
  • 1.6.0 is the prepared candidate;
  • 1.5.1 is published with partial delivered acceptance (wheel and image passed; PMCP offline, rehearsal and browser not run);
  • 1.3.0, 1.3.1, 1.4.0, 1.4.1 and 1.5.0 are yanked. Checked on PyPI 2026-11-09. 1.2.0 and its RCs also declare an unbounded mcp and are not yanked; this is recorded in public-package-identity.md and needs an owner decision;
• updates the docs tests that pin the wording to that state. PUBLISHED_VERSION = "1.5.1" stays; YANKED_VERSIONS replaces UNBOUNDED_MCP_VERSIONS. The docs must say "prepared candidate", "Published 1.5.1", "partial", "yanked" and mcp>=2.2,<2.4, and must tell users to remove any mcp<2 pin;
• guards STDIO initialize reports the mcp library version instead of the package version #128 in release smoke: the raw JSON-RPC initialize probe now requires serverInfo.version to equal the installed index-it-mcp version. The new contract test fails when a server reports the mcp library version (2.3.0).

Upgrade notes (from the CHANGELOG)

• mcp 2.x is required (>=2.2,<2.4). Drop any mcp<2 pin installed next to index-it-mcp (the workaround for 1.4.1/1.5.0, and what 1.5.1 requires); it makes the install unresolvable.
• Co-installs with PMCP 3.x and phase-loop-runtime==0.7.30 with a clean uv pip check. 1.5.1 could not.
• Claude Code negotiates protocol 2026-07-28, which has no Tasks: task metadata is ignored, calls run synchronously, and tasks/* answer -32601. Tools, schemas and results do not change. Clients that negotiate 2025-11-25, such as ClientSession and the PMCP 3.x gateway, keep Tasks.
• The cap moves one mcp minor at a time. Each new minor is re-tested before the cap is widened, because the Tasks runtime depends on the provisional Server.middleware.
• Generation retention is automatic (live, plus MCP_INDEX_GENERATION_RETENTION default 2, plus the newest failed generation). Pre-upgrade generations are never pruned automatically.
• Hosts that set a long MCP_WATCHER_SWEEP_MINUTES as a Watcher sweep treats never-indexed files as drift and triggers a full rebuild every hour #114 workaround can return to the default. Re-run PMCP pilot prepare to get grammar_cache.
• Known follow-ups:
  • PMCP pilot: move from pmcp 2.7.3 to 3.x and re-run offline/rehearsal acceptance #133: move the PMCP pilot from pmcp 2.7.3 to 3.x;
  • Delete unported legacy scripts (patch_mcp_server.py, scripts/cli servers) #134: delete the unported legacy scripts;
  • Plan a first semantic build and retire legacy Qdrant collections #121: first semantic build and legacy Qdrant retirement;
  • Per-language degradation when a tree-sitter grammar is unavailable #117: per-language grammar degradation.

Packaging and co-install (dev0, fresh Python 3.12.14 venvs, --no-config --resolution highest)

uv build produced index_it_mcp-1.6.0-py3-none-any.whl (f75278ad…52bbe4df) and index_it_mcp-1.6.0.tar.gz (64c08dcc…95861242). The wheel declares Requires-Dist: mcp<2.4,>=2.2 and jsonschema>=4.20.0.

Venv	Resolved	uv pip check	index-it-mcp --version	STDIO initialize + tools/list
(a) wheel alone, unconstrained	mcp 2.3.0, jsonschema 4.26.0, baml-bridge 0.23.0, tree-sitter 0.26.1, treesitter-chunker 6.0.0	clean	version 1.6.0	passed: serverInfo.version 1.6.0, protocol 2025-06-18, 8 tools
(b) wheel + pmcp>=3,<4	mcp 2.3.0, pmcp 3.0.3 (mcp>=2.2,<3)	clean	version 1.6.0	passed: serverInfo.version 1.6.0, 8 tools
(c) wheel + phase-loop-runtime==0.7.30	mcp 2.3.0, baml-bridge 0.23.0, tree-sitter 0.26.0	clean	version 1.6.0	passed: serverInfo.version 1.6.0, 8 tools

In every venv, grammars prefetch verified 47/47 grammars into a fresh private cache (tree-sitter-language-pack 1.20.0).

release_smoke.py --wheel --stdio --unconstrained on head 4fb4a2d passed, with a freshly prefetched grammar cache (47/47) and MCP_REQUIRE_GRAMMARS=1:

• locked: source contract (431 files), schema, prepare, Python client, two STDIO query sessions, installed lifecycle and safety probe;
• unconstrained: mcp 2.3.0 and openai 3.48.0 resolved; initialize reported serverInfo.version 1.6.0 with 8 tools; two STDIO query sessions passed;
• both ran on one wheel (18717a87…bc71587e2).

Tests run (dev0, serial, nice, one file per invocation, no xdist)

Load (~1–2 on 24 cores), memory and I/O pressure were checked first. 75 files, no failures, all on Python 3.12:

• all 66 tests/docs/test_*.py files, including p23 doc truth, p8, p26, pubname public docs and the identity contract;
• tests/test_release_notes.py: 4 passed
• tests/test_release_metadata.py: 27 passed
• tests/smoke/test_release_smoke_contract.py: 31 passed
• tests/test_p25_release_gates.py: 7 passed
• tests/test_requirements_consolidation.py
• tests/test_workflow_release_policy.py: 42 passed
• tests/test_localci_workflow_posture.py: 5 passed
• tests/test_p26_alpha_evidence.py: 6 passed
• tests/test_v13_pmcp_pilot.py: 167 passed, 1 skipped

black, isort and flake8 are clean on the changed Python files. The full suite was not run on dev0; hosted CI covers it.

Remaining publish steps (each needs owner approval)

1. [owner approval] Merge this PR on its accepted head after green CI and review.
2. [owner approval] Collision check. Confirm that PyPI index-it-mcp==1.6.0, the GitHub release and tag v1.6.0, refs/tags/release-claims/v1.6.0 and the GHCR candidate image do not exist or are partial. Record the merge commit and tree.
3. [owner approval] Single dispatch of Release Automation with mode=publish, version=v1.6.0, auto_merge=false, expected_commit=<merge sha>, expected_tree=<accepted tree>, --ref main. Never redispatch after a partial failure (see the Publication Gate in docs/operations/v13-release.md).
4. [owner approval] Delivered acceptance of the registry artifacts:
   • release_smoke.py --wheel-path <PyPI wheel> --wheel-sha256 <registry sha256> --unconstrained --image-ref <ghcr>@sha256:<digest> with a prefetched grammar cache;
   • a plain pip install index-it-mcp==1.6.0, with and without pmcp 3.x and phase-loop-runtime==0.7.30: uv pip check, plus serverInfo.version 1.6.0;
   • PMCP pilot prepare and offline. The pilot still uses pmcp 2.7.3 (PMCP pilot: move from pmcp 2.7.3 to 3.x and re-run offline/rehearsal acceptance #133).
5. [owner approval] Post-release docs PR recording the published state and acceptance of 1.6.0, like docs: record published index-it-mcp 1.5.0 (delivered acceptance partial) #123 and docs: record published index-it-mcp 1.5.1 (wheel and image accepted; PMCP offline, rehearsal and browser not run) #126.

No tag, dispatch, publish, yank or merge was done in this PR.

🤖 Generated with Claude Code

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-10T00:03:11.224492Z	4fb4a2d	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.