roslyn-codelens

# Roslyn CodeLens — Semantic .NET Intelligence ## Response shape All list-returning tools wrap their results in an envelope: ```json { "items": [...], "totalCount": 142, "truncated": false, "limit": 500, "summary": { ... } } ``` When `truncated` is `true`, `items` are the **top N by the tool's natural sort order** (severity-first, worst-first, by-project, etc.) — usually that's what you want. Raise `limit` only if the truncated tail matters for the task. Tools that include a `summary` aggregate: - `get_diagnostics` — `{ error, warning, info, hidden }` counts - `find_references` — `{ byProject: { name: count }, byKind: { kind: count } }` - `find_callers`, `find_attribute_usages` — `{ byProject: { name: count } }` - `search_symbols`, `find_reflection_usage` — `{ byKind: {...} }` - `find_unused_symbols` — `{ byKind: {...}, filteredOut: { testMethod, testContainer, mcpTool, generated, composition, interop } }` - `find_naming_violations` — `{ byRule: {...} }` - `get_complexity_metrics` — `{ max, avg, overThreshold, maxCognitive }` — `max`/`avg`/`overThreshold` describe whichever metric `metric` selected; `maxCognitive` is always the cognitive one - `resolve_stack_trace` — `{ byOrigin: { source, metadata, unresolved }, exceptions, skippedFrameLike }` — `skippedFrameLike` counts frame-like-but-unparseable lines (also present in items as `Kind="unknown"`) Single-object tools (`get_type_overview`, `get_symbol_context`, `apply_code_action`, etc.) are unchanged — they r...