## Problem
As part of sagemaker-connect project: 
- User able to connect to sagemaker space from toolkit extension 
- User able to connect to sagemaker space using deeplink uri

## Solution
- Connect using sagemaker startSession API which starts an ssm session 
- Use remote-ssh extension to handle the ssh connection 
- Use custom proxy command to handle initial connection and reconnection
- Use a detached local endpoint that is able to call startSession to
handle connection and reconnection

---

- 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.

---------

Co-authored-by: Newton Der <[email protected]>
Co-authored-by: Edward Sun <[email protected]>

…#2136)

## Problem
- Users should be able to start and stop SageMaker Spaces directly from
the Toolkit extension, without relying on the Studio UI.
- When actions like start, stop, or connect fail, users currently
receive no feedback, making troubleshooting difficult.


## Solution
- Added buttons to start and stop a space
- Implemented error notifications for failures when viewing, starting,
or stopping spaces.
- For errors during startSession, display a webpage hosted by the local
SageMaker server, since remote VS Code windows cannot display standard
error messages from the local server.

---

- 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.

---------

Co-authored-by: Newton Der <[email protected]>
Co-authored-by: Edward Sun <[email protected]>

## Problem
- When the Toolkit connects to a remote space, it should automatically
apply the space filter based on the space profile owner.

## Solution
1.  Read the metadata file to extract the space name and domain ID.
2. Use the describeSpace API to retrieve the profile name.
3. Apply filtering using the domain ID and profile name as keys.


---

- 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.

Merge staging into feature/sagemaker-connect

…pdate error page styling (aws#2149)

## Problem
- Disable deep link reconnect logic for the Phase 1 release of the
SageMaker Connect feature, as backend support is not yet ready. Logic
will be re-enabled in Phase 2.
- Fix styling issues on the error page.

## Solution
- Comment out reconnect logic and associated tests.
- Return a 200 response with a message for reconnect attempts.
---

- 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.

## Problem
- Merge staging into feature branch

## Solution
- fix merge conflicts

---

- 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.

---------

Co-authored-by: aws-toolkit-automation <>
Co-authored-by: Laxman Reddy <[email protected]>
Co-authored-by: aws-toolkit-automation <[email protected]>
Co-authored-by: Roger Zhang <[email protected]>
Co-authored-by: Reed Hamilton <[email protected]>
Co-authored-by: Jacob Chung <[email protected]>
Co-authored-by: aws-ides-bot <[email protected]>

* Release 1.81.0

* Update version to snapshot version: 1.82.0-SNAPSHOT

* feat(lambda): Merging Feature/lambda console2 ide to staging branch. (aws#7601)

## Notes:
- Releasing aws/aws-toolkit-vscode-staging#2144


---

- 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.

Co-authored-by: aws-toolkit-automation <[email protected]>
Co-authored-by: Roger Zhang <[email protected]>
Co-authored-by: Reed Hamilton <[email protected]>
Co-authored-by: Jacob Chung <[email protected]>

---------

Co-authored-by: aws-toolkit-automation <>
Co-authored-by: aws-toolkit-automation <[email protected]>
Co-authored-by: Roger Zhang <[email protected]>
Co-authored-by: Reed Hamilton <[email protected]>
Co-authored-by: Jacob Chung <[email protected]>