Skip to content

v0.11.0

Latest

Choose a tag to compare

@github-actions github-actions released this 14 Jul 03:58
· 4 commits to main since this release

[0.11.0] - 2026-07-14

New Features

  • zcodegraph status and zcodegraph doctor now share graph health language, so users and scripts can distinguish healthy, degraded, stale, failed, unavailable, and corrupted indexes with exact next-step commands.
  • rust-hybrid indexing now handles C baseline symbols through the Rust-owned path, so C functions, structs, enums, typedefs, includes, and calls no longer depend on TypeScript fallback extraction.
  • rust-hybrid indexing now handles Java baseline symbols through the Rust-owned path, so Java classes, interfaces, annotations, enums, imports, and method calls no longer depend on TypeScript fallback extraction.
  • rust-hybrid indexing now preserves Python decorator relationships through the Rust-owned path, so decorated Python functions and methods can appear in graph impact and traversal results.
  • rust-hybrid indexing now understands Python calls, imported names, and module-level values, so Python search, callers/callees, and file dependents work through the Rust indexer.
  • zcodegraph status now shows decision-ready rust-hybrid fallback diagnostics, including top reason groups, graph usability, the exact doctor command, and the privacy-preserving bundle artifact to share with maintainers. (#668, #669, #670)

Fixes

  • MCP ToolHandler now lazily recovers from corrupted SQLite databases instead of crashing, so agents get a clear error and retry path instead of a hard failure. (#679)
  • rust-hybrid fallback health now reports a three-tier state (healthy / partial / degraded), so users can tell at a glance whether the graph is fully usable or partially degraded. (#682)
  • zcodegraph doctor --engine rust-hybrid --bundle can now create a local diagnostic bundle for a corrupted graph database without opening the broken database or collecting source paths. (#671)
  • zcodegraph doctor --engine rust-hybrid --bundle --last-run now points degraded fallback reports to the per-file diagnostic artifact and next maintainer handoff step instead of leaving users at the bundle path alone. (#669, #670)