fix(cli): use Kilo cache for npm packages#9581
Conversation
| Layer.provide(EffectFlock.layer), | ||
| Layer.provide(AppFileSystem.layer), | ||
| Layer.provide(Global.layer), | ||
| Layer.provide(kilo), |
There was a problem hiding this comment.
WARNING: Kilo-specific change is outside the annotation block
This line is the actual default-layer switch from the shared opencode global paths to Kilo paths, but it is not covered by a kilocode_change marker. The opencode annotation check scans added lines in shared packages/opencode files, so this and the related unmarked changed lines will fail CI unless they are covered by an inline marker or surrounding block.
| import { describe, expect, test } from "bun:test" | ||
| import { Npm } from "../src/npm" | ||
| import { tmpdir } from "./fixture/fixture" | ||
| import { Global } from "../src/global" |
There was a problem hiding this comment.
WARNING: Kilo-specific test changes need annotation coverage
packages/opencode/test/npm.test.ts is a shared opencode test file, and the added import plus regression test are Kilo-specific. The opencode annotation check will flag these added lines unless they are covered with kilocode_change markers.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (3 files)
Reviewed by gpt-5.5-20260423 · 397,782 tokens |
980b8a1 to
17048fa
Compare
Summary