Update .vscode/README.md to enhance the documentation for custom Assertoor configurations. Added an example YAML configuration and detailed notes on the configuration process, including how to set up nodes, enable additional services, and customize parameters for testing environments. This improves clarity and usability for users creating personalized configurations.

Author: tosettil-polimi

.vscode/README.md

@@ -109,22 +109,41 @@ You can create a custom devnet configuration to customize the testing environmen
 2. Add your desired configuration to this file
 3. The devnet setup will automatically use your custom configuration if it exists
 
-## Custom Assertoor Configuration
+### Example Configuration
 
-You can create a personalized Assertoor configuration that overrides or extends the automatically generated settings.
+Here's an example of a custom configuration:
 
-### How the configuration system works
+```yaml
+participants:
+- el_type: erigon
+  el_image: test/erigon:current
+  cl_type: prysm
+  count: 2
+additional_services:
+- assertoor
+- dora
+assertoor_params:
+  run_stability_check: false
+  run_block_proposal_check: true
+```
 
-When you run the devnet setup (`.hack/devnet/run.sh`), the following process occurs:
+This configuration:
+
+- Sets up 2 nodes with Erigon (execution layer) and Prysm (consensus layer)
+- Enables additional services (Assertoor and Dora)
+- Configures Assertoor with specific parameters and test playbooks
+- Uses custom Docker images for testing
+
+### Notes
 
-1. **Kurtosis generates a base config** from the ethereum-package, including endpoints and global variables
-2. **The script looks for a custom file**:
-   - First searches for `custom-assertoor.devnet.config.yaml`
-   - If not found, uses `assertoor.devnet.config.yaml`
-3. **Applies environment variables** to the custom file using `envsubst`
-4. **Merges the configurations** using `yq eval-all` which combines:
-   - The config generated by Kurtosis (with endpoints, database, etc.)
-   - Your custom config that overrides/adds settings
+- Make sure all requirements are installed before launching the debugger
+- The `devnet-setup` task may take a few minutes the first time
+- You can set breakpoints in the Go code before starting the debug session
+- Custom configurations allow you to test different network setups and scenarios
+
+## Custom Assertoor Configuration
+
+You can create a personalized Assertoor configuration that overrides or extends the automatically generated settings.
 
 ### Creating your custom Assertoor configuration
 
@@ -179,7 +198,6 @@ database:
 
 - **Change web port**: Modify `web.server.port`
 - **Add custom tests**: Use `externalTests` to include your test playbooks
-- **Custom global variables**: Use `globalVars` for test parameters
 - **Custom logging**: Configure log level and format
 - **Different database**: Switch from PostgreSQL to SQLite or customize connection settings
 
@@ -189,35 +207,3 @@ database:
 - The generated config is recreated each time you run the devnet setup
 - Environment variables in your config (like `${DEVNET_DIR}`) are automatically substituted
 - Your custom settings will override any conflicting settings from the generated config
-
-### Example Configuration
-
-Here's an example of a custom configuration:
-
-```yaml
-participants:
-- el_type: erigon
-  el_image: test/erigon:current
-  cl_type: prysm
-  count: 2
-additional_services:
-- assertoor
-- dora
-assertoor_params:
-  run_stability_check: false
-  run_block_proposal_check: true
-```
-
-This configuration:
-
-- Sets up 2 nodes with Erigon (execution layer) and Prysm (consensus layer)
-- Enables additional services (Assertoor and Dora)
-- Configures Assertoor with specific parameters and test playbooks
-- Uses custom Docker images for testing
-
-### Notes
-
-- Make sure all requirements are installed before launching the debugger
-- The `devnet-setup` task may take a few minutes the first time
-- You can set breakpoints in the Go code before starting the debug session
-- Custom configurations allow you to test different network setups and scenarios