v0.5.2

Two real bugs in the analysis core, both found by running this project's own predict_failures over its src/core/, and both missed by the test suite.

Fixed

A model verdict was thrown away when the reply had prose after it. The end of the JSON was located with lastIndexOf, so commentary containing a } or ] — "the guard at if (a) { return; } already covers it" — moved the cut past the reply and a correct, confident finding was reported as unknown. The end of the value is now found by scanning forward with depth tracking, string- and escape-aware.

export default foo; sent the model const foo = foo instead of the function. An identifier naming a declaration made earlier in the file fell through to the range covering the identifier itself, so the callee excerpt spent tokens to say a function is itself — inside the feature that exists to make the model more accurate. It now resolves through the same alias path a named export uses.

A third report from the same sweep was a false positive and was correctly not acted on: rank() guarantees the finding list is never empty, on a path the model could not see from one module away.

Also in 0.5.x

• scan_project no longer ranks test files (includeTests to opt back in)
• The MCP server ships a fix-verification rule as instructions plus an onFix hint
• README has a beginner primer; the benchmark report defines its terms before using them
• Code contributions are closed for now; bug reports are open and wanted

Full detail in CHANGELOG.md.