Regenerate `*.cbuild-run.yml` after saving `./cmsis/xxx.dbgconf`

[jreineckearm]

Current behavior, Steps to reproduce and Expected behavior

Tested with nightly build 1.68.1-28-20260715

Open-CMSIS-Pack/cmsis-toolbox#636 added support for converting *.dbgconf into device-settings: in *.cbuild-run.yml. This works fine but we need a trigger now to regenerate *.cbuild-run.yml after *.dbgconf was saved.

Note if it helps with implementation: The trigger can be suppressed if *.csolution.yml contains device-settings: in the active target set as they would win over the *.dbgconf contents.

Additional Information

No response

[edriouk]

@jreineckearm , .dbgconf files are in a hidden folder (.cmsis). Users should not see and edit them directly, right? What triggers their updates?

[jreineckearm]

@jreineckearm , .dbgconf files are in a hidden folder (.cmsis). Users should not see and edit them directly, right? What triggers their updates?

Configuration Wizard. This is an essential configuration file and must be discoverable by the user.

The dbgconf file is listed in the CMSIS View under Device section:

[edriouk]

Can we change the location? What was actual motivation to place a file in a hidden folder, but make it discoverable?
We use file watcher for solution files that exclude hidden directories.

[jreineckearm]

Don't know, the spec says "This file can be configured to reflect user settings." Nothing about being unchangeable.

Also, launch.json and friends in .vscode are user editable through the GUI (like *.dbgconf should be through Configuration Wizard). Looks like the same principle across all platforms to me.

@edriouk - see Open-CMSIS-Pack/devtools#2029 (comment)