PolyCodeGraph v0.6.0 — Compact MCP responses and targeted exploration

PolyCodeGraph v0.6.0 — Compact MCP responses and targeted exploration

Version 0.6.0 reduces response volume for coding agents while preserving semantic
provider evidence, stable symbol IDs, query depth and explicit pagination/limits.
All ten language providers and the sixteen MCP tool names remain available.

• Opt-in compact profile: configure response_profile: compact or launch
  serve --response-profile compact. Legacy remains the default; every tool accepts
  detail: full to retrieve its legacy response and defaults.
• Paged health details: compact status/index summaries expose freshness,
  coverage, counts and diagnostics. Use status.section for diagnostics, skipped
  files, providers, update lists, metrics or architecture; omitted results are visible.
• Targeted exploration: compact search defaults to 10 rows, relations to 20,
  architecture to 5 and implicit snippets to 30 lines. Explicit requests retain
  existing hard budgets. Invalid indexed file prefixes produce a warning and a
  unique root-relative suggestion when available, never a silent correction.
• Index consistency: independent health identity, same-generation diagnostic
  refresh, effective configuration hashing and guarded publication on config races.
• Metrics and harness guidance: per-tool calls/errors/response bytes, targeted
  consumer instructions, response replay tooling and token-accounting validation.

Native downloads

Rust is not needed to run the packages. Keep the executable beside providers/;
selected semantic providers still require the runtimes/SDKs documented in README.

Platform	Archive
Linux x64	polycodegraph-0.6.0-linux-x64.tar.gz
Windows x64	polycodegraph-0.6.0-windows-x64.zip
macOS Intel	polycodegraph-0.6.0-macos-x64.tar.gz
macOS Apple Silicon	polycodegraph-0.6.0-macos-arm64.tar.gz

Verify downloads using the attached SHA256SUMS.

Upgrade and rollback

Replace the executable/provider package and restart MCP. Existing graph
configuration and tool arguments remain compatible. A cache from 0.5 may
reconcile/rebuild once because graph configuration inputs now hash effective
options. Profile/formatting edits to existing config files subsequently retain
semantic identity. Enable compact explicitly; remove the override or set
response_profile: legacy to restore legacy presentation. See the
response contract and
consumer harness.

Validation and limits

Local Linux verification: format, Clippy with warnings denied, 39 Rust tests,
four Python accounting tests and real stdio profile checks. Native differential
checks against 0.5 covered ten languages (185 symbols/419 edges), Dart (37/99),
real Flutter (24/75), Android SDK (5/6) and TypeScript without Dart on PATH.
All 20 cross-platform CI jobs passed, including Windows/macOS/Linux core checks,
Flutter, Android SDK, macOS UIKit and relocated-package smoke checks for all four targets.
Validated release commit and CI run.

Deterministic replay of the recorded Flutter MCP calls reduced response bytes by
44.96% and 50.87%. The tool schema grew 14.9%; some small query responses
also grow to retain health and omission metadata. These are response measurements,
not measured AI-token savings or whole-task speedups. The six fresh A/B/C
executor runs and their token/correctness gates remain pending. Compact therefore
remains opt-in. Detailed measurements.

Static dispatch, dynamic/cross-language omissions and platform SDK requirements
remain unchanged. Smaller output does not reduce stored semantic evidence, and
coverage/truncation must still be checked before drawing conclusions.