Raymond Zhao

This commit performs a **maintenance** update by running `npm audit fix` to address identified security vulnerabilities within the project's **dependencies**. It specifically targets and patches known security issues, ensuring the application's overall **security posture** is improved. This action primarily affects the `package.json` and `package-lock.json` files, updating dependency versions to secure ones without introducing new features or functional changes.

This commit introduces a **bug fix** to the **Copilot extension's post-installation script** (`extensions/copilot/script/postinstall.ts`). It modifies the `createClaudeSymlinks` function to **prevent the creation of symbolic links when running on Windows operating systems**. This change **resolves post-installation failures** that previously occurred on Windows due to the system's handling of symlinks, ensuring a smoother and more reliable installation process for users of the Copilot extension on that platform.

This commit performs **maintenance** by updating the **GitHub Actions PR pipeline** configuration. It grants `contents: read` permissions to the pipeline, specifically enabling the `core-ci` task to access and read companion extension releases. This **configuration update** is crucial for the `core-ci` task to function correctly, preventing build failures that would occur due to insufficient permissions when trying to read necessary release artifacts. The change is applied to the workflow definition in `.github/workflows/pr.yml`, ensuring the continuous integration process has the required access.

chore: bump flatted (#303340)

This commit performs essential **security maintenance** by executing `npm audit fix` across the project. It addresses identified **vulnerabilities within the project's dependency tree**, ensuring that all installed packages are updated to their most secure versions where fixes are available. This action significantly improves the overall **security posture** of the application by mitigating potential risks associated with outdated or compromised third-party libraries. The work is a **dependency management** task, enhancing the reliability and safety of the entire codebase.

chore: run npm audit fix (#301189)

This commit performs a **maintenance chore** to **standardize the installation steps** across the project. It aims to **align existing installation procedures**, likely within **documentation** or **setup scripts**, to ensure consistency and clarity. The primary impact is an improved and more uniform onboarding experience for new users and developers setting up the project, reducing potential confusion during the initial setup phase.

chore: test gif transfer (#299560)

This commit performs **maintenance** by addressing **security alerts** originating from the `serialize-javascript` dependency. It resolves reported vulnerabilities, likely through a dependency update or configuration adjustment, to mitigate potential risks associated with this third-party library. This **security fix** improves the overall robustness and trustworthiness of the application by ensuring its dependencies are free from known issues.

This commit performs **routine security maintenance** by executing `npm audit fix` to address identified vulnerabilities within the project's **third-party dependencies**. It updates the `package-lock.json` file to ensure that all installed packages meet the latest security recommendations, thereby **improving the overall security posture** of the application. This **proactive patching** helps mitigate risks associated with known exploits in external libraries, ensuring a more robust and secure development and production environment.

This commit **adjusts** the **BinSkim filter** specifically for **Windows builds**, refining the static analysis configuration. As a **chore**, this change aims to improve the relevance and signal-to-noise ratio of BinSkim reports by potentially suppressing false positives or focusing on more critical issues. This update streamlines the development workflow for Windows by ensuring static analysis provides more actionable insights.

This commit performs a general **dependency update** via `cargo update`, primarily **upgrading the Rust toolchain** in the CI workflow from version 1.85 to 1.88. As part of this **maintenance chore**, internal adjustments were made within the **CLI module** to accommodate updated dependencies. Specifically, byte slice handling was adjusted for **JSON RPC message dispatching** in `cli/src/json_rpc.rs`. Additionally, the `url_path_basename` function's logic for path segment retrieval and error mapping was simplified in the **HTTP utility functions** within `cli/src/util/http.rs`. This ensures compatibility and leverages improvements from newer Rust versions and libraries across the project.

This commit performs a **maintenance** task by **bumping the version numbers** for various extensions within the project. This ensures that the system utilizes the latest compatible versions of these dependencies, potentially incorporating recent bug fixes, performance improvements, or new features from those updated components. The change affects multiple extension modules, aligning them with current release cycles and improving overall project stability and currency.

This commit performs a **core infrastructure update** by **onboarding the project onto a new sysroot**. This **maintenance** task ensures the entire build system and all dependent components are compatible with updated system libraries and tools. The change impacts the foundational **build environment**, laying the groundwork for future development and maintaining compatibility with the latest platform standards.

This commit **removes** the `workbench.settings.scrollBehavior` setting, effectively **deprecating and eliminating** the user-configurable scroll behavior within the **Workbench Settings Editor**. This **feature removal** simplifies the settings interface by removing an option that controlled how the editor scrolls when navigating between settings. The change primarily affects the `src/vs/workbench/contrib/preferences/browser/settingsEditor2.ts` module, where associated logic, interfaces, and constants were removed, and methods like `onDidClickSetting` and `updateTreeScrollSync` were updated to reflect the absence of this setting. Users will no longer have control over this specific scroll behavior in the settings.

This commit delivers a **bug fix** addressing a **regression** in the **settings editor's feature filtering**. It **restores the correct display and filtering** of **chat-related settings** by refactoring the `filter` logic in `src/vs/workbench/contrib/preferences/browser/settingsTreeModels.ts`. This ensures that settings tagged with `@chat` are properly recognized and included in search results, preventing users from encountering issues when searching for chat preferences within the settings UI.

This commit **refines the settings layout** for the **Chat feature**, addressing structural inconsistencies and introducing new experimental controls. It **removes an empty and redundant `settings` array** from the `chat` section within `settingsLayout.ts`, improving the clarity of the settings definition. Concurrently, it **adds new experimental settings** under `chat.experimental.detectParticipant.*` to the `chatContext` settings, providing users with advanced configuration options for chat participant detection. This work enhances the maintainability of the settings schema and expands user control over experimental chat functionalities.

This commit introduces a **new capability** to the **Preferences UI** by enforcing a more structured organization for **Chat settings**. It updates `src/vs/workbench/contrib/preferences/browser/settingsLayout.ts` to ensure that all chat-related configurations are now nested within specific subcategories, rather than appearing at the top level. This change improves the discoverability and management of chat features by providing a clearer hierarchy for their settings. The work is a **UI/UX improvement** aimed at enhancing the overall user experience when configuring chat functionalities.

This commit introduces a **new sorting mechanism** for **extension settings** within the **Settings UI**, specifically prioritizing stable settings by moving all **experimental extension settings to the end** of the list. This **feature enhancement** improves the user experience by ensuring that more commonly used settings are readily accessible. The change involves a new sorting function applied during the resolution of the settings tree, affecting how settings are displayed via functions like `_resolveSettingsTree` and `sortSettings` in `settingsTree.ts`. Users will now find experimental options less prominent, streamlining the configuration process for standard settings.

This commit provides a **bug fix** for a regression that affected the **Settings Editor's search and filtering interaction**. It **restores correct behavior** by ensuring that category filters are properly applied when users search for settings, preventing instances where search results might incorrectly disappear or appear. The change involves **refactoring** the `SettingsTreeFilter` logic within the `preferences` module, including renaming the `filterToCategory` property to `categoryFilter` and introducing a new `settingContainedInGroup` method to accurately determine if a setting belongs to a filtered category. This significantly improves the **reliability and consistency** of the settings search experience.