Lightpath 0.1.2

npx @lightpath-dev/cli init --agent claude-code   # or: cursor, vscode, kiro

Fix: resolve false-positive line attribution in un-taken else-if/switch branches and post-throw statements.

0.1.1 could show lines as run that did not run. 0.1.2 fixes that. Needs Node.js 22.12 or newer, as before.

Packages

Package	Version
@lightpath-dev/protocol, core, daemon, mcp, cli	0.1.2
@lightpath-dev/browser	stays 0.1.1
@lightpath-dev/node-agent	stays 0.1.0
VS Code extension, lightpath-agent (PyPI)	unchanged

Fixed

• A line that holds only }, ), ; or a trailing comment no longer takes the count of the code around it. These showed as run when they did not run: an untaken } else if (…) {, the body and break; of an untaken case or default:, and the untaken arm of a multi-line ternary or && (D-149).
• Lines after a call that threw are shown as unknown, naming the line that threw. Before, they showed as run. V8's coverage has no count for them, so Lightpath does not claim either way (D-153).
• Lines that hold only a comment have no count. Loop headers show the loop's count. An untaken catch shows 0.

Tests

• pnpm accuracy runs fixture apps (Node, Vite + React) and compares every line against hand-written expected results.
• packages/core/test/accuracy.test.ts: regression tests for each case above. 5 of its 6 fail on 0.1.1's code and all pass on 0.1.2.

Decisions: D-149, D-153, D-154. Full list: CHANGELOG.