Deep Verdicts — source_check + Phase 3

v0.12.0 — Deep Verdicts

library_docs Phase 3 plus source_check. A team release: two systems engineers worked in parallel, with briefs and reviews by the tech lead.

Added

• source_check(claim, urls?) — the 6th MCP tool: deterministic claim verification without an LLM (mechanics dissected from pi-web-access and rebuilt on our architecture). Sources → parallel dives with query=claim → passages with passage_id and sha256 hashes → verdict SUPPORTED/CONTRADICTED/UNCLEAR/MISSING-EVIDENCE with confidence; polarity markers in RU+EN with negation checks; source classes (official_docs / forum / news / blog / repo_issue, RU forums). Our edge over the reference: domain independence — a verdict backed by a single domain is capped at 0.65 and flagged (the two-independent-sources rule).
• library_docs Phase 3: (a) version — pin releases via GitHub tags (raw.githubusercontent.com/{owner}/{repo}/{tag}/README.md, trying v prefixes; docs sites get an honest "latest" note); (b) a self-growing user index BATHYS_DOCS_INDEX (~/.local/share/bathys/docs-index.json): successful search resolutions are remembered, and the next call for the same library resolves instantly with status user-index; priority seed → user-index → search; atomic writes, idempotent.
• Tests: +51 (159 OK): 28 source_check (polarity / negation / term filtering / independence / full pipeline on fakes) + 21 library_docs Phase 3 + config.
• Contracts: library_docs (phases 1–3) and source_check sections in docs/contracts/mcp-tools.md, footers in docs/contracts/output-format.md; env BATHYS_DOCS_INDEX in the tables.

Team

Scouting and briefs — tech lead; implementation — two senior systems engineers in parallel, no conflicts; spot-check reviews, documentation updates and shipping — tech lead.

---

Install: pip install bathys==0.12.0
Changelog: CHANGELOG.md