0.8.3

Added

• Right-click a gutter icon to open the CI report. Left-click still opens the local report in a single click; when a CI report URL template is configured (Settings → Tools → Kensa), the gutter icon's right-click menu now offers "Open Local Report" and "Open CI Report", and its tooltip advertises the CI option. Previously the local/CI chooser lived only on the Alt+Enter intention menu, which devs rarely discovered, so a configured CI template appeared to do nothing — the gutter always jumped straight to the local report. KensaGutterLineMarkerProvider supplies the chooser through the gutter renderer's getPopupMenuActions(), so the fast local path is unchanged.

Fixed

• High idle CPU. KensaOutputFileWatcherStartupActivity polled for new reports by walking the entire project tree (including build/, .git, node_modules) every 5 seconds, forever — continuous filesystem I/O even when the IDE was idle. The walk existed because reports written by terminal/external test runs land under an excluded build/ dir that VFS never reports. It is replaced by three bounded layers: (1) a native file-watch (addRootToWatch) on each discovered report dir, so changes to known reports surface instantly with no polling; (2) a 3-second targeted probe of only the build/output dirs — read from the module model's excluded roots (Gradle build, Maven target) — checking the fixed report shape (<buildDir>/<reportDir>/indices.json or …/sources/<id>/indices.json) so brand-new reports appear quickly without ever walking a build dir's contents; (3) a 60-second pruned safety walk for reports in unconventional locations, which also refreshes the build-root set and prunes stale entries. Idle CPU drops to near zero while a terminal test run still updates gutter icons within ~3 seconds (instantly for already-known reports). Site-mode bundles (build/<site>/sources/<id>/) are handled across all three layers.