v0.1.5

• fix(pi): start the guard as node <bundled runner> by default — createPiExtension() used to default to the bare gitflow-guard command, which Windows cannot start without a shell (extension-less npm shim or .cmd), so the spawn error was swallowed by the fail-open path and the extension silently stopped guarding (verified on Windows 2026-10-06); resolvePiBin() now returns [process.execPath, resolveRunnerPath()], GITFLOW_GUARD_BIN still overrides it, and the verification matrix asserts the default and runs a real CLI round-trip without injecting bin/run —— Pi 扩展默认执行器改为 node <随包 runner>：此前默认走 PATH 上的 gitflow-guard，而 Windows 不带 shell 无法启动无扩展名 shim 或 .cmd，spawn 失败被降级路径吞掉，守卫静默失效（2026-10-06 Windows 实测）；现 resolvePiBin() 返回 [process.execPath, resolveRunnerPath()]，GITFLOW_GUARD_BIN 仍可覆盖，复测矩阵改为不注入 bin/run 直接验证默认执行器并实弹跑一次真实 CLI。
• docs(pi): document user-level wiring — the 11 READMEs, the Pi protocol reference, the wire --client pi guidance and the shipped extension header now describe the user-level install (~/.pi/agent/extensions/ + ~/.pi/agent/settings.json + the package installed inside ~/.pi/agent, PowerShell junction on Windows) and state that no PATH entry or global npm install is needed —— Pi 用户级接线补进文档：11 语言 README、Pi 协议参考、wire --client pi 引导与随包扩展头部说明均补上用户级安装三条（~/.pi/agent/extensions/ + ~/.pi/agent/settings.json + 在 ~/.pi/agent 内安装本包；Windows 用 PowerShell junction），并写明不依赖 PATH 与全局 npm 安装。
• docs: drop the remaining section signs in source comments and test names (17 occurrences) — the same replacement as 0.1.4, applied to .ts / .mjs comments and the dogfood extension header; the only remaining "§" is the literal one quoted in the 0.1.4 changelog entry itself —— 补清源码注释与测试名里的章节符号（17 处）：与 0.1.4 同一替换规则，覆盖 .ts / .mjs 注释与 dogfood 扩展头部；现在唯一剩下的 "§" 是 0.1.4 条目里描述本次清理时引用的那个字面符号。