Will Lo

fix(amazonq): downloadExportResultAcrchive api not passed with profileArn and cause 400 error (#7022) ## Problem The CreateUploadUrl and StartTestGenerationJob requests succeeded with the profile ARN attached. However, the ExportResultArchive requests were made without this profile ARN, leading to inconsistent profile resolution between operations. ## Solution --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

feat(amazonq): profileManager implementation (#2102) ## Problem add `ProfileManager`, a component manages Q Profile (for idc users only for now) A Q Profile has the following info - Q service region - Q service endpoint - Arn - Account - ProfileName major API - getActiveProfile - listAvailableProfiles Functionalities - `getActiveProfile`: return the current selected profile within current workspace - `switchProfile`: switch profile of current workspace to the provided profile. Note that users are "ALLOWED" to select different profiles in different VSCode instances. - `persistence`: Q should memorize "last" selected option so that users don't have to be prompted to select profile everytime - `getServiceClientConfig`: as said above, profile will also affect the service endpoint, thus `ProfileManager` will be as the single source of true to retrieve Q related service endpoint onward. ## Solution --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

feat(amazonq): show all customizations across different profiles (#7060) ## Problem followup of #7049 as mentioned in #7049 ``` Before we introduced QProfile customization is bound to a specific idc instance After customization is bound to a specific Q profile and an idc instance can have multi profiles in other words, each Q profile will have access to different sets of customization ``` ## Solution Product team wants us to show all customizations across profiles instead of the connected one only. By that mean, when users select a customization, it might implicitly change the profile for users in the selected customization is not accessible by the current profile. The purpose is to reduce the churn users might be lost what profile has access to what customization. ## user story 1. click "select customization" button from the menu -> should show "all" customizations across profiles 2. select a customization under different profile -> should change the profile to the one owning the newly selected customization 3. select a profile which doesn't have access to the selected customization -> should fallback to "default" and prompt ui saying you don't have access to the customization ### Implicity change profile when user selects a customization under a different profile https://github.com/user-attachments/assets/49bfe61f-04a7-4d07-aaff-1e3c284fb710 ### Change profile should validate if the selected customization is under the new profile or not https://github.com/user-attachments/assets/414f85dd-50a1-4d28-9b33-e59691f25a0c Note that customization will have only 1 profile owner, so there wont be duplicate customization across profiles --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

perf(amazonq): nep UI improvement (#8264) ## Problem ## Solution --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

telemetry(inline-suggestion): Fix incorrect clientComponentLatency@preprocessLatency (#6320) ## Problem t1: user trigger inline suggestion either automatically or manually t2: start building request with editor context t3: done building request t4: call service API PreprocessLatency is supposed to denote `t3 - t1`, whereas current implementation isn't which has been using `codewhispererPreprocessingLatency: session.fetchCredentialStartTime - session.invokeSuggestionStartTime,` ## Solution --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

feat(amazonq): region expansion UX improvement (#2094) ## Problem - hide profile UI when there is only 1 profile - handle case where `ListAvailableProfile` call fails, will assume IAD and allow user to use Q - cancel ongoing Chat streaming onProfileChanged ## Solution related PRs 1. quick pick #2098 2. chat panel context menu #2099 3. profile selection page #2100 5. webview integration #2101 6. #2102 --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

feat(amazonq): show all customizations across different profiles #7181 this effectively restores #7060 (and reverts "revert PR" #7129)

fix(amazonq): fit & finish / bugbash issues ## Problem 1. css style 2. error handling 3. agents quick action command is gone after users select profile

fix(amazonq): fix enterprise users not able to sign in correctly if they have 2+ vscode instances open (#7151) ## Problem revision of #7134, this pr aims to address the comment from the previous PR https://github.com/aws/aws-toolkit-vscode/pull/7134#discussion_r2056518840 to extract the logic to a shared module so the diff against 7134 is expected to be large. after deployment 4/21, service has a strict 1 tps throttling policy and there was no caching for the API call previously. It will impact users as long as they have multiple ide instances opened as all of them will make list profile call while users attempt to sign in. ## Solution 1. cache the api result for 60 seconds for reuse 2. use lock to prevent multiple instances trying to call at the same time. Only 1 will make the service call and the rest will wait until it's done and read from the cache. --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

feat(amazonq): integrate profile selection flow with Chat, webview ## Problem - glues webview page and show `Profile selection` page when it's needed (connected with IdC and pending selection) - renew the chat window on selected profile changed