Your goal is to help me arrive at the most elegant and effective solution by combining two modes of thinking: 1.First-PrinciplesDeconstruction: Act like a physicist. Break down my ideas, plans, or questions to their most fundamental truths. Aggressively questionevery assumptionuntil only the core, undeniable components remain. Do not accept my premises at face value. 2. Pragmatic Reconstruction (KISS): Act like an engineer. From those fundamental truths,build the simplest, most direct solution possible. If there's a straight line,point to it. Reject any complexity that doesn't directly serve a core requirement. Always present your counter-arguments and alternative solutions through this lens.

**First-Principles+ KISS**: Questionevery assumptionaggressively, thenbuild the simplest solution from fundamental truths. If there's a straight line,take it, otherwise ask questions and gather any information necessary to determine the right path forward.

- Build:`yarn build`

- Watch mode:`yarn watch`

- Package:`yarn package`

- Lint with auto-fix:`yarn lint:fix` (always use this instead of regular lint)

-**Run all unit tests with coverage:`yarn test:ci --coverage`** (ALWAYS use this, not individual file testing)

- Integration tests:`yarn pretest; yarn test:integration`

- Full test suite:`yarn test:ci --coverage && yarn pretest && yarn test:integration`

- TypeScript with strict typing

- No semicolons (see`.prettierrc`)

- Trailing commas for all multi-line lists

- 120 character line width

- Use ES6 features (arrow functions, destructuring, etc.)

- Use`const` by default;`let` only when necessary

- Prefix unused variables with underscore (e.g.,`_unused`)

- Sort imports alphabetically in groups: external → parent → sibling

- Error handling: wrap and type errors appropriately

- Use async/await for promises, avoid explicit Promise construction where possible

- Unit test files must be named`*.test.ts` and use Vitest

- Integration test files must be named`*.test.ts` and be located in the`src/test` directory

- Avoid eslint-disable comments where at all possible - it's better to make a custom type than disable linting

Current status:**78.49% overall unit test coverage** with 405 unit tests and 69 integration tests passing.

1.**Write failing test first** - define expected behavior

2.**Implement minimal code** to make test pass

3.**Run full test suite** with`yarn test:ci --coverage`

4.**Refactor if needed** while keeping tests green

5.**Ensure backward compatibility** when modifying existing interfaces

1.**Files with <50% coverage** need immediate attention (remote.ts: 49.51%)

2.**Add incremental tests** - focus on measurable progress each session

3.**Target coverage improvements** of 5-15 percentage points per file

4.**ALWAYS use`yarn test:ci --coverage`** - never test individual files

5.**Ignore coverage for test-helpers.ts** - this is a test utility file containing mock factories and helper functions

-**Use mock factories from test-helpers.ts** - 30+ factory functions available for all common types

-**No inline mock definitions** - always use factory functions for consistency

-**Minimal`as any` usage** - reduced from 95 to 4 instances (96% reduction)

-**Use createMockOutputChannelWithLogger()** for consistent Logger testing

-**Mock external dependencies** properly using vi.mock() with TypeScript types

-**Test core functionality first** - constructor, main methods, error paths

-**Ensure backward compatibility** by adding compatibility methods during refactoring

-**Group related tests** in describe blocks for better organization

exportfunction createMockStorageWithAuth():Storage

exportfunction createMockStorageMinimal():Storage

exportfunction createMockWorkspaceRunning():Workspace

exportfunction createMockWorkspaceStopped():Workspace

exportfunction createMockWorkspaceFailed():Workspace

exportfunction createMockExtensionContext():vscode.ExtensionContext

exportfunction createMockRemoteSSHExtension():vscode.Extension<unknown>

exportfunction createMockTreeView<T>():vscode.TreeView<T>

exportfunction createMockStatusBarItem():vscode.StatusBarItem

exportfunction createMockQuickPick<T>():vscode.QuickPick<T>

exportfunction createMockTerminal():vscode.Terminal

exportfunction createMockOutputChannel():vscode.OutputChannel

exportfunction createMockWorkspaceProvider():WorkspaceProvider

exportfunction createMockRemote():Remote

exportfunction createMockCommands():Commands

exportfunction createMockEventEmitter<T>():vscode.EventEmitter<T>

exportfunction createMockAxiosInstance():AxiosInstance

exportfunction createMockProxyAgent():ProxyAgent

exportfunction createMockUri(path:string,scheme?:string):vscode.Uri

yarn lint:fix# Lint with auto-fix

yarn test:ci --coverage# Run ALL unit tests (ALWAYS use this)

yarn pretest&& yarn test:integration# Integration tests

###FileswithExcellentCoverage (>90%)-UseasExamples:

-featureSet.ts:100%

-proxy.ts:100%

-logger.ts:98.44% (goodTDDexample)

-sshSupport.ts:98.13%

-util.ts:97.31%

-headers.ts:96.49%

-api-helper.ts:96.36%

-sshConfig.ts:96.21%

-api.ts:95.52%

-extension.ts:93.07% (refactoredfrom39.71%usingTDD)

-workspaceMonitor.ts:92.37%

-error.ts:90.44%

-cliManager.ts:90.05%

###CurrentDevelopmentApproach

-**TDDfornewfeatures**-testfirst,implementsecond

-**Incrementalrefactoring**-small,measurableimprovements

-**Comprehensivemockfactories**-30+factoryfunctionsintest-helpers.ts

-**Type-safetesting**-minimal`as any`usage (only4instancesremain)

###RefactoringStrategy

-**TypeScript strict mode**, no semicolons, 120 char lines

-**Test files**:`*.test.ts` (Vitest for unit, VS Code API for integration)

-**Use test-helpers.ts**: 30+ mock factories available - NEVER create inline mocks, instead create a new factory in that file and import it

-**TDD always**: Write test → implement → refactor

-**Never use any**: Always try to use at least a decently close Partial type or equivalent

-**Never delete tests**: Only delete or skip tests if directly asked, otherwise ask the user for help if fixing the tests does not work.

###Example:TDDRefactoringPattern (extension.tssuccessstory)

1. Use`yarn test:ci --coverage` before and after EVERY change

2. Import factories and mocks from test-helpers.ts (createMock* and*Factory)

3. Write a test, make sure it fails, and only then make it pass

4. Use proper types, NEVER use eslint-disable to make mocks work

5. If mocking is too complicated, consider whether the function under test needs a minor refactoring that passes existing tests first, to make it easier to test.