| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(test): skip POSIX chmod assertion on Windows in key-crypto Same platform issue as PR #100: fs.statSync().mode & 0o777 returns 0o666 on Windows regardless of the mode passed to writeFileSync, because Windows file ACLs don't map cleanly to POSIX mode bits. Production src/security/key-crypto.ts still writes with { mode: 0o600 } — harmless no-op on Windows, correct on POSIX. Wrap the assertion with it.skipIf(process.platform === 'win32') so it runs unchanged on POSIX (still fails if encryptToFile drops mode: 0o600) and skips cleanly on Windows. Strict expect(mode).toBe(0o600) is kept under the skip so a regression that flips 0o600 to 0o644 still trips the test on POSIX. | 3 个月前 | |
fix: honor WIGOLO_LLM_API_KEY for explicit provider (#102) The TUI writes WIGOLO_LLM_API_KEY and tells users to set it alongside WIGOLO_LLM_PROVIDER, but the runtime key resolver only read the provider-specific vars, so gemini/openai/etc. users fell back to heuristic synthesis. Honor WIGOLO_LLM_API_KEY as a last-resort env fallback, gated on WIGOLO_LLM_PROVIDER explicitly naming the provider so auto-detect stays unambiguous and the provider-specific var still wins. | 3 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 个月前 | ||
| 3 个月前 |