v0.8.2

Added

• Solution scope warning. csmesh doctor and csmesh index now say when a solution
  file was found but did not fully decide which projects are indexed: some listed project
  paths match nothing on disk, none do, the solution lists no project, or it cannot be read.
  The line names the solution, how many of its paths matched, and the first one that did
  not, as written in the file:

  solution        App.slnx: 2 of 3 project path(s) matched on disk (first unmatched: src/Old/Old.csproj)
  

  When the result was a fallback to the ProjectReference closure, the line says so. Before
  this, the fallback was silent. --json carries the same data as solution_findings on
  both reports; the field is new, no existing field changed, and exit codes are unchanged.

Fixed

• Spurious incremental run after the first index. In a repository where the solution
  leaves some projects out of scope, the run after a first full index could come back
  incremental instead of current. Two causes, both fixed: the index created its own
  .csmesh/ directory after stamping the repository root, so it moved the stamp it checks
  next time; and the new-file check walked out-of-scope projects and reported their files as
  new. Nothing out of scope ever entered the graph; the cost was one needless rebind.

Upgrade

dotnet tool update -g CsMesh
npm i -g @nrafinia/csmesh

The graph format is unchanged (v14); existing indexes load as they are.

---

📦 Installation & Upgrades

Global .NET Tool

dotnet tool update --global CsMesh

Automatic One-Line Install Script

Linux & macOS:

curl -fsSL https://raw.githubusercontent.com/nRafinia/CsMesh/main/install.sh | sh

Windows (PowerShell):

irm https://raw.githubusercontent.com/nRafinia/CsMesh/main/install.ps1 | iex

Quick Setup for AI Assistants

# Install skills and register MCP server in one command:
csmesh install -g --all
csmesh index --full