Scope provider profiles to custom storage paths - #2305

Related GitHub Issue

Closes: #2303

Description

This PR scopes provider profiles to the configured custom storage path. It supports the Reliability First goal by keeping profiles separate across custom storage scopes.

When the setting is empty, the manager uses the existing global SecretStorage key. This preserves current behavior for users who do not set a custom path.

When the setting has a value, the manager normalizes the path and uses its hash to select a separate SecretStorage key. Provider profiles remain in VS Code SecretStorage. The custom path does not store them as files.

On first use of a scope, the manager copies the legacy profile only if no scoped profile exists. It keeps the legacy entry. Existing scoped profiles take precedence. The manager continues to use the existing load and store flows.

The manager reads the setting when it starts. Reload the extension after changing the path.

Test Procedure

Run the provider profile tests:

pnpm --dir src exec vitest run core/config/__tests__/ProviderSettingsManager.spec.ts

Result: 68 tests passed.

Run the TypeScript check:

pnpm --dir src run check-types

Run ESLint on the changed files:

pnpm --dir src exec eslint --prune-suppressions --max-warnings=0 core/config/ProviderSettingsManager.ts core/config/__tests__/ProviderSettingsManager.spec.ts

Run both dead-code checks:

pnpm knip

pnpm knip:production

Both Knip checks passed.

These checks ran with Node v24.22.2. The repository requests Node v22.23.4, so pnpm reported an engine warning.

The full test suite did not pass on main in this environment. Dist asset tests reported missing generated assets. Checkpoint tests hit the GIT_MERGE_AUTOEDIT environment guard.

Pre-Submission Checklist

• Issue Linked: Confirm issue Support workspace-scoped API provider profiles and settings across VS Code windows #2303 is approved and assigned.
• Scope: This change focuses on provider profile storage for issue Support workspace-scoped API provider profiles and settings across VS Code windows #2303.
• [x ] Self-Review: Review the final changes before submission.
• Writing Style: This description uses short sentences and plain words.
• Testing: Tests cover default storage, scoped storage, migration, and reset behavior.
• Test Helpers: Shared helpers handle mechanical setup. Scenario-specific behavior remains visible.
• Visual Snapshot: This change does not affect the UI.
• Documentation Impact: No separate documentation update is required.
• [x ] Contribution Guidelines: Confirm that you read and agree to the Contributor Guidelines.

Visual Snapshots

Not applicable. This PR does not change the UI.

Videos (interaction / animation only)

Not applicable. This PR does not change an interactive UI flow.

Documentation Updates

• No documentation updates are required.
• Yes, documentation updates are required.

Additional Notes

AI tools assisted with implementation and test updates.