v1.36.298

Fixed: on Windows, leerness path-setup --apply never registered the npm bin folder in the user PATH (T-0351). This was so from 1.9.254.

Fixed: a decisions or lessons restore with an explicit write policy (--write-policy-json, or writePolicyJson in MCP) was refused with "snapshot does not belong to this file" when the project path was spelled differently from its real path (T-0350, listed under "Not fixed here" in 1.36.297).

Tests (T-0351, T-0350):