[docs] Automatic Workspace folders feature is now enabled by default.

Bug: 395562934
Change-Id: If06bcf28f3a7252b7c0a42aca6f1136fd1412b7f
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6357470
Reviewed-by: Philip Pfaffe <[email protected]>
Auto-Submit: Benedikt Meurer <[email protected]>
Commit-Queue: Philip Pfaffe <[email protected]>

Author: bmeurer

docs/cookbook/devtools_on_devtools.md

@@ -37,9 +37,11 @@ editing in your IDE (e.g. VS Code or Cider-G). With M-135, a new feature called
 [Automatic Workspace folders][automatic-workspace-folders-documentation] was
 introduced, which can be used to make debugging and developing DevTools easier.
 
+As of 2025-03-16, the feature is enabled by default in M-136 and later version.
 Follow the steps [here](../ecosystem/automatic_workspace_folders.md#setup) to
-set up your Chrome or Chromium instance. Then in your `devtools-frontend`
-checkout, use
+set up your Chrome or Chromium instance for earlier versions of M-136 and M-135.
+
+Then in your `devtools-frontend` checkout, use
 
 ```
 ./third_party/chrome/chrome-linux/chrome \

docs/ecosystem/automatic_workspace_folders.md

@@ -68,9 +68,10 @@ the origin of the inspected page is `localhost`.
 
 ## Setup
 
-In M-135, which is in Canary channel at the time of this writing, and probably
-M-136 too, this feature is disabled by default. To use it, you need to turn on
-two feature flags in `about:flags`:
+In M-136, which is in Canary channel at the time of this writing, the relevant
+flags have been enabled by default (as of 2025-03-16). In earlier versions of
+M-136 and in M-135, this feature is disabled by default. To use it, you need to
+turn on two feature flags in `about:flags`:
 
 -   [chrome://flags#devtools-project-settings](chrome://flags#devtools-project-settings)
 -   [chrome://flags#devtools-automatic-workspace-folders](chrome://flags#devtools-automatic-workspace-folders)