deps(knip): configuring knip and removing dead code

[roomote]

Related to: #519

What problem this solves

Knip was only configured to detect unused files and dependencies. This extends the configuration to also catch unused exports, enum members, duplicate exports, and types — surfacing dead code that was previously invisible to static analysis.

What changed

Knip configuration (knip.json)

• Added rules for exports, types, enumMembers, nsExports, nsTypes, and duplicates at warn level (non-blocking, exit 0)
• Set classMembers: off (too noisy for the current codebase)
• Added ignore for eslint.config.mjs and scripts/** in apps/cli to fix graph traversal after the sdk directory was removed

Dead code removed

• apps/cli/src/agent/extension-host.ts: removed dead user: null field from ExtensionHostOptions interface and all callers (App.tsx, useExtensionHost.ts, Header.tsx, list.ts, run.ts, extension-host.test.ts)
• apps/cli/scripts/build.sh and .github/workflows/cli-release.yml: removed stale @trpc/client and superjson entries from release package.json construction (dependencies were already removed)
• packages/types/src/task.ts: deleted TaskStatus.None enum member (zero callers)
• webview-ui/src/components/ui/select-dropdown.tsx: deleted DropdownOptionType.ITEM enum member (never referenced)
• src/core/tools/EditTool.ts: deleted searchAndReplaceTool alias
• src/core/tools/SearchAndReplaceTool.ts: deleted (re-exported only the now-deleted alias)
• src/core/tools/__tests__/searchAndReplaceTool.spec.ts: deleted (tested the now-deleted alias)
• src/api/providers/lm-studio.ts: deleted private getLmStudioModels function (never called, shadowed by a same-named local function in useLmStudioModels.ts)
• packages/build/src/types.ts: deleted 5 unused type X = z.infer<typeof xSchema> aliases
• packages/vscode-shim/src/types.ts: removed 4 unexported unused interfaces (TextDocument, WorkspaceFolder, WorkspaceConfiguration, CancellationToken)

Formatting

• Removed trailing blank lines from 7 files flagged by git diff --check

[roomote]

No actionable issues found. See task

• resolvePathInWorkspace() now resolves brand-new files into the only workspace root that already contains the parent directory, so create flows no longer fall back to the first root in that case.
• Secondary-root .rooignore content is now loaded for execute_command and the prompt instructions instead of staying pinned to this.cwd.
• e2e-mock is still red on the current head: the multi-root repro times out after 60s, so CI still is not proving that the second workspace folder becomes available under GitHub Actions. — moved to sibling PR #228 after splitting the product fix from the VS Code e2e harness work.
• validateCommand() no longer skips Windows absolute paths, so validateAccess() still runs for secondary-root C:\\... arguments.
• src/core/tools/__tests__/writeToFileTool.spec.ts now uses an explicit platform-aware in-root diff-path expectation, which matches the remaining Windows failure on f455a8e73 instead of feeding the assertion back through mocked path.resolve.
• src/core/tools/__tests__/applyPatchTool.execute.spec.ts now matches the actual diff-path behavior on Windows instead of assuming the Linux-only in-root path shape.
• src/core/tools/__tests__/listFilesTool.spec.ts, src/core/tools/__tests__/searchFilesTool.spec.ts, and src/core/tools/__tests__/applyDiffTool.spec.ts now directly cover the remaining multi-root path-resolution surfaces that were still missing from the patch.
• platform-unit-test (ubuntu-latest) passed on 8a98d562f88b720eb86f84ec58e2d7b11dcb1993 after the bounded wait.
• platform-unit-test (windows-latest) passed on 8a98d562f88b720eb86f84ec58e2d7b11dcb1993 after the bounded wait.

[roomote]

Pushed d4df00b6e on #225.

What changed:

• fixed the remaining Windows-only expectation mismatch in writeToFileTool.spec.ts by making the in-root diff-path expectation explicit per platform instead of routing it back through the mocked path.resolve
• kept the patch scoped to the one spec file that still matched the old f455a8e73 failure log

Validation:

• pnpm --dir src exec vitest run core/tools/__tests__/writeToFileTool.spec.ts
• pnpm --dir src exec vitest run core/tools/__tests__/writeToFileTool.spec.ts core/tools/__tests__/applyPatchTool.execute.spec.ts core/tools/__tests__/listFilesTool.spec.ts core/tools/__tests__/searchFilesTool.spec.ts core/tools/__tests__/applyDiffTool.spec.ts
• pnpm --dir apps/web-roo-code test

Visual proof: not applicable for this change because it only updates backend/tooling test coverage.

CI is rerunning now on d4df00b6e. On the previous head f455a8e73, codecov/patch was already green; this push is specifically to clear the remaining platform-unit-test (windows-latest) failure.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[roomote]

I see some merge conflicts here. Working on them now...

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

This PR has merge conflicts that need to be resolved.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

This PR has merge conflicts that need to be resolved.

[roomote]

This PR has merge conflicts that need to be resolved.

[roomote]

This PR has merge conflicts that need to be resolved.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

This PR has merge conflicts that need to be resolved.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

This PR has merge conflicts that need to be resolved.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

This PR has merge conflicts that need to be resolved.

[roomote]

This PR has merge conflicts that need to be resolved.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

This PR has merge conflicts that need to be resolved.

[roomote]

I detected merge conflicts but could not start a task to address them.

[roomote]

This PR has merge conflicts that need to be resolved.

[roomote]

I detected merge conflicts but could not start a task to address them.

[edelauna]

Reusing PR to fix knip config - will address findings in a separate PR