refactor(vscode): remove write-only browser automation state

[marius-kilocode]

What Problem This Solves

BrowserAutomationService tracked a state field with a setState transition logger. Nothing read the value: there is no getter, no consumer, and no test. It was write-only bookkeeping.

Why This Change Was Made

this.state was written at seven call sites and read only by setState itself to format the State X -> Y log line. Removing it eliminates dead state and keeps the service behavior identical.

User Impact

None. Browser automation still starts, connects, and disables exactly as before. The only removed output is a transition log line that no diagnostic flow consumed.

Evidence

rg -n 'this\.state|setState|BrowserAutomationState' packages/kilo-vscode/src packages/kilo-vscode/webview-ui packages/kilo-vscode/tests shows the only reader of the field was setState in this file; all other matches are unrelated services and test fixtures.

Diff: 1 file changed, 3 insertions(+), 26 deletions(-), net -23 lines.

Checks run from packages/kilo-vscode/:

• bun run typecheck (pass)
• bun run lint (pass)
• bun run test:unit (6133 pass, 2 skip, 0 fail)

Manual self-test in isolated VS Code: enabled Browser Automation, which spawned the Playwright MCP child process under the test backend; disabled it, which removed the process; no extension errors.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 file)

• packages/kilo-vscode/src/services/browser-automation/browser-automation-service.ts

---

_{Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0}

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