fix(jetbrains): stabilize workspace reload state

[kirillk]

What

Make JetBrains backend app reloads observable even when global app data is unchanged by adding an internal Ready revision. Keep the app SSE watcher subscribed during reloads and tighten workspace reload tests to wait for concrete mock-server side effects and provider data changes.

Why

The flaky workspace SSE test could miss a fast Loading -> Ready cycle and then wait forever because StateFlow suppresses equal Ready values. Workspace RPC subscriptions also depend on observing those reloads so they can resubscribe to fresh workspace instances after the manager clears stale state.

Notes

The Ready revision stays internal to backend state; the RPC DTO shape is unchanged.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• packages/kilo-jetbrains/backend/src/main/kotlin/ai/kilocode/backend/app/KiloAppState.kt
• packages/kilo-jetbrains/backend/src/main/kotlin/ai/kilocode/backend/app/KiloBackendAppService.kt
• packages/kilo-jetbrains/backend/src/test/kotlin/ai/kilocode/backend/workspace/KiloBackendWorkspaceTest.kt

Notes:

• Verified _events in KiloBackendConnectionService is a single persistent MutableSharedFlow created once at construction, so dropping eventWatcher?.cancel() from load() does not risk the watcher outliving/orphaning a stale event source — it correctly keeps observing the same flow across reloads, matching the stated intent.
• KiloAppState.Ready.rev is only ever constructed with an explicit value at its one production call site (setAppReady), so adding it to the data class correctly breaks StateFlow value-equality suppression for a fast Loading → Ready cycle without introducing dead paths.
• New test assertions (awaitRequestCount, rev-based first) replace polling/delay-based waits with deterministic conditions, in line with this package's integration-test guidance.
• packages/kilo-jetbrains/ is a Kilo-owned package, so no upstream fork-hygiene concerns apply; no changeset needed since this is an internal stability/test fix with no user-visible behavior change.

---

_{Reviewed by claude-sonnet-5-20260630 · Input: 32 · Output: 18.4K · Cached: 1.3M}

_{Review guidance: REVIEW.md from base branch main}